Windows Remote Desktop Web Connections

[L0stAngel]

Hello, I just setup web connections on a Win2K3 server, and want to be able to connect to x number of clients in the network. I have a Watchguard Firebox 1000. Right now, I can navigate to

http://<external

ip>/tsweb/, and I can view the login page...however when I try to connect to a pc...im prompted that I cant connect. If I am however physically on the Win2k3 server, I can goto

http://192.168.10.100/tsweb...and

connect to the peoples computers (10.100 is the 2k3's ip).

 

[L0stAngel]

Anyone?

 

[wintek]

It seems that you r trying to access the webserver from the internal side using the External Ip address. It wont let you do that incase of watchguard.

Reason : When you will try to access it using the external ip address, request will go out upto the ISP and when it'll come back to the Firebox's Ip address, Request will be denied by the Firebox because Destination and source Ip address will be same.

Solution : Publish a internal DNS Server which can resolve name of your website to the internal Ip address of the webserver and point all the computers to that DNS.. (Use secondary DNS as 4.2.2.2)
OR

Change the "Lmhost" File on all the computer to map name of the website to Internal Ip address of the webserver.

 

[Haunter]

tsweb needs port 3389 exposed to work properly. Even though you log into a web page on prot 80 it then moves you to port 3389. Now if you are not running a web server you can edit the tsweb page and window registry to work on port 80.

This applies to windows XP but can easily work for 2k3.

http://www.microsoft.com/windowsxp/using/networking/expert/northrup_03may16.mspx

Cheers


haunter@battlestrata.com