|
| If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|||||||
|
|
Thread Tools | Display Modes |
|
#1
January 5th 10, 10:52 PM
posted to microsoft.public.windowsxp.network_web
|
|||
|
|||
Strange DNS behaviour
I have an Active Directory domain (Server 2003 r2) with three AD integrated
DNS servers, x.x.x.85, x.x.x.87, and x.x.x.95. Most XP workstations are configured for 95 and 85 but they query 85 only. For instance if I use nslookup it shows x.x.x.85 as the server it's working against, even if the 85 server isn't one of the entries in the network setup. This isn't a problem until I take down 85 for maintanence. When I do that all XP boxes lose the ability to resolve names. Anyone have an idea of what's going on and how I can make these XP machines go to their secondary server when the primary isn't available? Thanks, Mark 
|
| Ads |
|
#2
January 5th 10, 11:42 PM
posted to microsoft.public.windowsxp.network_web
|
|||
|
|||
|
Strange DNS behaviour
Try these:
1. run nslookup and make sure you don't have any errors. 2. Switch the DNS to 95, for example server x.x.x.95. 3. enter a web site and press enter. Do you see any errors? Or post back with the result of ipconfig /all here. -- Bob Lin, Microsoft-MVP, MCSE & CNE Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com "MarkW-VA" wrote in message ... I have an Active Directory domain (Server 2003 r2) with three AD integrated DNS servers, x.x.x.85, x.x.x.87, and x.x.x.95. Most XP workstations are configured for 95 and 85 but they query 85 only. For instance if I use nslookup it shows x.x.x.85 as the server it's working against, even if the 85 server isn't one of the entries in the network setup. This isn't a problem until I take down 85 for maintanence. When I do that all XP boxes lose the ability to resolve names. Anyone have an idea of what's going on and how I can make these XP machines go to their secondary server when the primary isn't available? Thanks, Mark
|
|
#3
January 5th 10, 11:42 PM
posted to microsoft.public.windowsxp.network_web
|
|||
|
|||
|
Strange DNS behaviour
Try these: 1. run nslookup and make sure you don't have any errors. 2. Switch the DNS to 95, for example server x.x.x.95. 3. enter a web site and press enter. Do you see any errors? Or post back with the result of ipconfig /all here. -- Bob Lin, Microsoft-MVP, MCSE & CNE Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com "MarkW-VA" wrote in message ... I have an Active Directory domain (Server 2003 r2) with three AD integrated DNS servers, x.x.x.85, x.x.x.87, and x.x.x.95. Most XP workstations are configured for 95 and 85 but they query 85 only. For instance if I use nslookup it shows x.x.x.85 as the server it's working against, even if the 85 server isn't one of the entries in the network setup. This isn't a problem until I take down 85 for maintanence. When I do that all XP boxes lose the ability to resolve names. Anyone have an idea of what's going on and how I can make these XP machines go to their secondary server when the primary isn't available? Thanks, Mark
|
| Thread Tools | |
| Display Modes | |
|
|
Linear Mode
