![]() |
|
Welcome to Vista Banter. You are currently viewing our boards as a guest which gives you limited access to view most discussions, articles and access our other FREE features. By joining our free community you will have access to ask questions and reply to others posts, upload your own photos and access many other special features. Registration is fast, simple and absolutely free so please, join our community today! If you have any problems with the registration process or your account login, please contact contact support. |
|
|||||||
| Networking with Windows Vista Networking issues and questions with Windows Vista. (microsoft.public.windows.vista.networking_sharing) |
|
|
LinkBack | Thread Tools | Display Modes |
|
|||
|
I was having a terrible time getting a new Vista workstation to join the
domain at work. The solution for me was to go into the TCP/IP settings on the Vista machine and make sure the DNS address listed first was that of our local DC (which is also our file server). The secondary address is that of our ISP's servers. XP didn't have a problem when only our ISP's DNS address was listed but Vista needs the DNS address of our server explicitly. Since our server is also a DHCP server, I could also add our server's DNS address there and let the workstations stay set to "Obtain DNS server address automatically". Hope this will help someone! Tom Lake |
|
|||
|
Thank you for the update. For the security and performance, you should use
the internal DNS only. -- Bob Lin, MS-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 wrote in message ... I was having a terrible time getting a new Vista workstation to join the domain at work. The solution for me was to go into the TCP/IP settings on the Vista machine and make sure the DNS address listed first was that of our local DC (which is also our file server). The secondary address is that of our ISP's servers. XP didn't have a problem when only our ISP's DNS address was listed but Vista needs the DNS address of our server explicitly. Since our server is also a DHCP server, I could also add our server's DNS address there and let the workstations stay set to "Obtain DNS server address automatically". Hope this will help someone! Tom Lake |
|
|||
|
"Robert L (MS-MVP)" wrote in message ... Thank you for the update. For the security and performance, you should use the internal DNS only. When I tried that, I could no longer access the Internet from the workstation. Tom Lake |
|
|||
|
"Malke" wrote in message ... wrote: "Robert L (MS-MVP)" wrote in message ... Thank you for the update. For the security and performance, you should use the internal DNS only. When I tried that, I could no longer access the Internet from the workstation. Then you probably forgot to set forward/reverse lookup zones on the server. Briefly, correct DNS set up needs the server to only look to itself for DNS with the lookup zones set for Internet access. All workstations should only look to the server for DNS. Thanks! I'll check it on Monday when I'm back at work. I do know I have forward and reverse lookup zones but I don't know if they're set for Internet access. Tom Lake |
|
|||
|
wrote in message
... "Robert L (MS-MVP)" wrote in message ... Thank you for the update. For the security and performance, you should use the internal DNS only. When I tried that, I could no longer access the Internet from the workstation. You need to setup root hints or forwarders on your internal DNS server then have all clients use only the internal DNS server. Removing the ISPs DNS will probably speed up the XP clients for some network operations as well as make Vista work properly. I recommend you use forwarders. If your server is SBS 2003 then running the IECW wizard will setup DNS and DHCP for you. http://technet2.microsoft.com/window....mspx?mfr=true http://technet2.microsoft.com/window....mspx?mfr=true http://support.microsoft.com/kb/323380 -- Kerry Brown Microsoft MVP - Shell/User http://www.vistahelp.ca |
|
|||
|
"Kerry Brown" *a*m wrote in message ... wrote in message ... "Robert L (MS-MVP)" wrote in message ... Thank you for the update. For the security and performance, you should use the internal DNS only. I have it all working now with the DHCP server handing out our server's DNS address (rather than our ISP's DNS address) along with an IP address. You're right; The remaining XP machines log on faster and we can still access the Internet. Thank you so much to all who responded! Tom Lake |
|
|||
|
"Tom Lake" wrote in message
... I have it all working now with the DHCP server handing out our server's DNS address (rather than our ISP's DNS address) along with an IP address. You're right; The remaining XP machines log on faster and we can still access the Internet. Thank you so much to all who responded! You're welcome. -- Kerry Brown Microsoft MVP - Shell/User http://www.vistahelp.ca |
| Thread Tools | |
| Display Modes | |
|
|