Quantcast
Viewing all articles
Browse latest Browse all 18256

MKS error on port 902

Hello,

 

I am getting the MKS error connecting to port 902 error when trying to use the vCenter and vSphere client or web client, and accessing the console of any vm. I'm using the vCenter OVF appliance (latest version 5,1) since Im just evaluating and short on hardware.

 

The system I'm trying to connect from is on the same LAN as the ESXi and venter systems via a site-to-site VPN connect with no filtered ports. Indeed port 902 is listening, however it's only listening for UDP:

 

lsof -i -P | grep 902
vpxd      13237      root   46u  IPv4   35058      0t0  UDP *:902
vpxd      13237      root   47u  IPv6   35059      0t0  UDP *:902

 

Only when watching the network traffic I see connections being made and (rightfully) refused by the OS on 902/TCP:

 

  2.610354    10.0.0.54 -> 10.1.0.5     TCP 56533 > 902 [SYN] Seq=0 Win=8192 Len=0 MSS=1380 WS=2 SACK_PERM=1
  2.610363     10.1.0.5 -> 10.0.0.54    TCP 902 > 56533 [RST, ACK] Seq=1 Ack=1 Win=0 Len=0
  3.146729    10.0.0.54 -> 10.1.0.5     TCP [TCP Port numbers reused] 56533 > 902 [SYN] Seq=0 Win=8192 Len=0 MSS=1380 WS=2 SACK_PERM=1
  3.146742     10.1.0.5 -> 10.0.0.54    TCP 902 > 56533 [RST, ACK] Seq=1 Ack=1 Win=0 Len=0
  3.686552    10.0.0.54 -> 10.1.0.5     TCP [TCP Port numbers reused] 56533 > 902 [SYN] Seq=0 Win=8192 Len=0 MSS=1380 SACK_PERM=1
  3.686562     10.1.0.5 -> 10.0.0.54    TCP 902 > 56533 [RST, ACK] Seq=1 Ack=1 Win=0 Len=0

 

So I guess my question is why isn't vpxd listening on TCP too?

 

I have seen a diagram around here that shows more recent versions of vCenter may not need 902/TCP but can make use of 443/TCP. If this is the case then how do I get the vSphere client to use this port?

 

Thank you,

 

-Erric


Viewing all articles
Browse latest Browse all 18256

Trending Articles