[fatnhairy]

This is the problem we have:

Server 2008 r2 standard on an ML350G6 4gb RAM, quad core, RAID 5 built with smart start 8.30. All drivers updated to latest version from HP.

Built server, added roles and features - Directory services, DCPROMO, DNS, DHCP.

This is an infant school and 1st time they've had a server - only server in domain

Windows updates all done - took several attempts due to problem below

Network/DNS is really flaky: network icon in taskbar constantly flashes up telling us no internet access. Run a continuous ping to the gateway and we get about 20% failure rate. Plug another PC into same network point and ping is 100%

Joining a pc to domain is nigh on impossible, if you do manage it after several attempts, logon is just as unreliable

RDP into server and every few minutes connection is dropped. Sometimes it will reconnect itself, sometimes it times out.

already reinstalled OS from scratch

HP have replaced Motherboard

googled myself silly looking for a fix. Have turned off eDNS but this hasn't fixed it

HELP PLEASE!

[john]

Have you tried newer (or older) drivers for the NIC?

[maniac]

Have you checked the cable linking the server to the switch and/or tried another one, and if possible tried another switch. It sounds to me as if it could be related to something else other than the server its self.

I know you've said another PC works fine in the network point, but if for instance the other PC had a 100mbs network card, but the server is gigabit this could make a difference.

It could also be worth forcing thse server to use 100mbs if possible if it is gigabit, just to see if it makes a difference.

[dhicks]

Originally Posted by fatnhairy

Network/DNS is really flaky

Have you tried replacing the network card? Could it be the cable? If a single wire is knackered then 100mbps would work okay, but not gigabit...

--
David Hicks

[fatnhairy]

thanks for the responses

cabling checked, swapped patch leads, tried different data points, mobo swapped out - nics on board. old drivers tried and updated to latest, firmware updated, bios flashed.

tried both network cards individually in 100mbps and 1000mbps ports on procurve switch. tried hp teaming on and off with old version and updated to latest version

used wireshark and ms network monitor with nothing obvious

used pc and laptop with 100mbps and 1000mbps nics on data points and all OK, tried server on other data points and even tried plugging into a mini switch and a 10mbps hub

[Greedz]

Would you care to post up a DCDIAG report, show us what your DC is doing... is it clean?
Anything in your event logs? Are there errors within DNS, is it failing to advertise its role as a PDC?

Edit out the bits you dont want the rest of the world to see like public IP's if any.
It should all be internal lan stuff anyway with local addressing so it shouldnt matter.

[eean]

You've definately got your clients using server 2008 as their only DNS. On the server, the DNS settings on the network card should be 127.0.0.1 (loopback) or it's own IP. Forwarders (within DNS on the server) setup to point to internet dns servers?

[fatnhairy]

Originally Posted by eean

You've definately got your clients using server 2008 as their only DNS. On the server, the DNS settings on the network card should be 127.0.0.1 (loopback) or it's own IP. Forwarders (within DNS on the server) setup to point to internet dns servers?

yes, that's how it was set.

gave up and flattened server and installed 2k3 r2 and problem gone away

thanks to all

[Greedz]

Thats a shame, 2008 Server is a sensational platform for management.