Slow/Unresponsive Network

[BBousman]

Hello,
Recently we had a major network problem where we couldn't access e-mail and network programs/folders. I managed to get them back online and working but our network seems to be running slow and won't connect to certain servers/folders at times. Also, if it does connect, it takes FOREVER to connect to it. Before this network "crash" happened the only thing changed on the server was that the "Windows Firewall: Protect all Network Connections" option was turned off. I turned it back on and that's when everything came back online although most of our windows firewalls are still turned off for whatever reason. Does anyone know how I could go about solving this little catastrophe? Thanks in advance!

Brett

 

[karmic]

First thing, download the support tools, install it on your server(s).

http://www.microsoft.com/downloads/...78-8BE1-4E81-B3BE-4E7AC4F0912D&displaylang=en

from a dos prompt, run dcdiag /v and netdiag /v and check for warnings or failures. Post the results. using >filename.txt will export results to a file.

Run nslookup from a dos prompt on the servers and a couple of workstations and post the result.

I always disable the windows firewall and opt for a decent hardware firewall solution. Usually the pix and close ports that way.

~ K.I.S.S - Don't make it any more complex than it has to be ~

 

[BBousman]

When I run the NSLOOKUP on the server this is what I get:
*** Can't find server name for address 209.253.171.61: Non-existent domain
Default Server: UnKnown
Address: 209.253.171.61

When I run NSLOOKUP on any workstation, I get this:
*** Can't find server name for address 209.253.171.61: Non-existent domain
*** Can't find server name for address 209.253.171.62: Server failed
*** Default servers are not available
Default Server: UnKnown
Address: 209.253.171.61

When I ran the DCDIAG, this is an error I got:
Testing server: Default-First-Site-Name\SERVER02
Starting test: Connectivity
* Active Directory LDAP Services Check
The host ba22d680-6a60-4474-836c-64ded53f5c19._msdcs.uelnertool.local could not be resolved to an
IP address. Check the DNS server, DHCP, server name, etc
Although the Guid DNS name

(ba22d680-6a60-4474-836c-64ded53f5c19._msdcs.uelnertool.local)

couldn't be resolved, the server name (server02.uelnertool.local)

resolved to the IP address (192.168.0.253) and was pingable. Check

that the IP address is registered correctly with the DNS server.
......................... SERVER02 failed test Connectivity

When I ran the NETDIAG, this is what I got:
Testing DNS
[WARNING] The DNS entries for this DC are not registered correctly on DNS server '209.253.171.61'. Please wait for 30 minutes for DNS server replication.
[WARNING] The DNS entries for this DC are not registered correctly on DNS server '209.253.171.62'. Please wait for 30 minutes for DNS server replication.
[FATAL] No DNS servers have the DNS records for this DC registered.


I'm guessing my DNS is messed up, I'll see if I can try to figure out how to fix it but if anyone knows how please post and let me know. Thanks in advance!

 

[karmic]

So it's safe to assume you're running a 192.168.0.X subnet?

You have some DNS issues... Check your dhcp scope and ensure your DC is the first address in the list, it looks like you're resolving to the isp dns servers. This won't work. if your server is 192.168.0.253, then make it the only dns server under scope options. What else do you have under scope options?

Also, make sure the server has itself as the first (and only) dns server under "network connections"



~ K.I.S.S - Don't make it any more complex than it has to be ~

 

[BBousman]

Yeah that's the subnet we're running.

When I opened up the DHCP Manager, there was is no server listed under there so I can't really tell you what the scope is.

When I looked under Network Connections, the only thing listed there is the Server Local Area Connection. When I look at the TCP/IP settings of it here's what's listed:

IP ADDRESS: 192.168.0.253
SUBNET MASK: 255.255.255.0
DEFAULT GATEWAY: 192.168.0.1
PREFERRED DNS SERVER: 209.253.171.67
ALTERNATE DNS SERVER: 209.253.171.68

Those DNS server's listed are the ISP DNS Servers. I'm not the one who set our network up and from the looks of it they weren't too bright on it. I'm not too familiar with setting up a network but I can tell this is wrong. I did manage to get things working better this weekend though. I configured all the client PC's to have their PREFERRED DNS SERVER set to 192.168.0.253 and that seemed to solve a lot of problems but I'd like to fix this so it works like it's supposed to.

 

[karmic]

Ok, couple of more questions before going to far. Is this a domain controller you're working with or a member server??? are the workstations logging onto the domain or just sitting in a workgroup?

Is DNS installed on the server? Under admin tools do you see a couple of icons relating to active directory?

It sounds like your firewall is doing the addressing for your network. In a good domain setup, DNS is running on the server and the workstations are carrying the primary DNS 192.168.0.253. The servers first DNS address should be 192.168.0.253. DHCP should be running on the server as well as WINS.

If DNS is installed on the server, do you see your workstations listed?

~ K.I.S.S - Don't make it any more complex than it has to be ~

 

[BBousman]

Yeah we're working with a domain controller. The workstations are logging into a domain, not a workgroup.

There's a DNS manager that I can open so I'm assuming it's already installed. Yes I see those icons under admin tools.

I don't see any workstations listed under the DNS manager.

 

[BBousman]

Okay so here's a little update. I got the dcdiag and netdiag to verify my DNS once I set the preferred DNS server to 192.168.0.253 and changed the NetBIOS Setting to Default instead of just Enabled so once I restarted the Net Logon Service, it worked.

However, when I tried to add the server to the DHCP Servers under the DHCP Manager, it said it wouldn't connect because the DHCP Server Service wasn't running so I went into services and started it but it immediately turned it back off, any clue why this is happening and what I can do to fix it?

Also, our Linksys router has a setting called DHCP Server which has the following settings:
- Enabled
- Starting IP Address: 192.168.0.130
- Max # of Users: 50
- Client Lease Time: 0 (One Day)
- WINS: 192.168.0.253
Would this have something to do with our DHCP messing up? Should I have this enabled or not?

 

[Titleist]

BBousman,

You should install the DHCP service on one of your servers, authorize and configure it. Turn off the DHCP service on the Linksys and give the workstations a reboot to obtain new IP addresses.

John

 

[BBousman]

John,
Alright, I'll give that a try this weekend. We run full-time around the clock except on weekends so I can't just shut the system down in the middle of the work week but I will definitely give that a try. Thanks!

BBousman