Ok, took the dead linky back and got one that works. Thats the easy part.
OK, heres the setup and can I do what I want to do?
Have aDSL PPoE 3 with comps going straight out the linky set up dynamic, they work great, forth one is a 2000 server running proxy software and two more behind the proxy 2000 machine. This is so I can run filters on the kids and keep some control over their browsing habits
OK, the question, with the outbound NIC in the 2000 server set dynamic it works great, but if I set up the Server static with 192.168.1.100 it can see the linky but not connect to the net. I want the server static so I can map to it to run HTTP server and a unreal server.
Why cant i get the static machine through the Linky???
Can the Linky be setup dynamic yet still have a staticly addressed machine behind it is my question
Any help would be appreciated.
Linksys Question
- YeOldeStonecat
- SG VIP
- Posts: 51171
- Joined: Mon Jan 15, 2001 12:00 pm
- Location: Somewhere along the shoreline in New England
You need a couple of more things, mainly, Gateway, and DNS.
Leave DHCP of the router turned on as a safety net, so you can get any machine going with "obtain IP".
On any machine you make static, take a range outside of the routers DHCP. Since the routers LAN IP is 192.168.1.1, and it's DHCP hands out beginning at 192.168.1.100, that leaves you 192.168.1.2 up to 192.168.1.99 to work with.
When the workstations are set to "obtain IP", they get more information from the routers DHCP service than just an IP address, they also get told what the gateway is (how to GET to the internet), and where to get their DNS info (for name resolution on the internet). So take away DHCP, they need to be given this information.
So give the "server" an IP of say 192.168.1.11, subnet of 255.255.255.0 Any other computers just pick a different IP address, must be unique for all.
Set it's gateway to be the LAN of the router, assuming defaults, 192.168.1.1
WINS...leave disabled.
DNS...normally the router hands out its own address, which just forwards to your ISP's two DNS servers. Find out what your ISPs two DNS servers are, and enter those. You can find these by looking on your routers web admin page...the status tab...when it's connected. On Win9X boxes, and NT 4, on the DNS section, it will also have a DNS host name, and DNS domain. Host is just your computers network identification, and domain is your ISP's formal domain name.
Reboot and you will be up and running.
Leave DHCP of the router turned on as a safety net, so you can get any machine going with "obtain IP".
On any machine you make static, take a range outside of the routers DHCP. Since the routers LAN IP is 192.168.1.1, and it's DHCP hands out beginning at 192.168.1.100, that leaves you 192.168.1.2 up to 192.168.1.99 to work with.
When the workstations are set to "obtain IP", they get more information from the routers DHCP service than just an IP address, they also get told what the gateway is (how to GET to the internet), and where to get their DNS info (for name resolution on the internet). So take away DHCP, they need to be given this information.
So give the "server" an IP of say 192.168.1.11, subnet of 255.255.255.0 Any other computers just pick a different IP address, must be unique for all.
Set it's gateway to be the LAN of the router, assuming defaults, 192.168.1.1
WINS...leave disabled.
DNS...normally the router hands out its own address, which just forwards to your ISP's two DNS servers. Find out what your ISPs two DNS servers are, and enter those. You can find these by looking on your routers web admin page...the status tab...when it's connected. On Win9X boxes, and NT 4, on the DNS section, it will also have a DNS host name, and DNS domain. Host is just your computers network identification, and domain is your ISP's formal domain name.
Reboot and you will be up and running.
MORNING WOOD Lumber Company
Guinness for Strength!!!
Guinness for Strength!!!