Assigning IP address makes computer lose connectivity

[packdragon]

I installed a new computer and joined it to the domain. When it's set to have an IP address assigned to it automatically, everything is fine, it is able to see the network and ping other machines. The second I set the IP address to something specific, it can no longer see the other machines in the network. It only sees itself as the only member of the domain. As soon as I change it back to Automatic IP it sees the other computers again.

I thought maybe there was an IP conflict, but even when I assign it the exact same IP that had been given by DHCP it no longer can ping other machines except itself.

What is causing this? Is there a setting that I am overlooking? It's going to be a web server so it has to have a static IP. How do I check for IP conflicts? Nbtstat -n isn't showing anything meaningful to me. I need to know what other machine it's conflicting with. Ideas? Tips?

 

[arteus]

Could you please provide some specifics ie workstation OS, subnet details and type of domain (NT 2000). Also the protocols bound to the adaptor.

Regards

 

[fuunstatic]

you may have tried this however, have you tried pinging the network with the ip address you want to use, in case it is in use by someone else

when you set your card to a static ip are you able to ping the default gateway etc. and if that works ok can you ping its name

the NIC that is in use is it an onboard one (ie part of the moptherboard) or a seperate NIC card?

not being able to to "see" other machine suggests you are on a different network or DNS settings are wrong



"Work to live, don't live to work"

"The problem with troubleshooting is that sometimes it shoots back"

 

[GiaBetiu]

If there wil be an IP conflict Windows will announce this immediatelly.
Try if ping from that computer to the gateway or other computer is working.
Check your DHCP options, see what you are sending more to other computers via DHCP.


Gia Betiu
gia@almondeyes.net
Computer Eng. CNE 4, CNE 5, MCSE Win2K
new:

http://www.almondeyes.net

(just started)

 

[packdragon]

Ok everyone, get ready to point your fingers and me and laugh. Turns out I was physically plugged into the wrong subnet. I was able to join to the domain of the other subnet, which fooled me into thinking I was connected correctly. After switching the machine to a network cable connected to the right subnet, I was able to assign an IP and it was still able to see the other boxes in the network.

Thanks for your input guys!

 

[packdragon]

Next problem, same computer. This time it's DNS-related. The primary DNS lists this computer both in the domain folder and in the Reverse lookup. However the secondary DNS server, which resides in a different subnet, only has it listed in the domain folder. It is missing from the Reverse lookup. I right-clicked on it and selected Transfer From Master, but this doesn't seem to do it.

This is a Windows 2000 mixed-mode domain with active directory domain controllers. The problem computer resides in subnet B, with its DNS entry in an active-directory-integrated zone. I need the computer to be able to see subnet A (and vice versa). Subnet A has a DNS server that hosts a secondary zone of subnet B's domain and reverse lookup.

I am currently logged into subnet A. When I try to ping the problem computer by name, it does resolve to the correct IP address, but the request times out. Is this indicative of some other problem?

I'm still learning all there is to know about DNS... which is a lot. Any insights would be greatly appreciated!

 

[packdragon]

Ok nevermind, problem solved. Turned out to be a firewall issue. The IPs being used were not declared as being part of the DMZ, so that's what was preventing me from pinging it from my machine.