Posted: 3/9/2006 2:33:47 PM EDT
|
OK, I finally have everything setup on the server. It has two nics, one attached to the internet and the other on the private network. I have two issues. 1. Internet on the local network is slow. 2. I cannot connect the clients to the servers domain. Here is the ipconfig info if it helps at all Windows IP Configuration Host Name . . . . . . . . . . . . : srvring Primary Dns Suffix . . . . . . . : Node Type . . . . . . . . . . . . : Unknown IP Routing Enabled. . . . . . . . : Yes WINS Proxy Enabled. . . . . . . . : No DNS Suffix Search List. . . . . . : hosts.bc1.bresnan.net Ethernet adapter Local Area Connection 3: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Realtek RTL8139 Family PCI Fast Eth NIC Physical Address. . . . . . . . . : 00-30-BD-6E-8D-0E DHCP Enabled. . . . . . . . . . . : No IP Address. . . . . . . . . . . . : 192.168.1.251 Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : 192.168.1.250 DNS Servers . . . . . . . . . . . : 192.168.1.250 Ethernet adapter Local Area Connection 2: Connection-specific DNS Suffix . : hosts.bc1.bresnan.net Description . . . . . . . . . . . : HP NetServer 10/100TX PCI LAN Adapt Physical Address. . . . . . . . . : 00-E0-18-C1-17-06 DHCP Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes IP Address. . . . . . . . . . . . : 69.146.134.83 Subnet Mask . . . . . . . . . . . : 255.255.240.0 Default Gateway . . . . . . . . . : 69.146.128.1 DHCP Server . . . . . . . . . . . : 172.19.133.17 DNS Servers . . . . . . . . . . . : 69.145.232.32 69.144.49.29 69.145.232.4 NetBIOS over Tcpip. . . . . . . . : Disabled Lease Obtained. . . . . . . . . . : Wednesday, March 08, 2006 11:18:21 Lease Expires . . . . . . . . . . : Sunday, March 12, 2006 11:18:21 PM |
|
I run a one server network at home, but on thing that got mine to work is to run the domain controler as the DNS server as well. This let the client computers get name resolution from a source that understands what your domain name is. Is the private network subnetted? |
|
I was able to clear up the speed issue by changing the DNS forwarder IP to the DNS of my ISP. So that it taken care of. Now I'm going to play with the domain joining issue. DHCP is running on the correct nic as I'm getting IP's assigned by the server on the private side. How are you doing Dave? |
|
The way I am reading it your private side is 192.168.0.0 and the pulic side is 69.146.134.83, am I correct? Or do you have a 3rd nic that is active? What puzzles me is this. DHCP Server . . . . . . . . . . . : 172.19.133.17 I don't see how your server can see that address from your ipconfig. I am doing well, how are you, Pepper and the kiddos doing? Me and Holly are expecting #4 this Sept..... 
|
|
Sigh I see this stuff all the time at work but I am a managing IT type now so forgive any errors. First, if that 2003 server is a DC, then you'll need to set that privately addressed nic's DNS server IP to be the same as the servers IP. I.E. both should be 192.168.1.251. Also, since you have DHCP running make sure it is handing out the servers private IP to the workstations as primary DNS otherwise they will not be able to join the domain. Reading below, I see you set the forwarder, so I will leave that it. It's late, I'm sure I missed plenty. ETA: How come your using both nic's in that manner? You should stick with ISA or whatever the Win2003 equivalent is if you must do that, or invest in a hardware gateway/firewall and disable that second nic. |
|
Multihomed Domain Controllers are some pretty bad stuff..I would at least make it a member server rather than a DC. However...here are some articles that may help. I bet the first one regarding DNS registration is the main problem. support.microsoft.com/kb/272294/en-us Also this one..it doesn't specifically say it applies to 2K3 but it does in all actuality...Make sure you unbind everything from the external NIC except TCP/IP. support.microsoft.com/kb/191611/EN-US/ IF that doesn't work IM me and i'll see what else I can come up with. I WOULD suggest a real firewall though, its not as if they are that expensive for a simple NAT one (sub 100$). ISA server is an option and also there are much better hardware firewalls out there...some even reasonable cheap depending on the size of your internet pipe, number of hosts on your internal network and the complexity of your configuration. *EDIT* IS this server also you DHCP server for the LAN? If so, do you have the DNS Servers on the scopes configured correctly? |
You are entirely correct on the addressing above. Honestly on the DHCP think I have no clue. It was automaticly configured as that. Congrats on the 4th! We just recently miscarried. :( |
DHCP is not currently running on the linksys router. I am running the dual nics because I thought it would be easiest to setup VPN doing it this way. I may end up reconfiguring the setup. |
|
What computer is .250?? If this machine (.251) is the DNS server you need to point the DNS to itself and then add your forwarders. Take that damn default gateway out of the local lan NIC also, it should be blank if you have another NIC in the system, the software (RRAS in your case I think) is what acts as the mechinism to route non-local traffic. The reason why it says DHCP on your WAN NIC is because thats what kind of connection setup you bought with your DSL package. That brings me to my next point, running DHCP on your WAN connection can be a bitch at times and if you want to do VPN I recommend you spend a bit more a month on your connection and get a static IP address that never changes. I agree with the statement that if your going to run dual nics on server 2000/2003 use ISA for that. But at that point, you might as well put that money into a hardware firewall unless your willing to take a friggen class on ISA server. |