Win2003 Server cannot see network anymore

[ccarney]

I installed my first Win 2003 Server yesterday and all was perfect. Set up the DNS (set the preferred DNS for the server to itself, then forwarded to ISP DNS Servers), created a local domain and setup AD. Then, I created new users in the domain, added two PCs, setup RAS and VPN. The VPN client connections worked fine. I was basically very please with myself for the first attempt.

Then, I lost power to the DSL modem and router and couldn't reconnect to the network from the server.

I have restarted everything in all the different orders. I have changed cables, and tried different switch ports and basically tried everything I can think of.

The Win2003 Server cannot ping anything but itself and loopback. So clearly as it can't ping the router on 192.168.0.1, it can't get to the external DNS Servers for any name resolution.

The other two PCs in the domain that can ping any IP address, in or out, including the router and the Win2003 server. But as they both have the DNS set to the Win2003 server, it's not surprising they can't resolve names.

Here's the scenario:
1. DSL Modem
2. Netgear Router (192.168.0.1), also DHCP server
3. Switch
4. Win 2003 with static IP 192.168.0.2, default gateway 192.168.0.1 and DNS server 192.168.0.2
5. Two PCs (192.168.0.7 and .3) that can 'see' everything but can't get any name resolution using the 192.168.0.2

I've also tried (after setting the LAN connection to get the IP automatically instead of static) ipconfig /release and /renew but couldn't get the renew to work.

I'm guessing that this is going to be something very basic that I just don't have the experience to know to look for. Although I have checked other settings in the MMC, it seems to be a basic issue that the server can't see it's own domain devices.

Any help would be very appreciated.

 

[ricpinto]

Did you install a software firewall or activate one on the server? What about TCP/IP filtering?

 

[ccarney]

I haven't installed anything but Win 2003 Standard Edition (evaluation edition, if it makes any difference).

If there is firewall software within Win2003 then I may have activated it without knowing, but don't know where to look to find out.

As for TCP/IP filtering, do you mean the Inbound and Outbound Filters defined in RRA -> <fileserver> -> IP Routing -> General -> <Ethernet Adapter> -> Properties?

Do you want the list of Inbound and Outbound settings?

In the IP Routing -> General tree, I believe that something has changed from before. There are four items shown: Loopback, Internal, Intel Pro Adapter Onboard (the LAN connection), and Intel Fast Ethernet LAN Controller PCI Slot 1 (unused). When all was working, the Internal listing had an IP Address of 192.168.0.5 and status UP. It is now Not Available and Unknown for those settings.

What is the Internal setting? Could this be related to the problem?

 

[ccarney]

A bit more information:

In the TCP/IP properties of the LAN connection in Network Connections, the firewall is disabled and the TCP/IP Filtering is disabled. TCP, UDP and IP settings are set to Permit All.

 

[ccarney]

Some more info in trying to narrow down the problem:

I altered the DNS Servers on one of the domain PCs to be the ISP's, and ran diagnostics. Everything passes. However, it is not possible to ping the win2003 server on the domain. I can still ping the other domain devices, including printer, PC and router.

On the other domain PC, I have left it and the diagnostics fails on the DNS Server connection - it can't ping the win2003 server on 192.168.0.2. However, it can ping the other devices including printer, PC and router.

Does this confirm that it is the win2003 IP configuration that is blocking anything from being sent or received?

And I know I said in the first message that the other PC's could see the server - they could yesterday but can't today. Obviously, it's not magic and something has been modified along the way as I have been trying to sort it out all day. I did find that DHCP Relay Agent was enabled and disabled that. I re-checked the route tables, the zone data, the metrics, the static IP (tried another value), the cables, disabled the second NIC. I'm convinced it will be something simple that is taking all of my time, but I'm actually pleased it hasn't worked smoothly as I'd rather be forced to get into all of this now than when it really counts.

 

[ccarney]

I realize that I'm talking myself through the problem, but maybe it will help someone else later.

I've swapped over to the second NIC and all is happy again. The router/DHCP assigned an IP address, I've since made it a reservation, everything can see everything else and I'm back to where I was before, verifying VPN.

If anyone has any ideas as to why the other NIC might have suddenly stopped blocked everything, I'd appreciate the info. If I have time later, I may go back to it and see if I can't correct it.

 

[LawnBoy]

you stated the NIC was showing &quot;Not Available&quot;. This means it has been:

A. disabled OR
2. has a corrupted driver OR
III. has a hardware problem

 

[ccarney]

It wasn't actually one of the two network adapters that was showing Unavailable. They were both enabled (or disabled when I disabled them). When I had first completed the 2003 installation, the first connection worked correctly. Sometime later, after restarting, it stopped being able to see the rest of the network.

They could both connect to the network, although the first couldn't see anything. I could set a static IP for the first one, but it wouldn't accept a DCHP IP address. When I switched to the second one, everything was ok.

It was the listing above them named 'Internal' that changed to Unavailable and I haven't had a chance to find out what 'Internal' represents. But it's still in that state and the connection works fine so I've more or less excluded it anyhow.

 

[GlenJohnson]

Try a pathping to someone outside and see what drops the ball. Have you tried some other basics? Ipconfig /all on the 2003 server? Have you posted this on the Windows.net 2003 forum? Good luck.

Glen A. Johnson
&quot;Fall seven times, stand up eight.&quot;
Proverb

Want to get great answers to your Tek-Tips questions? Have a look at FAQ219-2884

 

[ccarney]

I started with all of the basics I could think of, including changing cables. I'll try the pathping tomorrow and see what it tells me.

The ipconfig/all display indicated the correct IP address, DNS Server and default gateway.

But the ipconfig/renew initially failed to get a new IP address (although it eventually did), so that's pointing to an issue with the router which is the DHCP server. It didn't make any difference if I used static or dynamic IP so that probably elimates the DHCP functionality from the problem.

That's one reason I'm thinking that the block might be related to the router-server link.

I would think that the key is the fact that all other devices on the LAN could see the server, the router and the outside world, so the router/network settings in general are not the problem.

When I activated the second NIC on the Win2003 server, everything worked without changes, which suggests that the general Win2003 settings are not the problem.

That's narrowing it down to the NIC-to-router comms in my mind. I'll mess around with some more eliminations - it's just a matter of time before I've reduced it to whatever's causing the problem.

Thanks.