L
lurker
Original thread with same subject line was posted 05/30/2006 in this group.
Consider a home network with two PCs connected to a linksys router.
1) Windows XP Home and
2) Windows 2000 PRO
Both have been updated with all critical updates.
All has been well for several months. On Windows XP I use Quicken and
FrontPage 2000 with their data files on Windows 2000 File Shares.
Several (many?) weeks ago, I would go to bed with all working, and the
next morning, the Windows XP machine could no longer use (or create new)
shares.
After many frustrating weeks, I have observed the network connection
fails at any time of day, even if in use. There are no entries in
either system's Event Viewer.
Ping between the two machines works in both directions.
Net use from Windows 2000 to Windows XP works fine. It does not work
for XP => 2000. Net use produces error message
System Error 53. Network not found.
Rebooting the Windows 2000 machine fixes the problem.
I am looking for suggestions on what tools, procedures to use to
troubleshoot the problem.
UPDATE:
Machines are FIXED IP Ethernet connected to linksys router at 192.168.1.1.
Netbios through TCP/IP is enabled.
All has been well for about two weeks this time. Power outage today due
to tropical storm caused me to have a fresh power up on all systems.
A short while later, my failure showed up again.
I have made diagnostic output available at
http://rpchc.com/chuck/
to resolve text formatting issue when pasted into newsgroup.
Observation this round:
Running chucks cdiag from a command prompt, I observed a message:
System Error 53. Network not found.
I traced it to a failing command:
"NET VIEW 127.0.0.1"
After rebooting QUEENIE, the NET VIEW command works okay. The omission
of the NET VIEW "127.0.0.1" results from the cdiag.txt (right before the
ping of YAHOO) is easy to overlook.
I think this might be the clue I have been looking for, but I don't know
what to do with it.
King-daddy
Consider a home network with two PCs connected to a linksys router.
1) Windows XP Home and
2) Windows 2000 PRO
Both have been updated with all critical updates.
All has been well for several months. On Windows XP I use Quicken and
FrontPage 2000 with their data files on Windows 2000 File Shares.
Several (many?) weeks ago, I would go to bed with all working, and the
next morning, the Windows XP machine could no longer use (or create new)
shares.
After many frustrating weeks, I have observed the network connection
fails at any time of day, even if in use. There are no entries in
either system's Event Viewer.
Ping between the two machines works in both directions.
Net use from Windows 2000 to Windows XP works fine. It does not work
for XP => 2000. Net use produces error message
System Error 53. Network not found.
Rebooting the Windows 2000 machine fixes the problem.
I am looking for suggestions on what tools, procedures to use to
troubleshoot the problem.
UPDATE:
Machines are FIXED IP Ethernet connected to linksys router at 192.168.1.1.
Netbios through TCP/IP is enabled.
All has been well for about two weeks this time. Power outage today due
to tropical storm caused me to have a fresh power up on all systems.
A short while later, my failure showed up again.
I have made diagnostic output available at
http://rpchc.com/chuck/
to resolve text formatting issue when pasted into newsgroup.
Observation this round:
Running chucks cdiag from a command prompt, I observed a message:
System Error 53. Network not found.
I traced it to a failing command:
"NET VIEW 127.0.0.1"
After rebooting QUEENIE, the NET VIEW command works okay. The omission
of the NET VIEW "127.0.0.1" results from the cdiag.txt (right before the
ping of YAHOO) is easy to overlook.
I think this might be the clue I have been looking for, but I don't know
what to do with it.
King-daddy