Ubuntu-Certification

[SOLVED] Feedback on the DELL Precision T5600: NO NETWORK

Asked by JD Gascuel

I have four brand new (2013/10) T5600. Boot & install Ok. BUT NO NETWORK CONNECTION !

Bios version = A11. 16GB. 2x Intel E5-2609.

More precisely: the e1000e.ko module loads automatically. The wired connection is detected. ifconfig tells it is up and running. A few bytes are reported Rx and Tx, with no errors.

ping <some-nearby-ip> never get any replied packet (100% loss). ssh, http, dns does not work either.
BUT arp -an confirm that ethernet packets where successfully exchanged, as my computer do know the MAC address on the nearby machines.

----------- Edited -------------
SORRY !!!
The machine is working perfectly well and smoothly. I just did not figure the IT team added a DHCPsnooping protection on our network switches, disabling packet routing (except broadcasts) until a valid DHCP request was received and processed by the machine... leading to the exact symptome described above. Solution: just declare the MAC address to our network infrastructure...

Question information

Language:
English Edit question
Status:
Solved
For:
Ubuntu-Certification Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Po-Hsu Lin (cypressyew) said : 		#1

Hello,

Can you run these command in your terminal (ctrl + alt + t):
uname -a
lspci -nn | grep Eth -a5

And paste the result back here?
Thanks!

Revision history for this message
Launchpad Janitor (janitor) said : 		#2

This question was expired because it remained in the 'Needs information' state without activity for the last 15 days.

Revision history for this message
JD Gascuel (jean-dominique-gascuel) said : 		#3

----------- Edited -------------
SORRY !!!
The machine is working perfectly well and smoothly. I just did not figure the IT team added a DHCPsnooping protection on our network switches, disabling packet routing (except broadcasts) until a valid DHCP request was received and processed by the machine... leading to the exact symptome described above. Solution: just declare the MAC address to our network infrastructure...

Revision history for this message
Po-Hsu Lin (cypressyew) said : 		#4

Problem solved, set status to "Solved"