Big Issue- Not connecting from 10.10 networks

  • Thread starter Thread starter nerdpatrol
  • Start date Start date
N

nerdpatrol

We have tested this on 4 different 10.10.x.x networks and the 2x client will publish apps(80) and will not connect to app. You can connect via rdp full desktop with no issues. Trace Route shows no other 10.10.x.x. networks along the path.
 
If you are using the 2X ApplicationServer Client from a 10.10.x.x network, it will get the list of published apps, but it will not ever connect to the terminal server. The full RDP desktop works fine.

After having this issue appear at 3 client's sites, I set up a firewall in the office and assigned the internal network to 10.10.1.0/24, and I was unable to connect to the terminal server via 2X. I changed the network to 10.11.1.0/24 and it worked fine. I also tried 10.10.0.0/16 with the same results. After further testing, I determined that any netowrk starting with 10.10 produces the same results, regardless of the subnet or last two octets.
 
nerdpatrol said:
If you are using the 2X ApplicationServer Client from a 10.10.x.x network, it will get the list of published apps, but it will not ever connect to the terminal server. The full RDP desktop works fine.

After having this issue appear at 3 client's sites, I set up a firewall in the office and assigned the internal network to 10.10.1.0/24, and I was unable to connect to the terminal server via 2X. I changed the network to 10.11.1.0/24 and it worked fine. I also tried 10.10.0.0/16 with the same results. After further testing, I determined that any netowrk starting with 10.10 produces the same results, regardless of the subnet or last two octets.
Click to expand...

What does the 2X Managment Console, Status Page show, can you copy the information here
 
You must log in or register to reply here.
Back
Top