Publishing 2X Externally

Hi,

I have successfully setup 2X Application Server internally within my network and now I would like to see it working externally. However when I connect via the client I get the following message.

Code:

[I 13/00000005] Thu Aug 30 11:00:43 2012 - Connection to xx.xx.xx.xx:80 was succesful
[I 13/00000005] Thu Aug 30 11:00:44 2012 - Connection to xx.xx.xx.xx:80 was succesful
[I 13/00000005] Thu Aug 30 11:00:44 2012 - Connection to xx.xx.xx.xx:80 was succesful
[I 13/00000005] Thu Aug 30 11:00:44 2012 - Connection to xx.xx.xx.xx:80 was succesful
[I 13/0000000A] Thu Aug 30 11:00:44 2012 - Connecting to Server: [0] xx.xx.xx.xx:80 Mode: 0
[I 13/00000005] Thu Aug 30 11:00:44 2012 - Connection to xx.xx.xx.xx:80 was succesful
[E 13/0000000B] Thu Aug 30 11:00:46 2012 - The specified remote 2X Connection could not be found.Verify that you have typed the correct computer name or IP address, and then try to connect again.

Port 80 and 443 are allowed to this server but I am wondering if I need to change anything on the Gateway settings to get this working.

Any advice welcome on getting this working.

Regards
David

 

does it work if you connect with mstsc?

 

We don't have 3389 open for those server externally but the issue has moved on a little.

The server we have is an Amazon EC2 instance with a Security Policy which allows port 80 and 443 through, this is outside of our network. The scenario now is

If I connect from my office then I get the above issues

If I connect from home on a standard non firewalled connection then everything connects fine..

We do not block port 80 outbound as we have internet access and a telnet test works ok to port 80 so what could be getting in our way?

 

Trying it with the MS RP client 1st is a good hint as long as the gateway mode is used and not the direct mode. Further on I would assume that the gateway mode would be the right configuration here because there's only port 80 and 443 allowed by the firewall.

I guess the current issue can be found somewhere in the connection configuration within the 2X management console. Maybe not all needed ports get tunneled through the configured gateway port or the gateway port is disabled?

Kind Regards,

 

Hmm... it may be that the firewall at your office do only allow outbound traffic to port 80, but e.g. for using the publishing feature of 2X the firewall also need to allow inbound traffic here.
I think it's time to check the logs from the firewall or to use a network sniffer to know if there is any other outbound port requested by your client that tries the connection. One thing that is important if only port 80 is allowed is that you use the gateway mode in conjunction with the 2X RDP client instead of the direct mode for the connection. Maybe you should check this option 1st.

Kind Regards,

 

We found the problem and it was a firewall and web filter issue.

Basically because it was port 80 we were routing the traffic through the web filter and this was stopping the traffic. We now have a rule in place to remove this issue.

Thanks for your help

 

awesome thank you for sharing!

 

It has slightly confused me why port 80 was the port of choice for this product tbh.

I would of rather had a high port number that didn't conflict with anything and just open up the firewall..

On the other hand port 80 is easy I guess as long as a web filter isn't in the way.

 

I would assume its because it is the most commonly open port. There are other apps I have used that rely on port 80 as well. Most firewalls seem to have predefined rules for them.

I found out you can change the port from the gateway options, so if you ever need to make changes or dont like port 80, you can change from there too.

 

Hey,
I have the same problem you had.
basically if I understand right, if I have web filtering from my ISP and they have changed something a few days ago in my plan they might have blocked my connection to the server over WAN?

Thanks!

 

could be, best to check directly with your ISP