Bridude
03-08-2004, 12:58 PM
http://www.tribalwar.com/forums/showthread.php?t=279874
m having trouble getting the clients connected to the internet. I set the server up with 2 nics so its also acting as the firewall. We have a dsl modem which I just found out acts like a dhcp server. Is it ok to have the incomming nic set to obtain an ip or does it have to be a static ip?
Thanks in advance.
Also on another note: I setup the DHCP and everything was working great. Then all of a sudden the server started spewing out ip's called BAD_ADDRESS and knocking all the workstations off the network. Apperently theres a bug when you release/renew a client the screws up the DHCP. I looked everywhere for a fix but the only thing I found was related to NT 4.0. I disabled DHCP and even deleted the scopes and it was still bumping off the workstations. I had to use another batch of static ip's just to get things working.
Cliff Notes:
Help Please!
FUBAR|Ascain
03-08-2004, 04:01 PM
Ideally, you want a static IP address on the external interface and internal interface of the server for Active Directory and DNS reasons. Disable DHCP on the DSL modem and staticly assign an IP from the DSL router's IP range to the external interface of your 2k3 server. Plug the DSL modem into the external interface on the server. Plug the internal interface of the server into your hub/switch. Configure DHCP on the server to a different address set than the DSL modem servers. (10.10.10.x might be a good choice). Configure the DHCP options on the 2k server to point the gateway (router) to the 2k3 server's internal IP, and the DNS server and nameserver fields to the internal interface IP of the 2k3 server. Authorize the 2k3 DHCP server in Active Directory (right click it). Check to verify your 2k3 server DNS has root hint servers or forwarders. In Routing and Remote Access, verify your NAT is configured correctly.
Ipconfig /release and /renew your clients, verify you can surf the web.
Bridude
03-08-2004, 04:51 PM
Thanks Fub! The only thing is like I mentioned above I disabled the server's internal DHCP service cause it went crazy. From what I've read its due me releasing and renewing the ip's.
Unfortunatley I have to use 192.168.110.xx on the internal cause thats the ip's needed tp connect to the unix server.
Disable DHCP on the DSL modem and staticly assign an IP from the DSL router's
I will try that. or could I keep the dhcp on and set the range of the modem to only assign 1 ip and then put that ip on the external nic?
example modem DHCP range 10.10.10.1 to 10.10.10.1
Bridude
03-08-2004, 05:17 PM
here is the modem we have btw.
http://www.dslreports.com/faq/6096
FUBAR|Ascain
03-08-2004, 05:28 PM
Disable the modem DHCP entirely and make the IP on the external interface of the server static. Your DHCP is probably going crazy because it detects the second server. Can you set the internal IP of the modem? If so, set it to the seperate network address like 10.10.10.1, the server's external interface as 10.10.10.2 with a gateway of 10.10.10.1. You don't need the DHCP since the addresses are on the same network.
Set your 2k3 DHCP to have a range of 192.168.110.50-250 or whatever. Set the internal IP of the server to 192.168.110.a, set the DHCP scope options to have the router, dns and nameserver (and wins if you use it) to 192.168.110.a (the internal server IP). The server's internal interface will not have a default gateway. The server should point to itself as DNS. If your DNS server is configured correctly with the root hints servers clients will resolve addresses correctly.
Once the clients get the new IP address they will do DNS lookups from your 2k3 server, and route all requests to the web through the server's internal interface and out through the external.
Remember, if the modem is currently servicing the addresses and you set up a different server, there may be some systems who want a particular IP address for renewal. You may need to verify they allocate correctly. (Assuming you have no current IP conflicts it shouldn't be an issue, each will try to renew the current IP first and the server should let them since no IPs will currently be registered).
Bridude
03-08-2004, 07:03 PM
Yes I believe I can set the internal ip. I will try setting it up exactly like that.
Thanks a ton Fubar.