Recommended Posts

Hello ppl,

We've just had a DSL Router installed, if i connect my laptop to it to test with dns settings e.t.c all works ok.

I now have to intergrate it into an existing LAN.

we have a Windows 2000 server with 2 NICS 1 configured with an ip of 192.168.200.2 which is inline with the DHCP scope that it provides to the clients

We have another router that connects us to other sites which is 192.168.200.1

i need to give all the clients on our site ( about 10 ) access to the internet through this dsl router without changing the DHCP scope.

If i connect the router to the 2nd NIC and give it an adress local to the router i can talk to it but cannot get any internet access. This is because it is looking at our WAN router 192.168.200.1 which will eventually find the internet via another office. I have tried adding the dsl router as the primary dns but still no joy.

i cannot set up ICS because this will reset the IP addresses on the server.

any ideas what can i do ?

TIA Cray

Link to comment
https://www.neowin.net/forum/topic/106678-dsl-router-sharing-to-existing-lan/
Share on other sites

yes it was scribbled in haste ;)

ok existing setup...

1 Windows 2000 Server & 10 Windows 2000 Clients

DNS & DHCP running on server issueing 192.168.200.x addresses

1 existing router connects us to second office where there is internet access.

added to the system today.....

1 x DSL Router configured with 84.23.34.44

2nd NIC added to server configured with an IP so that it can talk to the router 84.23.34.45, also dns addresses added e.t.c

basically i need to give the 10 clients internet access through the new router rather than it finding the dns via our WAN. But it just defaults to our WAN Router even on the server itself ..

I can test the Router with my laptop plugged into the router and it works ok!

,,,,......

I would simply set the default DNS server on the clients to the Server's IP, that or set them to discover the server on its own.

If I understand correctly what the set up looks like, the server you what to pull addresses from and resolve names is the server closest to the client machines anyway.

This is all assuming that your problem is that the clients at this site are using the wrong server for DNS (i.e. thru your original router, to your WAN)

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.