IP addresses in event logs (Jump Desktop Connect for Windows)

Follow

Mike Radler

January 17, 2022 19:08

Hi,

When reviewing Windows event logs for Jump Desktop Connect, most incoming connection entries have public IP addresses as expected but some have private IP addresses that don't match the LAN they're on.

The ones I have seen are RDP connections using the private IP 172.31.x.x.

Example entry: Incomming Connection: Type:Cloud, ConnectionID:xxx, TunnelID:rdp, PeerID:xxxx, Email:xxxx, IP:172.31.32.230.

Thanks to someone who can explain what causes these private IP addresses to be logged rather that the users's public IP address.

0

• 

  WMC January 19, 2022 18:55 (Edited January 19, 2022 20:37)

  That's a good question. I just noticed today that 2 users were connected to Jump Connect on my PC while I was connected. This is my computer, and nobody else is supposed to have the password. I saw the screen flash, and they disconnected before I could get to the tray icon to see what their IP was. I'm checking the logs now to see if I can find out. I will update asap.

  0

  Comment actions Permalink
• 

  WMC January 20, 2022 18:46 (Edited January 20, 2022 18:47)

  Update: I figured out that it was me trying to connect simultaneously with my iPhone X while connected with my iPad. This has been a weird ongoing problem since December last year when my phone started to fail to connect. It can reflect the correct online status of each of my PCs, but it will not connect (most of the time).

  I hope you get a satisfactory answer to your question. Best regards!

  0

  Comment actions Permalink

Please sign in to leave a comment.