Welcome to ISAserver.org

XP's Remote Desktop Connection

Users viewing this topic: none

Logged in as: Guest

Printable Version

All Forums >> [ISA Server 2000 Firewall] >> SecureNAT Client >> XP's Remote Desktop Connection

Page: [1]

Message

<< Older Topic Newer Topic >>

XP's Remote Desktop Connection - 14.Jun.2004 3:31:00 PM

biz4mo

Posts: 2
Joined: 14.Jun.2004
Status: offline

We are a Microsoft 2k3 Server/XP shop. We have also implemented ISA Sever 2K. We have a client that are attempting to connect to a client's location using XP's Remote Desktop Connection. The client has a pix system and has allowed port 3389 from our location, however, our connection fails "[Frown]"

. Any suggestions?

Post #: 1

Featured Links*

RE: XP's Remote Desktop Connection - 14.Jun.2004 9:24:00 PM

spouseele

Posts: 12782
Joined: 1.Jun.2001
From: Belgium
Status: offline

Hi biz4mo,

you need to allow the RDP protocol (TCP port 3389 outbound) in a protocol rule. Take note that the internal client should be configured as a Firewall and/or SecureNAT too.

What is the ISA Firewall log telling you? Make sure you enabled the logging of all fields in the ISA MMC, especially Rule#1 and Rule#2.

HTH,
Stefaan

(in reply to biz4mo)

Post #: 2

RE: XP's Remote Desktop Connection - 14.Jun.2004 9:54:00 PM

biz4mo

Posts: 2
Joined: 14.Jun.2004
Status: offline

Stefaan,
I really appreciate your response. I had found a MS kb article # 275210 How to Allow Access to Terminal Services on ISA which help me know how to set up the packet filter.

Now I am in the testing stage, and I find that I can establish a remote connection from my workstation, and the ISA server, however, I cannot complete this task from other workstations in the domain.

My question is how is that possible that one workstation and the server can perform the task only? How can add additioanl workstations? All workstations are Firewall enabled clients.

Would you please explain more about the Firewall log.

(in reply to biz4mo)

Post #: 3

RE: XP's Remote Desktop Connection - 14.Jun.2004 11:05:00 PM

spouseele

Posts: 12782
Joined: 1.Jun.2001
From: Belgium
Status: offline

Hi biz4mo,

if something isn't working as expected, you should consult the ISA logfiles. They are your primary resource for debugging. To get the most information out of the logfiles, I strongly recommend to enable the logging of *all* fields. In the MMC, go to the node Monitoring Configuration, then select Logs. In the details pane, right-click the applicable service and then click Properties. On the Fields tab, click Select All. Also, it is a good idea to selct the ISA format for the ISA log files.

To understand what is logged, check out the ISA helpfile. There is a section called "Firewall and Web Proxy log fields", a must read. Additional information can be found in the following articles:
- http://support.microsoft.com/default.aspx?scid=kb;en-us;284818
- http://support.microsoft.com/default.aspx?scid=kb;en-us;193625
- http://msdn.microsoft.com/library/default.asp?url=/library/en-us/winsock/winsock/windows_sockets_error_codes_2.asp

HTH,
Stefaan

(in reply to biz4mo)

Post #: 4