Network Path Was Not Found When Attempting to Join a Domain
Posted on 2004-10-05
Our network was using IP addresses of 10.0.0.XXX, until today. We had a T1 router installed and it is 192.168.1.1. The instructions said to set the TCP/IP setting to "Obtain IP Address Automatically", which I did at the server (probably the kiss of death there). All client workstations can get on the internet using the T1, all can ping the server and the server can ping back, but 10 out of 12 machines can no longer see the shared folders on the server.
To troubleshoot, I tried taking one machine off the domain, added it it a new workgroup name, rebooted, then tried to add it back to the domain. I got "The network path was not found" error. I've read several threads on this site and have tried everything mentioned, except for downloading and running a winsockxpfix.exe file, which I'm a bit reluctant to do because (1) it sounded like that would be a fix if just one machine were having the problem and (2) it's not from Microsoft or another company I'm familiar with.
I've gone into "DHCP" in the Administrative Tools program group on the Windows 2000 server and deactivated the existing scope (the 10.0.0.XXX range) and created a new scope (the 192.168.1.XXX range). The machines that were working, continue to work. The machines that couldn't see the network, still don't see it.
All of these machines need access to the server's shared programs and files - please help!!!!