General discussion

Locked

W2K Server / Router Conflict

By gregberry ·
I have a small office of 5 pcs (win xp pro) and 1 Windows 2000 Server running AD (root server)(192.168.0.2). DNS is running on the server. We also have a NetGear FVS318 DSL Router (192.168.0.1). I have this same configuration at several client locations and not having this problem, not sure what I am missing here.

Here is the problem:
On the xp pro pcs, when we have 192.168.0.2 as the primary and 192.168.0.1 as the secondary DNS, we can log onto the server and always access server folers but the internet sometimes works and sometimes doesn't. Plus it takes quite a while to login.

If DNS has only 192.168.0.2 as the primary, we can login quickly and access everything except the internet.

If we have 192.168.0.1 as the primary DNSand 192.168.0.2 as secondary it takes forever to login, then we can't access any shared folders on the server, but we have internet access.

AD requires DNS to run correctly, and because it is a root server, I can't put any forwarders in the DNS properties.

Any Ideas or Suggestions? Thanks!

This conversation is currently closed to new comments.

11 total posts (Page 1 of 2)   01 | 02   Next
| Thread display: Collapse - | Expand +

All Comments

Collapse -

W2K Server / Router Conflict

by Gr@ndcri In reply to W2K Server / Router Confl ...

As I know your NetGear FVS318 DSL Router is not a DNS server. So why did you used 192.168.0.1 as DNS? Maybe you used DNS proxy function!!! Also your DNS 192.168.0.2 must have a link to his internet provider DNS(out site). For me 198.168.0.1 it is your gateway to the Internet and also your Firewall(settings are the same to the other?). Your problem should come from the setting between your W2k sever and your router. All Client pc should be setup with 192.168.0.2 as DNS or push this DNS via your DHCP(if it?s setup).
Hope this help you out. Maybe it?s just create a spark in your mind.

Collapse -

W2K Server / Router Conflict

by gregberry In reply to W2K Server / Router Confl ...

Poster rated this answer

Collapse -

W2K Server / Router Conflict

by CG IT In reply to W2K Server / Router Confl ...

I use DHCP on a W2K server with AD and configure W XP pro client's browsers to use proxy ,e.g. <server name> <port 8080> to obtain external access from the network.

On the W2K DC, I use two nics, one that is the internal interface for clients, one that is the external interface for WAN access.The external interface is configured with a static IP and the default gateway is the router IP address. DNS IP addresses are my ISP DN'S not my PDC.

Collapse -

W2K Server / Router Conflict

by gregberry In reply to W2K Server / Router Confl ...

requires a completely different configuration

Collapse -

W2K Server / Router Conflict

by curlergirl In reply to W2K Server / Router Confl ...

First of all, you don't want to use your Netgear internal IP address as a DNS server address, since it's NOT a DNS server. Here's what I'd recommend:

On your Win2K server, open your DNS zone and REMOVE the root object (".") so that your Win2K server is no longer a root server. This will allow you to enable forwarders on your Win2K server; set the forwarder(s) to your ISP's DNS server address(es). Then, on all workstations, set the DNS servers (both) to 192.168.0.2 (your DNS server) and thedefault gateway to 192.168.0.1 (your Netgear router). This should solve all your DNS problems and work very smoothly for you. If you have any other questions, feel free to email me. Hope this helps!

Collapse -

W2K Server / Router Conflict

by gregberry In reply to W2K Server / Router Confl ...

did remove the root object from the DNS server and added forwarders, but still had the same problem, found out it was a AD configuration problem.

Collapse -

W2K Server / Router Conflict

by Mihai.P In reply to W2K Server / Router Confl ...

your configuration should be like this:
pc's DNS should be 192.168.0.2 (DC server) - maybe static or using a DHCP server on DC
DC server should have set it's own ip in DNS (ip properties)
DNS server on domain controller should contain it's internal zone and have set up provider's DNS as forwarder

Collapse -

W2K Server / Router Conflict

by gregberry In reply to W2K Server / Router Confl ...

already setup

Collapse -

W2K Server / Router Conflict

by ak6110 In reply to W2K Server / Router Confl ...

First of all, seeing all the rest of the answer, no one ask you this question.

Are you using the NetGear DHCP to provide ip address. If so you client default DNS will be the NetGear IP address (192.168.0.1)

The best solution is to disable the NetGear DHCP, install a DHCP in your server. You can either use the DHCP option 006 to put in the DNS of your server and the ISP DNS, or you use you DNS forwarders to input the ISP DNS.

With both options, you client still need the option 006 in DHCP to have the server DNS ipaddress (192.168.0.2) to work.

Try this out, it will make you life less stress.

Collapse -

W2K Server / Router Conflict

by gregberry In reply to W2K Server / Router Confl ...

the pcs have internal static ips

Back to Windows Forum
11 total posts (Page 1 of 2)   01 | 02   Next

Related Discussions

Related Forums