Random & Frequent Timeouts

[ICTCity]

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.

[anubisrwml]

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.

[anubisrwml]

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.

[anubisrwml]

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

[ICTCity]

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

[ICTCity]

It looks like you may have some HW problem... try to change the cable first, then, if you can, change the NIC, you should have more than one NIC because of it is a server...

 

I also suggest you to download the diagnostic tool from the official website of your NIC. For example, HP has a utility to check your NIC status.

 

 

Let me know!