Guest Nobody Important Posted July 8, 2007 Posted July 8, 2007 An office that I have had one two XP Home machines for several years is doing an upgrade and had to go XP Pro and Server 2003. We installed a new Dell 840 and I upgraded both work stations to XP Pro. The only problem is the long delay of signing into the server. I did some web searches and people are describing my exact problem as a DNS related. The workstations are not seeing the server at first and the requests are going out onto the web. Right now, we have a Linksys behind a Bellsouth (now the new AT&T!) modem doing the DHCP and DNS and all and I am using 192.168.1.100 as the starting scope. This office needs web access. So how should I configure the network to resolve this? I'd rather not change anything with the Linksys since it is working fine with DHCP and forwarding DNS to the internet. Can I just use manual TCP/IP configuration? IF that is so, what would the DNS address be? Or just cheat and use a HOST file with a pointer to the server?
Guest Myweb Posted July 8, 2007 Posted July 8, 2007 Re: Server DNS/DHCP Configuration Questions Hello Nobody, Configure your server as DHCP and DNS server and disable the features on your Linksys. It is a workgroup server i assume, because you talking about DNS is coming form the Linksys? The DHCP scope configure for your internal LAN only and configure a Forwarder to your ISP's DNS in your DNS server. Then your workstations first talks to your internal DNS and if this can not resolve the request it will ask the forwarder and give the resolved addresses to your clients. Best regards Myweb Disclaimer: This posting is provided "AS IS" with no warranties, and confers no rights. > An office that I have had one two XP Home machines for several years > is doing an upgrade and had to go XP Pro and Server 2003. > > We installed a new Dell 840 and I upgraded both work stations to XP > Pro. > > The only problem is the long delay of signing into the server. I did > some web searches and people are describing my exact problem as a DNS > related. The workstations are not seeing the server at first and the > requests are going out onto the web. > > Right now, we have a Linksys behind a Bellsouth (now the new AT&T!) > modem doing the DHCP and DNS and all and I am using 192.168.1.100 as > the starting scope. This office needs web access. > > So how should I configure the network to resolve this? I'd rather not > change anything with the Linksys since it is working fine with DHCP > and forwarding DNS to the internet. > > Can I just use manual TCP/IP configuration? IF that is so, what would > the DNS address be? > > Or just cheat and use a HOST file with a pointer to the server? >
Recommended Posts