To be sure if the on board network port is faulty or it's just an operating system issue, could you please install any of the verified OS that is listed on page 8 in the user guide.
as per your directions, I installed Windows Server 2016 and additionally run the ePSA build 4304.29
The Network is still not connecting. LEDs on RJ45 are off. I am using the same cable and switch port connecting to the PCIe working card:
I installed a PCIe NIC, connected to Internet and using Device Manager initiated a driver update for the onboard NIC. A driver was found on line, downloaded and installation started. Then a window popped: Windows encountered a problem installing...This device can not start (code 10).
Just so we can test the nic against the network being the issue, would you try a couple things for me?
Enter System Setup (F2) and confirm that the NIC ports are enabled on the Integrated Devices screen
Restart the system and check for any system messages pertaining to the NIC controller. Do you see anything?
Lastly, after that, connect the T30 directly to a laptop or desktop and see if you are able to ping between the two, if not try another known good working cable, if that still doesn't work then it would look to be a hardware issue with the motherboard.
I confirm that the integrated NIC is enabled under BIOS, System Configuration. I verified several times during the troubleshooting process.
Regarding the ping, I do not have an IP address to ping for a non working NIC.
The integrity of the ethernet cable and Network connectivity is proven as I am using the same cable to connect the PCIe card in the same T30, which works with any problem. I just move the cable end from the PCIe jack to the integrated NIC jack (both on the rear panel). The first work, the second do not work.
At this point, in my opinion there is a motherboard hardware issue. Do you know hat would be the replacement process?
I can see that you have been corresponding with the email agent for a motherboard replacement. I'll leave the agent to do the dispatch and do reach out to us if you need any further help.
I have 4 dell poweredge t30 server in my firm. I already setup wake on lan in my optiplex 5060 model and it is woring fine. With the same configuration in my t30 server won't turn on and the NIC led is blinking when shutdown.
(Note : already disabled deep sleep controll and enable wake on lan in bios)
bios updated to 1.5 version still not working.
Is there any bug wih the model or further configuration changes are needed?
“Based on my research,Windows Server 2016 supports Wake on LAN feature.
>>If Yes, does WOL supported for S3, S4 and S5 power states ?
WOL is supported only from sleep (S3) or hibernation (S4) states in server 2016. Windows Server 2016 cannot be remote-started using Wake-on-LAN from the S5 state.
For more details, please refer to the following link:
In the S5, or shutdown, state, the machine has no memory state and is not performing any computational tasks.
The only difference between states S4 and S5 is that the computer can restart from the hibernate file in state S4, while restarting from state S5 requires rebooting the system.
State S5 has the following characteristics:
Power consumption Off, except for trickle current to devices such as the power button.
Software resumption Boot is required upon awakening.
Hardware latency Long and undefined. Only physical interaction, such as the user pressing the ON switch, returns the system to the working state. The BIOS can also awaken from a resume timer if the system is so configured.
DELL-Joey C
Moderator
•
4.1K Posts
0
May 7th, 2020 23:00
Hi,
To be sure if the on board network port is faulty or it's just an operating system issue, could you please install any of the verified OS that is listed on page 8 in the user guide.
https://dell.to/2zoD9cE
Also please run the ePSA test on the server, following the guide on page 86.
vectorsec
4 Posts
0
May 8th, 2020 08:00
I will do. Thankl you Joey!
Sergio
vectorsec
4 Posts
0
May 8th, 2020 11:00
Hi Joey,
as per your directions, I installed Windows Server 2016 and additionally run the ePSA build 4304.29
The Network is still not connecting. LEDs on RJ45 are off. I am using the same cable and switch port connecting to the PCIe working card:
I installed a PCIe NIC, connected to Internet and using Device Manager initiated a driver update for the onboard NIC. A driver was found on line, downloaded and installation started. Then a window popped: Windows encountered a problem installing...This device can not start (code 10).
The ePSA ended with "All test passed"
Waiting for more suggestions...Thank you!
DELL-Chris H
Moderator
•
9.7K Posts
0
May 8th, 2020 11:00
Vectorsec,
Just so we can test the nic against the network being the issue, would you try a couple things for me?
Enter System Setup (F2) and confirm that the NIC ports are enabled on the Integrated Devices screen
Restart the system and check for any system messages pertaining to the NIC controller. Do you see anything?
Lastly, after that, connect the T30 directly to a laptop or desktop and see if you are able to ping between the two, if not try another known good working cable, if that still doesn't work then it would look to be a hardware issue with the motherboard.
Let us know what you see.
vectorsec
4 Posts
0
May 8th, 2020 12:00
Chris,
I confirm that the integrated NIC is enabled under BIOS, System Configuration. I verified several times during the troubleshooting process.
Regarding the ping, I do not have an IP address to ping for a non working NIC.
The integrity of the ethernet cable and Network connectivity is proven as I am using the same cable to connect the PCIe card in the same T30, which works with any problem. I just move the cable end from the PCIe jack to the integrated NIC jack (both on the rear panel). The first work, the second do not work.
At this point, in my opinion there is a motherboard hardware issue. Do you know hat would be the replacement process?
Thank you Chris!
DELL-Chris H
Moderator
•
9.7K Posts
0
May 8th, 2020 13:00
Would you private message the svc tag to us? That way we can look at what options we have.
Thank you.
DELL-Joey C
Moderator
•
4.1K Posts
0
May 11th, 2020 03:00
Hi @vectorsec
I can see that you have been corresponding with the email agent for a motherboard replacement. I'll leave the agent to do the dispatch and do reach out to us if you need any further help.
sajanraj
1 Message
0
March 27th, 2021 02:00
I have 4 dell poweredge t30 server in my firm. I already setup wake on lan in my optiplex 5060 model and it is woring fine. With the same configuration in my t30 server won't turn on and the NIC led is blinking when shutdown.
(Note : already disabled deep sleep controll and enable wake on lan in bios)
bios updated to 1.5 version still not working.
Is there any bug wih the model or further configuration changes are needed?
Please help someone with this model.
DELL-Young E
Moderator
•
5.4K Posts
0
March 28th, 2021 20:00
Hi, As for S5, Windows 2016 does not support WOL I’m afraid. Please see below.
https://dell.to/39mDDzn
“Based on my research,Windows Server 2016 supports Wake on LAN feature.
>>If Yes, does WOL supported for S3, S4 and S5 power states ?
WOL is supported only from sleep (S3) or hibernation (S4) states in server 2016. Windows Server 2016 cannot be remote-started using Wake-on-LAN from the S5 state.
For more details, please refer to the following link:
https://dell.to/3fnpdmw
“
Also please see below more for S5 :
System Shutdown State S5
In the S5, or shutdown, state, the machine has no memory state and is not performing any computational tasks.
The only difference between states S4 and S5 is that the computer can restart from the hibernate file in state S4, while restarting from state S5 requires rebooting the system.
State S5 has the following characteristics:
Power consumption
Off, except for trickle current to devices such as the power button.
Software resumption
Boot is required upon awakening.
Hardware latency
Long and undefined. Only physical interaction, such as the user pressing the ON switch, returns the system to the working state. The BIOS can also awaken from a resume timer if the system is so configured.
System hardware context
None retained.