Unsolved
This post is more than 5 years old
3 Posts
0
36970
July 28th, 2013 11:00
R210 W2K12 Remote Desktop/Ping issues
I have a new PowerEdge R210 II running Windows Server 2012. It has two Broadcom BCM5716C NetXtreme GigE NICs, one of which is disabled. It is connected to another R210 running Windows Server 2008.
If I ping the 2008 box from the 2012 box, everything is fine. I don't get any dropped pings, and the response time is always <1ms.
When I ping the 2012 box from the 2008 box, I get many Request timed out mixed in with successful pings. Usually I will get a bunch of timed out in a row, then it will work for a while.
Attempting to connect a remote desktop to the 2012 box fails most of the time, but not always. Sometimes it connects, allows a login, then disconnects after a random amount of time. Sometimes it allows me to click a few things, sometimes it disconnects as soon as the mouse is moved, sometimes it disconnects immediately.
If it didn't let me connect at all, I would figure a firewall issue was to blame, but it behaves the same with firewall enabled or disabled.
I have updated the NIC firmware and drivers on both boxes. I have replaced the cables and switch between the two machines. I have added a third box to the group, which can connect just fine to the 2008 box, but has the exact same issues connecting to the 2012 box.
Any help at all would be greatly appreciated.
0 events found
Daniel My
12 Elder
•
6.2K Posts
0
July 28th, 2013 12:00
Hello johnlarson
Perform a continuous ping to the loopback address and see if you experience any timeouts. ping -t 127.0.0.1
If you encounter timeouts then there is likely a software issue. If there are no issues then move the cable over to the other LOM interface and perform your tests again, there may be a bent pin on the connector.
Thanks
JohnLarson
3 Posts
0
July 28th, 2013 12:00
Daniel,
Thanks for your reply.
Pings to 127.0.0.1 as well as 192.168.3.11 (its local ip address) work fine, as do pings from this box to another. It's pings to this box from another that fail:
Reply from 192.168.3.11: bytes=32 time<1ms TTL=64
Reply from 192.168.3.11: bytes=32 time<1ms TTL=64
Request timed out.
Request timed out.
Request timed out.
Reply from 192.168.3.11: bytes=32 time<1ms TTL=64
The Remote Desktop issue is strange, because it won't connect, won't connect, then it does connect, but drops. I think it has to be a networking issue, most likely the NIC, but I'm not sure what to check.
John
Daniel My
12 Elder
•
6.2K Posts
0
July 28th, 2013 13:00
Test the other interface on the LOM so that we can rule out a problem with that interface.
JohnLarson
3 Posts
0
July 28th, 2013 14:00
Daniel,
I moved to the second interface and everything is working. No missing pings and Remote Desktop is working fine.
I have four of these R210s. One is about a year old and works fine. But two of the new ones both have problems with the first interface. I haven't tried the last one yet.
Thanks for your help.
John
Daniel My
12 Elder
•
6.2K Posts
0
July 28th, 2013 14:00
It could be something odd with iDRAC port sharing. Check to see if the iDRAC is set to share interface LOM 1. If it is then turn it off and see if the issue still occurs.
I suspect either an odd issue with port sharing, or really bad luck with receiving two systems with bad interfaces.
Thanks