I have a Windows 2003 R2 Server with Terminal Services enabled. Everything is currently working, but have a few questions. 2x Client Gateway port = locahost:8088 HTTP = localhost:82 2x Publishing Agent = 20002 2x Site on IIS = port 82 Sharepoint on IIS = port 80 Default Site on IIS = port 81 Also have IIS setup using the exported webpage from the 2x Web Publisher. Ports 8088 and 82 are forward to the server. Technically everything is working both internally and externally, but I am not sure if it is setup correctly. As I understand, everything should tunnel over port 82, but nothing works unless I specify 8088 as the port to use in the clients. I also have to specify port 8088 when publishing the web applications when exporting the html code. This really wouldn't bother me, but I can use Remote Desktop and connect to terminal.domain.local:8088 both from internally and externally. I could use group policies to lock down the desktop, etc, but I think if it were setup correctly then nobody would be able to retrieve a full desktop. So I can go to http://external.domain.com:82 and pull up the web page. When the users click on the icon for the published app, it goes over port 8088. How can I get all the traffic to go over port 82 only as a proxy to port 8088, preventing Remote Desktop Connections from being ran. Thanks, Tyler
Hello, Your gateway port is 8088, so it is the port your clients will have to connect to to reach 2X ApplicationServer.
