[URGENT] SBS 2003 DNS issue

[seedubya]

I think it's a DNS issue anyway.

SBS 2003 configured with a single NIC. Server does everything except default gateway. Exchange is configured as store only.

Earlier today, having worked flawlessly since installation 5 or 6 years ago it started to get flaky. Clients couldn't access the internet or email. File shares stopped working, some clients dropped off the network entirely.

All services are running, nothing unusual in EventVwr. Most clients can get an address from the DHCP but some can't. Any client that does get an address can't connect to AD resources or the internet. Can ping by IP address though. The server IS the DNS server for the network and is pointing to itself for DNS also. The few working DHCP clients can ping the server and are assigned it's address as their DNS server. Cannot resolve either internal or external addresses though. If I manually set client DNS to Google, internet and email works just fine.

Root hints seem to be set up correctly, I changed the forwarders just in case but still no joy.

Any and all help gratefully accepted. This is urgent. I need to have it working in the next 12 hours or so and it's 8pm here and my head tech is on paternity leave!

 

[viperit]

Hi,

Couple of quick questions - can the server resolve DNS?

Can you output a ipconfig /all from the server and a desktop and post it on the forum?

Thanks, Tom

 

[TAPtech]

I would also check the switch.

 

[Simmy]

I would also check the switch.

That was my first thought too. Something hardware related (switch/NIC) if the server has been untouched and working perfectly for the past 5 years.

 

[seedubya]

Hi,

Couple of quick questions - can the server resolve DNS?

Can you output a ipconfig /all from the server and a desktop and post it on the forum?

Thanks, Tom

Yes, the server can resolved DNS queries just fine.

Server

Microsoft Windows [Version 5.2.3790]
(C) Copyright 1985-2003 Microsoft Corp.

C:\Documents and Settings\Administrator>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : SERVER01
Primary Dns Suffix . . . . . . . : XXXXXXXXXX.local
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : XXXXXXXXXX.local

Ethernet adapter Server Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit Ethernet
Physical Address. . . . . . . . . : 00-1E-C9-2D-70-0E
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.1.100
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.254
DNS Servers . . . . . . . . . . . : 192.168.1.100
Primary WINS Server . . . . . . . : 192.168.1.100

I can't provide workstation output right now because I'm back home and none of the clients are online.

I would also check the switch.

I'll bring a spare switch with me in the morning.

 

[YeOldeStonecat]

Servers IP settings seems correct.....it uses itself for DNS, and nothing else...nothing..just itself. That's good.

Assuming DNS fowarders are going to something it can get good response to?

But you say some workstations can't pull an IP...that sounds more like a connectivity issue, agree...possibly a failing switch.

Make sure someone didn't uplink some broadband router to the network using a LAN port...trying to use it like an access point. Can create a rogue DHCP service on your LAN if they didn't take the steps to configure it properly to run just as an AP. I see this often..very often.

Run an IPCONFIG /ALL from every workstation and compare. Post here even (or at least post an IPCONFIG /ALL from a failing workstation if you can).

 

[axem56]

I had similar issues with an SBS 2003 server, disabling the firewall resolved the issue. Now to find out what is causing the issue with the firewall.

 

[YeOldeStonecat]

I had similar issues with an SBS 2003 server, disabling the firewall resolved the issue. Now to find out what is causing the issue with the firewall.

He stated it was configured with single NIC. With Server 2003 the firewall service literally cannot start unless 2x or more NICs are enabled and active.
If you're running SBS single homed...should always disable the unused NIC(s).

 

[seedubya]

I had similar issues with an SBS 2003 server, disabling the firewall resolved the issue. Now to find out what is causing the issue with the firewall.

This was the problem.

He stated it was configured with single NIC. With Server 2003 the firewall service literally cannot start unless 2x or more NICs are enabled and active.
If you're running SBS single homed...should always disable the unused NIC(s).

It is configured with a single nic. There isn't even a second nic in the machine, never mind enabled. Yet somehow, yesterday afternoon, the firewall was switched on. I say "somehow". It mysteriously coincided with a Quickbooks tech logging in to solve some random QB problem.