Xen Win2008 64 bit VM no rdp access

An IT company is virtualizing our servers on 3 Xenhosts using redundant SANS.  We're just getting started and there are also various new switches etc involved.  At this point we can RDP on the local network to a Win2003 VM, however we cannot RDP consistently to a 2008 64 bit VM.  I think it has something to do with the network interface on the 2008's.  In the 1st initial testing we WERE able to RDP to one 2008 vm, and I'm pretty sure at that point the Xen NICs were not in a bonded redundant config, but I'm not 100% sure.  Hoping someone can point us in the right troubleshooting direction.  Like I said the 2003 32 bit vm has no trouble.  The 2008 64 bit VMs can't connect or once in a great while, after a couple of minutes they will connect, but most of the time they will not.  I first thought it was a misconfig or routing issue on the new switches that are connected to our old, but if so the 2003 should have trouble too.  Which leaves me thinking the 2008's are having some routing or RDP issue with their bonded nic interface on the Xenhost.  However, ping to the 2008's works fine.  Any ideas would be appreciated as I'm paying them mega $$ on a Sunday to troubleshoot this.  We have a deadline we have to make this week.
LVL 1
Brian_MBAsked:
Who is Participating?
 
Jason WatkinsIT Project LeaderCommented:
Is there a gateway address assigned to each NIC?
0
 
Jason WatkinsIT Project LeaderCommented:
Hello,

You can, at some time, RDP into your WS08 box? Could there be any firewall setting which may be preventing your connection on the; WS08 VNIC, Xen NIC, switch port or router? I am assuming you can get online from WS08 and work normally that way.
0
 
Brian_MBAuthor Commented:
Yes some times it will connect after a minute or two which tells me nothing is totally blocking RDP.  I think we are goint to try breaking the bonded nic and go back to a single interface to see if it works like it did initially.  If that works then we just have to figure out why the bonded nics are causing RDP to not work all of the time.
0
Network Scalability - Handle Complex Environments

Monitor your entire network from a single platform. Free 30 Day Trial Now!

 
Brian_MBAuthor Commented:
Not sure.  What they know at this point is taking the bonded nic away fixes the problem.
0
 
Jason WatkinsIT Project LeaderCommented:
Similar fix for a similar problem in Microsoft's Hyper-V. Removing the second default gateway address from the additional NIC fixed any connectivity issues. Glad to hear it is working now.
0
 
Brian_MBAuthor Commented:
The problem "fixed itself" according to the techs working on it.  However, I was in another VM troubleshooting no rdp from a vpn client and noticed that there was no default gateway assigned.  I have a suspicion that this was the same problem on the other server even though they said it wasn't, therefore I'll award points to Firebar for the gateway suggestion.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.