11 listopada 2010 18:28
I have a cluster that works fine with topology 1, but NAT is turned off. If I configure network to provide the compute nodes with access to the internet using NAT I experience intermittent problems in the connection. I lose the remote desktop session every few minutes.
I need to access the world from the nodes because I need to use a license server that is outside.
What can I check to find a solution to this?
13 listopada 2010 00:09
Is your cluster on a network where there might be some network restrictions that are blocking or preventing your head node from being a "Boundary Server" ?
Are you seeing anything in the Event Logs on your Head Node that may be able to shed more light on this problem? If your head node is dropping connections with NAT turned on then perhaps something is there.
Just some ideas.
22 grudnia 2010 23:39
I have a similar problem. Two network connections with topology 1, NAT on and if the private NIC is enabled I can't connect to my head node. The first NIC is connectect to our enterprise network with static IP. When I disable the 2nd NIC for private I can establish a RDP session. When I then enable the private NIC all is OK, but after a reboot I haven't RDP.
What can I check?
2 stycznia 2011 09:15
Troubleshooting NAT problems can be difficult in certain environments (including those at Microsoft where IPSec and multitudes of network security policies are in full force).
Do any of the HPC pack network diagnostic tests fail (DNS, AD connectivity, ping, etc.)?
One thing to try is changing your private network definition to a more traditional definition of 192.168.0.1/255.255.255.0 (or perhaps a more encompassing subnet mask like 255.255.0.0). You would also need to manually adjust your DHCP scope settings appropriately in the network configuration wizard.
- Zaproponowany jako odpowiedź przez Don PatteeModerator 4 lutego 2011 21:24