UH OH! Lost all network connectivity on win2k server 3

[dpresley]

I set up a win2k server, made the domain name and thought i had done it JUST like the other one that i had successfully set up. HOWEVER at some point as i was setting up something (i have no idea what it was as this is 3 weeks ago and i'm JUST now able to get back to fixing it) and i lost all connectivity. No internet usage or anything. It's a bit frustrating.
I make no beans about it, i am a psuedo network and system administrator! haha

any help would be appreciated

Dave

 

[ahalecitrix]

If it completely lost all connectivity it may be as simple as a hardware problem with the NIC or a driver issue with the NIC. Try uninstalling and reinstalling the driver for the NIC and make sure you double check all of the network / protocol settings to ensure they are correct.

 

[dpresley]

Actually i think i may have been an active directory issue... i have another server on the same network. I'm going to try to make this one a child? god help me!!!

 

[ahalecitrix]

Just make sure that when you run dcpromo you have full network connectivity and that the second domain controller becomes a domain controller in the exisiting domain. You do not want to create a new domain.

 

[Stevehewitt]

Can you give some more info? Can you Ping? If not are you sure your routing tables/IP Addresses/Subnets are setup correctly? If your just trying to connect via DNS Names try the IP's, if they work then you have a DNS problem.

Can you explain in a bit more detail?

Steve Hewitt

 

[dpresley]

Well, the thing is that it's not seeing ANYTHING on the network except itself. I removed active directory. All the DNS, subnet, gateway and IP numbers are set. Are you saying that i need to set up DNS somewhere else?

I tried to start active directory with the new server acting as a child directory, but it couldn't find the main domain. BUT when i checked the IP addy settings i put in one that was already in use and it saw it. When i ping the new server i get a timeout.

 

[dpresley]

Here's the skinny on the network i have set up.
80 win2k computers. 1 win2k server. I am adding another server. Everything else on the network is groovey, but i cant get the new server to see anything else on the network. It WAS seeing everything just fine. Something happened (i have no idea what) and it wont see anything anymore. I had set up active directory and created a new domain. I thought that might be the problem, so i removed the active directory with the dcpromo command. Still no luck. I've verified that the ip subnet etc are all good. still no luck.

-Dave

 

[Stevehewitt]

OK. So it can't ping? I assume you have tried various machines, to and from the new server? If you have and have a timeout are you certian you are using the correct NIC on the server (if you have multiple), the LED's are on the NIC and the Switch/Hub and the cable is correct. Use a cable tester on the cable if you have one. If not just replace it with some patch cable. If there is still a problem try another NIC.

Failing all of those I would look at a Windows software issue. Look at the event logs, see if you can see anything. Also - what manufacturer is your new server/old server/infrastructure?

Steve Hewitt

 

[dpresley]

Well, i've tried various machines on the cable that the new server is on now. They all work. Just seeing whats going on i would say i that it's a server software issue. Just me setting SOMETHING up wrong. There is only one NIC on the new server. The reason i think it's working is because when i change the new servers ip addy, to one that is already being used, it rejects it. It says that THAT IP addy is already being used on the network. It's weird tho because i cant ping to or from the new server.
As far as what the infrastructure is? HA! 6 d-link switches and a d-link router. I guess just a big mesh network. I had formerly had it set up as a big peer to peer network. The servers are 1.8 ghz, 1gig ram, 40 gig hd. Just your basic overloaded computer. Nothing fancy.

 

[dpresley]

Okay... in the System event log, there are an assload of DNS related errors.

there are a few DHCPserver errors
a TON of netlogin errors..
"registration of the DNS record "insert name here" failed due to:
DNS server was unable to interpret format"


hope this helps!
-Dave

 

[Stevehewitt]

Weird! OK, the old server cannot ping the new one & vice versa? Right. But anything else CAN ping the new server and the old server?! Thats weird.

OK, try removing the old server NIC, booting it up. Shut down again and re-instert the NIC. Reinstall drivers etc and try to recongig TCP/IP.

Also, are you using DHCP?

Steve Hewitt

 

[dpresley]

Everyone with the exception of the NEW server can ping to and from the old server. NOONE can ping the NEW server and the new server can not ping anyone. haha.. sorry if that was confusing for ya.

-Dave

 

[Stevehewitt]

So are you using DHCP, if so - is the new server using it?

Also, have you tried the NIC advice I gave?

Steve Hewitt

 

[tcambridge]

Do you have another NIC that you can replace the old one with? Seems like that's the root of your problem, since everything else on your network is fine, connectivity-wise.

Good Luck!

Tim
Certified AND Qualified

 

[Stevehewitt]

I agree. My last post was going to be a last attempt before looking into the MS KB about the problem!!! It must be the NIC. You know the cable is fine, and TCP/IP is a relativility simple protocol to setup. Just because the server realised the IP address is already in use does not mean that the NIC is fully working. Try to re-load it (as in my last post.) If that doesn't work, a new NIC should do it.

If that doesn't work, take your server to the nearest window, and throw! ;-)

Steve Hewitt

 

[GiaBetiu]

Whatever,.. i will ask basic things.
What is the answer of ipconfig /all on the new server?
What is the asnwer of ipconfig /all on the old server?
Just then we can have an image about your IP configuration there.
As about a NIC error, possible too.

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

http://www.almondeyes.net

(just started)

 

[dpresley]

Okay, here's the update. I felt like i messed setting something up in configuring the server SO i just reinstalled. Nothing was on it yet, so i didn't lose anything. I set it up and made it a part of the old servers domain, and viola! All is well. Connectivity is restored. All the ip, subnet, etc is as it was before.

I shoulda taken a left turn at Albequerque!

Thanks!

-Dave

 

[dpresley]

Stevehewitt, I dont beleive i'm using DHCP. Know any good sites that will explain it? To be honest, i dont even have the faintest as to what it is!


Like i said. I AM a psuedo network and systems admin! haha
I appreciate you guys and this site more than you know as it is helping me with the pretty steep learning curve that IS network and systems admin.

THANKS!
-Dave

 

[GiaBetiu]

Have a look on my site in the article about DHCP. Is an intro. Currently, is almost released a version about some special features from Windows 2000. I hope that soon i will add that information too.

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

http://www.almondeyes.net

(just started)

 

[Stevehewitt]

Don't worry, we are all learning about network every day!

Basically, DHCP is when you have a server (or sometimes a router, JetDirect or network attached storage!) which "sends" (allocates) IP addresses to computers on a network. You don't need to know the ins and outs of it. Windows doesn't come with it already configured, so unless you have already enabled it DHCP won't be running.

Sounds like your having fun! I agree with GiaBetiu though, go to command prompt (type cmd in the "Run" box in the start menu) and type in IPCONFIG on both servers to make sure they are on the same subnet and IP range. You'd be suprised how often this problem happens and its an TCP/IP config problem.

Thinking about your comments that you think its a Win2k Server mis config - I doubt it. I can't think of anything that Win2k can do to stop a server from pinging it without some sort of third party software (e.g. ISA Server).
Make sure that the new server has an Computer account on the domain controller, your using the correct cable (I assume RJ45 CAT5e cable. Ensure its not something dodgey like cross over! )
I can't see how a Win2k mis configuration problem would prevent pinging. Whilst in command prompt type in ROUTE PRINT to see how your routing table is setup. If you need help send a snap shot to my email. administrator@timbertradinguk.com

Its sounds very, very much like a TCP/IP or a NIC problem, not Win2k. I strongly recommend that you try another NIC in the server on a different PCI slot and try to make it a different make. (E.G. if your using NetGear try a HP one.)

Hope this helps.

Steve Hewitt