|
Home > Archive > 70-216 > May 2002 > dns trouble...
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
|
|
| gtfive0 2002-05-23, 5:37 pm |
| i've tried setting up a small network for testing. its consist of three computers. i'v set one up as a domain controller, and installed active directory on it, along with dns. the other two computers so far are just windows 2000 pro with static ip address. i gave each of the computer seperate names, and i can ping each of the computers, and i can access each computer. the question/problem i have is when(on the domain controller) i enable a second network card that has access to a cable modem, my dns doesn't work on the private network, when i ping my domain controller by name, it comes back with the ip address of the cable modem, not the ip for the private network, but when i disable the connection to the cable modem, it goes back to showing the ip for the private network, and dns on the private network is fine. is there something i've missed configured that when i enable the cable modem connection my dns doesn't work right on the private network, also when i have it enabled, on the other two computers i can ping ip addresses from the internet, but i can't ping host names. anyone know what i'm doing wrong?? | |
|
|
| KScheler 2002-05-23, 10:59 pm |
| You won't believe this but I ran to the same problem today. I setup a W2k server and installed NAT. My clients can get an IP from the dhcp allocator, ping the internal NIC and external NIC of the NAT server but can go no further. The NAT server can ping the clients, it's default gateway but no further, can't ping the internet. I disable the internal NIC and the NAT server can get past the default gateway and get to the Internet. It's like it's supposed to be routing but will not route. I had this box working perfect then they moved it to another building with a different subnet/IP. Boy did that hose the NAT. Decided to wipe it & start fresh. I'm beginning to think it's best to install with only 1 NIC installed, then add the 2nd NIC. Any ideas out there? Frank? | |
| KScheler 2002-05-24, 11:21 am |
| Well, I found my cause of my problem. Bad patch cable from the Private NIC to the switch. Changed the cable and everything works like it should. Doesn't make since, thru the bad cable my clients could get IPs, ping both NICs on the NAT server but couldn't get past that. Go figure?  | |
| gtfive0 2002-05-24, 10:55 pm |
| i dont know.. still can't figure mine out.. the cables are good, and i can ping ip addresses, ip addresses of both the internal and external, plus any other ip on the internet, i just can't ping the host name, but i can disable my dns, and use internet connection sharing and everything for the windows 2000 client computers works fine, i'm not sure what the deal is, or what i might have miss configured. | |
| Slinky 2002-05-25, 12:05 pm |
| I use NAT also in this configuration, and everything works fine. On the NIC card that is connected to the private network, make sure you have the DNS IP for the private network. For example, if that computer is a domain controller and is running DNS, then type in that servers address. And for the NIC connected to the cable modem, make sure you have a DNS IP that they give you or obtain it automatically. |
|
|
|
|