Good Afternoon,

 

I recently installed Windows Server 2008 R2 with AD DS and DNS - since I installed these roles however the internet is really laggy for me - downloads time out, websites time out very very frequently, and when I did ping tests, even those would randomly time out. I'm not sure why or where the hang up is but it makes it very difficult to navigate or get anything done so I'd like to find a resolution to this as soon as possible.

 

I'm fairly new to Windows Server 2008 so I'm not sure what information is needed so let me know whats needed to help troubleshoot this and I'll provide it within minutes.

 

Thanks and I hope to find a resolution soon - I'll browse the forum too - maybe this has been addressed in the past.

 

Matthew

 

PS This is attempt 3 to post this.

Hi,

 

Before going further, open task manager > RESOURCE MONITOR.

 

You have 5 TABS.

 

First of all on OVERVIEW you have 4 bars and on the right there's a small blue square which indicates the percentile of usage. Take a look if there's something high (when I say high, I mean >= 50%).

 

This EXCEPT the network. For network you have to determine first your network's speed. Let's say you have a 5M connection, if you see the 5% on the blue square, it means your bandwidth is full! (5% of 100), if you have a 1gb NIC, you will have 0,5% and so on.

 

If you think there's something unusual, go to the relative tab and check WHICH process is using your resource.

 

Let me know if you need help!

Thanks for the quick reply!

 

I did as requested but I didn't see anything over 1-4% - of course I'm running a monster of a machine -

I7 960 3.2 gHz w/ 16 GB DDR3, 7200 RPM 2TB HD, GeForce 580, and we have a T1 connection. Prior to installing the DNS and Active Directory the internet absolutely flew flawlessly. Now, like I said when I submit or do a search or try to open a page - sometimes it loads with a delay, and othertimes it gives me the classic Internet Explorer cannot display the webpage error.

 

And its often that it times out - the fact that it does work bothers me and I'm not sure where the problem could lie. I did notice another error in the server logs - "The DNS could not open the socket for 10.0.10.4" - the IP being this machines address.

 

Any other thoughts on where to begin looking?

The goal here is to setup this machine as the server for the office w/ active directory. My thoughts were also to pass DNS and internet requests through it, as it would act as the gateway for the rest of the office. I bought a book and was reading up on it, but I'm not sure what roles I need and dont need. They do want to host a website as well, both internal and external. But that's for a different topic. Right now I'd be pleased to just get the internet to work again.

Thanks for the quick reply!

 

I did as requested but I didn't see anything over 1-4% - of course I'm running a monster of a machine -

I7 960 3.2 gHz w/ 16 GB DDR3, 7200 RPM 2TB HD, GeForce 580, and we have a T1 connection. Prior to installing the DNS and Active Directory the internet absolutely flew flawlessly. Now, like I said when I submit or do a search or try to open a page - sometimes it loads with a delay, and othertimes it gives me the classic Internet Explorer cannot display the webpage error.

 

And its often that it times out - the fact that it does work bothers me and I'm not sure where the problem could lie. I did notice another error in the server logs - "The DNS could not open the socket for 10.0.10.4" - the IP being this machines address.

 

Any other thoughts on where to begin looking?

 

First post the output of:

 

ipconfig /all

 

Then try this:

 

ipconfig /flushdns

open internet explorer > delelete ALL browsing history

Try to open www.google.com (it should be SLOOOOW)

If it fails, no problem, we don't care about this.

 

Now on Internet Explorer put on the URL bar this:

http://87.248.112.181/ (this is the yahoo's IP)

 

and tell me if it is a bit faster.

Results from ipconfig /all

 

Windows IP Configuration

 

Host Name . . . . . . . . . . . . : AF001

Primary Dns Suffix . . . . . . . : appreciationfinancial.net

Node Type . . . . . . . . . . . . : Hybrid

IP Routing Enabled. . . . . . . . : No

WINS Proxy Enabled. . . . . . . . : No

DNS Suffix Search List. . . . . . : appreciationfinancial.net

 

Ethernet adapter Local Area Connection 3:

 

Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : Microsoft Virtual Network Switch Adapter

#2

Physical Address. . . . . . . . . : BC-AE-C5-60-0A-E2

DHCP Enabled. . . . . . . . . . . : No

Autoconfiguration Enabled . . . . : Yes

Link-local IPv6 Address . . . . . : fe80::214b:86a4:bff1:59ab%15(Preferred)

IPv4 Address. . . . . . . . . . . : 10.0.10.4(Preferred)

Subnet Mask . . . . . . . . . . . : 255.255.255.0

Default Gateway . . . . . . . . . : 10.0.10.100

DHCPv6 IAID . . . . . . . . . . . : 264023749

DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-15-5F-81-95-BC-AE-C5-60-0A-E2

 

DNS Servers . . . . . . . . . . . : 127.0.0.1

NetBIOS over Tcpip. . . . . . . . : Enabled

 

Tunnel adapter isatap.{027DAAA4-AB78-4820-8C20-6756C272913C}:

 

Media State . . . . . . . . . . . : Media disconnected

Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : Microsoft ISATAP Adapter

Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0

DHCP Enabled. . . . . . . . . . . : No

Autoconfiguration Enabled . . . . : Yes

 

Tunnel adapter Local Area Connection* 9:

 

Media State . . . . . . . . . . . : Media disconnected

Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface

Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0

DHCP Enabled. . . . . . . . . . . : No

Autoconfiguration Enabled . . . . : Yes

I was playing around with the ping and web searches and found something interesting. The first two pings below worked just fine - the last one I did right after I started a search on yahoo.com

 

I've never seen General Fault before...

 

Pinging any-fp.wa1.b.yahoo.com [98.137.149.56] with 32 bytes of data:

Reply from 98.137.149.56: bytes=32 time=26ms TTL=56

Reply from 98.137.149.56: bytes=32 time=34ms TTL=56

Reply from 98.137.149.56: bytes=32 time=23ms TTL=56

Reply from 98.137.149.56: bytes=32 time=131ms TTL=56

 

Ping statistics for 98.137.149.56:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 23ms, Maximum = 131ms, Average = 53ms

 

C:\Users\Administrator>ping www.yahoo.com

 

Pinging any-fp.wa1.b.yahoo.com [98.137.149.56] with 32 bytes of data:

Reply from 98.137.149.56: bytes=32 time=26ms TTL=56

Reply from 98.137.149.56: bytes=32 time=31ms TTL=56

Reply from 98.137.149.56: bytes=32 time=25ms TTL=56

Reply from 98.137.149.56: bytes=32 time=23ms TTL=56

 

Ping statistics for 98.137.149.56:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 23ms, Maximum = 31ms, Average = 26ms

 

C:\Users\Administrator>ping www.yahoo.com

 

Pinging any-fp.wa1.b.yahoo.com [98.137.149.56] with 32 bytes of data:

Reply from 98.137.149.56: bytes=32 time=50ms TTL=56

Reply from 98.137.149.56: bytes=32 time=24ms TTL=56

Reply from 98.137.149.56: bytes=32 time=27ms TTL=56

Reply from 98.137.149.56: bytes=32 time=22ms TTL=56

 

Ping statistics for 98.137.149.56:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 22ms, Maximum = 50ms, Average = 30ms

 

C:\Users\Administrator>ping www.yahoo.com

 

Pinging any-fp.wa1.b.yahoo.com [98.137.149.56] with 32 bytes of data:

Request timed out.

General failure.

General failure.

General failure.

 

Ping statistics for 98.137.149.56:

Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

It looks like the DNS is pulling the IP just fine as it should, but after that it's getting stuck somewhere. Maybe this isn't a DNS issue but something more?

Ok, let's try this:

 

Open DNS Manager, right-click the DNS server name, then click Properties. Click the Interfaces tab, you should see the IP address of your system (10.0.10.4), if not, correct it.

 

Then:

 

Open Control Panel, Network, select the Bindings tab and verify that the bindings for all protocols to network adapters exist.

 

Let me know.

It looks like the DNS is pulling the IP just fine as it should, but after that it's getting stuck somewhere. Maybe this isn't a DNS issue but something more?

 

 

I have the same though.

 

Read my "last" post regarding the binding and so on...

Ok, let's try this:

 

Open DNS Manager, right-click the DNS server name, then click Properties. Click the Interfaces tab, you should see the IP address of your system (10.0.10.4), if not, correct it.

 

Then:

 

Open Control Panel, Network, select the Bindings tab and verify that the bindings for all protocols to network adapters exist.

 

Let me know.

 

Ok in Interfaces, it's set to Listen on: All IP addresses. There is a binding for Only the Following IP addresses: And it has both my ipv4 and ipv6 listed. Should I select that?

 

Also not sure where you're finding the Bindings Tab

I also set up two forwarders to the DNS of our provider (cox) - it's also setup to use root hints if no forwarders are available. I assumed this would be necessary to pulll a FQDN. I also don't have any reverse lookup zones - will that matter?

And something that keeps bugging me - why is it when I ping from Command Prompt does it work every time flawlessly right up till I do a search or web request. At that point, it times out, gives faults and all sorts of nonsense, then once it's displayed the cannot load page error, it goes right back to pinging correctly again.

Just to make a try...

 

Change the "All ip address" to the IPv4 address.

 

run this: ipconfig /registerdns

 

restart DNS service.

 

 

Are you running any FW / AV?

And something that keeps bugging me - why is it when I ping from Command Prompt does it work every time flawlessly right up till I do a search or web request. At that point, it times out, gives faults and all sorts of nonsense, then once it's displayed the cannot load page error, it goes right back to pinging correctly again.

 

easy.

 

You have trouble with name resolution (DNS), from here the error "cannot create socket".

 

When you PING DNS is just used one time to resolve the name to IP address, once done, the result is stored in a cache.

 

When you ping and search, the DNS request is "overflowing" your bandwidth.

Ok figured out the binding thing - Alt+N brought up the advanced menu and I found it there - under network Controller 3 everythings checked so I'm assuming it's all bound there.

Ok changed the settings and restarted - also ran that ipconfig command.

 

As for firewalls I am running windows Firewall - I can disable that if necessary - I assumed since everything was configured with it on that exceptions would have been put into place automatically.

Ok after running some random tests - it *seems* like it's playing nice now - though it could just be a lucky stretch. Yahoo doesn't want to play nice but everything else seems to be working ok. I'm going to try downloading some files as well.

It looks like it's working better but I still can't seem to get more than a few pages before it goes back to what it was doing again.

Funny thing - if I watch a download, the download speed will get way up there (1-2MB/s) but then suddenly drop to 0 and hang there then start to go back up again. Perhaps this is related?

wait.

 

Do you have the same message on DNS log?

 

Can you temporarly replace your router with another one?

 

I think your problem can be related to the router... but this only if the error message has gone.

 

Windows FW is ok.

Ok question - maybe this would be easier. Is there a way to set it up so that it forwards all traffic and requests and such to 10.0.10.100 (my router) as though it wasn't here? Essentially cut out DNS from the loop and let it run like it used to? I know DNS is required for AD DS but if I can pass the buck onto the DNS servers with Cox might be easier. I don't plan on putting DHCP on this machine at all - just manage an office domain.

You know it might be my router - it's set up as static and it works just fine for everyone else in the office (They're not on the domain yet) so it appears to be functioning as expected. That being said though, since this is a DNS server what ports should I have forwarded? Right now I'm forwarding a large handful of em but maybe I missed some important ones? If it's not the forwarding, then I'm stumped - I unfortunately can't replace the router - we only have the one and it's fairly new (maybe a month or two?) - never had any issues with it in the past.

Ok I just pinged my router and this was the results.

 

C:\Users\Administrator>ping 10.0.10.100

 

Pinging 10.0.10.100 with 32 bytes of data:

Reply from 10.0.10.100: bytes=32 time=1ms TTL=64

Request timed out.

Request timed out.

Request timed out.

 

Ping statistics for 10.0.10.100:

Packets: Sent = 4, Received = 1, Lost = 3 (75% loss),

Approximate round trip times in milli-seconds:

Minimum = 1ms, Maximum = 1ms, Average = 1ms

 

C:\Users\Administrator>ping 10.0.10.100

 

Pinging 10.0.10.100 with 32 bytes of data:

General failure.

Request timed out.

Request timed out.

General failure.

 

Ping statistics for 10.0.10.100:

Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

 

C:\Users\Administrator>ping 10.0.10.100

 

Pinging 10.0.10.100 with 32 bytes of data:

General failure.

General failure.

Reply from 10.0.10.100: bytes=32 time

Well, in your network properties (DNS server), simply change the DNS from 127.0.0.1 to 10.0.10.100. I think this will help in some way, but actually I can't understand the cause of your problem...

 

Where I live it's quite late, I have to sleep a bit.

 

Keep posting, I will answer tomorrow.

 

Cheers