I'm...just about ready to throw the thing out the window. And it's too hot and my head is scrambled from all the stress and fatigue.
All I know is that there's a computer behind me that I'm trying to get onto this network (linked by Ethernet cable through a reliable Netgear hub)... Other comps on the network are fine, and this one also worked fine until I had to copy that comp's drive onto another physical drive because it was dying. I then had to run a repair with an XP disk, install SP1 again, and...
Voila. Certainly not the first time I've had the case of the 53s... I'm referring, of course, to the output received ('system error 53--The network path specified was not found.') when I try to run a 'net use \\compname'--Network Setup Wizard and 'repair' functions for both server and client comps are unhelpful, and simply show that the client network connection is unable to renew IP (that is, obtain a DNS). This is annoying as heck, of course.
In addition, in subsequent random resettings/hub unpluggings/network connection reimplementings, the 'net view' command run from the client comp will sometimes show the server's computer name, and sometimes not. I've experienced this behavior before, so I don't consider it unusual.
Please save me from throwin' this thing out the window...
All I know is that there's a computer behind me that I'm trying to get onto this network (linked by Ethernet cable through a reliable Netgear hub)... Other comps on the network are fine, and this one also worked fine until I had to copy that comp's drive onto another physical drive because it was dying. I then had to run a repair with an XP disk, install SP1 again, and...
Voila. Certainly not the first time I've had the case of the 53s... I'm referring, of course, to the output received ('system error 53--The network path specified was not found.') when I try to run a 'net use \\compname'--Network Setup Wizard and 'repair' functions for both server and client comps are unhelpful, and simply show that the client network connection is unable to renew IP (that is, obtain a DNS). This is annoying as heck, of course.
In addition, in subsequent random resettings/hub unpluggings/network connection reimplementings, the 'net view' command run from the client comp will sometimes show the server's computer name, and sometimes not. I've experienced this behavior before, so I don't consider it unusual.
Please save me from throwin' this thing out the window...