N
Nobody Important
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?
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?