System error 53 after hours of connection working

[clackey]

I have been running this HOME environment for 2-1/2 years. after
putting on updates in January, I became of this "relatively" interment
network file sharing problem.

3 machines
A. Windows XP Home SP2 with all updates
B. Windows XP Home SP2 with all updates
C. Windows 2000 PRO with all updates.

After rebooting machine C, everything is working as it always has.
Several hours later, the file shares quit working.
Ping still works in both directions on all machines.
Machines A and B cannot net use to C
Machines A and B cannot complete NET VIEW \\<ip address> /CACHE

Machine C can perform all net sharing with A and B.

nbtstat -a <machine-name> returns the correct information in the Machine
Name table.

Rebooting Machine C fixes the problem. I have to do this at least two
times a day.

See drawing here:
http://tinyurl.com/gvma7

I have chased a lot of excellent ideas here:
http://tinyurl.com/edqyx
but I can't seem to solve the problem.

Any ideas appreciated.

The fact that rebooting the target remote Windows 2000 always fixes the
problem suggests the problem is there. There are no items in the Event
logs or any other logs that indicate a problem.

Carl

 

[Ron Martell]

I have been running this HOME environment for 2-1/2 years. after
putting on updates in January, I became of this "relatively" interment
network file sharing problem.

3 machines
A. Windows XP Home SP2 with all updates
B. Windows XP Home SP2 with all updates
C. Windows 2000 PRO with all updates.

After rebooting machine C, everything is working as it always has.
Several hours later, the file shares quit working.
Ping still works in both directions on all machines.
Machines A and B cannot net use to C
Machines A and B cannot complete NET VIEW \\<ip address> /CACHE

Machine C can perform all net sharing with A and B.

nbtstat -a <machine-name> returns the correct information in the Machine
Name table.

Rebooting Machine C fixes the problem. I have to do this at least two
times a day.

See drawing here:
http://tinyurl.com/gvma7

I have chased a lot of excellent ideas here:
http://tinyurl.com/edqyx
but I can't seem to solve the problem.

Any ideas appreciated.

The fact that rebooting the target remote Windows 2000 always fixes the
problem suggests the problem is there. There are no items in the Event
logs or any other logs that indicate a problem.

Carl

Problems of this general type quite often turn out to be caused by a
firewall or internet security application. What are you using?

You would probably have a better chance of getting a solution to your
problem if you posted it to the newsgroup
microsoft.public.windowsxp.network_web as you will find more people
there with specific expertise in networking.

Good luck

Ron Martell Duncan B.C. Canada
--
Microsoft MVP (1997 - 2006)
On-Line Help Computer Service
http://onlinehelp.bc.ca

"Anyone who thinks that they are too small to make a difference
has never been in bed with a mosquito."

 

[clackey]

Problems of this general type quite often turn out to be caused by a
firewall or internet security application. What are you using?

You would probably have a better chance of getting a solution to your
problem if you posted it to the newsgroup
microsoft.public.windowsxp.network_web as you will find more people
there with specific expertise in networking.

Good luck

Ron Martell Duncan B.C. Canada

Thanks for the tip. I will post there.
For troubleshooting, I have turned off ALL firewalls. Across teh
months, I have tried several. I agree it sounds like firewall, but I
think I have proved it is not that.

 

[Rick]

I have been running this HOME environment for 2-1/2 years. after
putting on updates in January, I became of this "relatively" interment
network file sharing problem.

3 machines
A. Windows XP Home SP2 with all updates
B. Windows XP Home SP2 with all updates
C. Windows 2000 PRO with all updates.

After rebooting machine C, everything is working as it always has.
Several hours later, the file shares quit working.
Ping still works in both directions on all machines.
Machines A and B cannot net use to C
Machines A and B cannot complete NET VIEW \\<ip address> /CACHE

Machine C can perform all net sharing with A and B.

nbtstat -a <machine-name> returns the correct information in the Machine
Name table.

Rebooting Machine C fixes the problem. I have to do this at least two
times a day.

See drawing here:
http://tinyurl.com/gvma7

I have chased a lot of excellent ideas here:
http://tinyurl.com/edqyx
but I can't seem to solve the problem.

Any ideas appreciated.

The fact that rebooting the target remote Windows 2000 always fixes the
problem suggests the problem is there. There are no items in the Event
logs or any other logs that indicate a problem.

Carl

Maybe part of the problem is with the OS. XP Home is not the best
system for networking

--

Rick
Fargo, ND
N 46 53.251
W 096 48.279

 

[Ron Martell]

Maybe part of the problem is with the OS. XP Home is not the best
system for networking

Balderdash.

XP Home and Pro are identical in terms of peer-to-peer networking
connections.

The networking differences are primarily concerned with joining a
Windows Server domain, which is only available in Pro.

Ron Martell Duncan B.C. Canada
--
Microsoft MVP (1997 - 2006)
On-Line Help Computer Service
http://onlinehelp.bc.ca

"Anyone who thinks that they are too small to make a difference
has never been in bed with a mosquito."