Jump to content

Network Connection Issues On Dell Optiplex GX620


Recommended Posts

Posted (edited)

Hi,

 

I have a handful of machines that are giving me issues. When the computer boots up its ignoring the group policy to wait for the network before allowing logon. So it is missing the MSI installers i am sending out. It takes a good few mins to get a network connection. Once connected it shows the link as 100mbs when it should be infact gigabit.

 

I have the following in the event viewer

 

The system failed to update and remove host (A) resource records (RRs) for network adapter

with settings:

 

Adapter Name : {5EE003CC-F15A-4F96-A388-FBB8AF726184}

Host Name : V105-00

Primary Domain Suffix : KPHS.com

DNS server list :

172.16.96.20, 172.16.96.21, 172.16.16.2

Sent update to server : 172.1.1.1

IP Address(es) :

172.16.98.169

 

The reason the update request failed was because of a system problem. For specific error code, see the record data displayed below.

 

For more information, see Help and Support Center at Events and Errors Message Center: Basic Search.

 

Broadcom NetXtreme 57xx Gigabit Controller: The network link is down. Check to make sure the network cable is properly connected.

 

Broadcom NetXtreme 57xx Gigabit Controller: Ethernet@WireSpeed is enabled and could not negotiate maximum link speed. Potential faulty cable or connection.

 

I have tried the fllowing

  • Change point on switch.
  • Configure port on switch to force at gigabit.
  • Reinstal windows.
  • Update BIOS
  • Update Drivers

 

The machine is a Dell Optiplex GX620 we must have about 150 of these all fine but a select few.

 

I have swapped the network port on the switch from a machine from a good known working one and still get issues.

 

I have checked DNS its all fine

 

I can also see at one point it has been ok breifly becuase some software i sent for deployment is on the machine.

 

This is driving me up the wall. Does anyone have any thoughts please?

Edited by FN-GM
  • 3 weeks later...
Posted

yep turned out to be a faulty network cable :doh:

 

What threw me was the fact that other machines worked perfectly on the same connection

  • 1 month later...

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...