rokerij
Technical User
- Feb 12, 2003
- 199
Windows 2000 Adv. Server
Netgear Wireless Router - DHCP Doles out our IP's and uses the ISP's DNS (Time Warner Roadrunner)
Adding a 2000 client to the domain, we need to change the DNS in the network settings from Dynamic to 192.168.1.1 (add for the server)(only way to add the client to the domain), however using this DNS does not allow us access to the internet. Weird? SO we change the DNS setting back to dynamic after adding client and it allows internet and network on ALL the 2000 clients.
THE BIG ONE and MOST IMPORTANT
Adding a XP Pro client to the domain - use the same steps above. Works. However the XP client seems to lose the connection from time to time to the server and files. Internet still works fine, but if you open a server folder, it appears empty, or will hang.
1. Sometimes you can get direct access to the server and it's files, with no issues.
2. Sometimes it asks for a user name and password - you are not able to use the UN/Pass that you logged onto the client with and only on occassion will the admin/pass work.
3. Other times you can see the Root folder (DFS) on the server, but when you open the folders they are empty. Hovering over the folder will also show that they're empty..
4. Still other times you get denied access to the server all together with a network path not found error.
Thought that XP Pro was to make networking easy, this is a nightmare.
S.C. Albertin
Systems Coordinator/Newbie Tech
United Way
Help me to find my way, so that I may help others find theirs...
Netgear Wireless Router - DHCP Doles out our IP's and uses the ISP's DNS (Time Warner Roadrunner)
Adding a 2000 client to the domain, we need to change the DNS in the network settings from Dynamic to 192.168.1.1 (add for the server)(only way to add the client to the domain), however using this DNS does not allow us access to the internet. Weird? SO we change the DNS setting back to dynamic after adding client and it allows internet and network on ALL the 2000 clients.
THE BIG ONE and MOST IMPORTANT
Adding a XP Pro client to the domain - use the same steps above. Works. However the XP client seems to lose the connection from time to time to the server and files. Internet still works fine, but if you open a server folder, it appears empty, or will hang.
1. Sometimes you can get direct access to the server and it's files, with no issues.
2. Sometimes it asks for a user name and password - you are not able to use the UN/Pass that you logged onto the client with and only on occassion will the admin/pass work.
3. Other times you can see the Root folder (DFS) on the server, but when you open the folders they are empty. Hovering over the folder will also show that they're empty..
4. Still other times you get denied access to the server all together with a network path not found error.
Thought that XP Pro was to make networking easy, this is a nightmare.
S.C. Albertin
Systems Coordinator/Newbie Tech
United Way
Help me to find my way, so that I may help others find theirs...