Zone Alarm Pro and Remote Desktop

Bill,

Turning off Zonealarm , can you get remote desktop working ?

Make sure the inbuilt firewall in windows xp is NOT turned ON aswell ..

Is your computer directly connected through cable modem or through a router ?

Also check if this would help
http://members.cox.net/ajarvi/RemoteDesktop/Multiple_PC_RD.html

Do this aswell

How to change the listening port for Remote Desktop
http://support.microsoft.com/default.aspx?scid=kb;EN-US;q306759

SR

Terminal Services ( Remote Desktop ) is a service.

I am assuming that Zone Alarm is on the machine that you are trying to connect to ( you mentioned it didn't see incoming calls )

Goto Control Panel Services
With Zone Alarm  running find the Terminal Services ( remote desktop service ) and restart.
Zone Alarm should detect it and prompt you.

I always restart all of may services at least once like this after I install or update Zone Alarm.

Cheers
Ian

I cannot restart terminal services. It is started, but it doesn't allow me to start, stop, or restart it.

And to answer above, Remote Desktop worked perfectly before, it works when I shutdown Zone Alarm, no the Windows firewall is not running, and yes I am behind a router that forwards port 3389 to my static IP.

Thanks,
Bill

Is opening port 3389 in Zonealarm , the only thing you have done in it for remote desktop to work ?

When you try to connect from a different machine , have you given like this

<ipaddress>:3389

SR

If you can not restart then chances are you are not a local administrator.
Log on as a local Administrator and so as above.

Cheers
Ian

I am not on the Administrator account, but the account I am using is part of the administrator accounts

No I haven't tried ipaddress:3389, but I am 100% sure the default port is 3389, my router is only forwarding that port and the MS support site says the default port is 3389.

Yes, the only thing I have tried is opening port 3389 is zonealarm.

Thanks,
Bill

Try that ipadress:3389 to connect to the machine and see if that would wokr.
You are right about port 3389.. I was just suggesting you to try that ipaddress:3389

SR

Bill,

Also in your zonelarm , see if you have done this
open Zonealarm
In the left, you would see "program control". Click on it
Now you would see list of programs displayed . In that check if you see Remote desktop connection. If you see then, on the right of it , if you see ?, just click on it and press the green tick mark. Do for all the ?s there. See if that would help

SR

Bill,

I have just tried the below to confirm it works. One or other should work.

Go start run C:\Windows\System32\svchost -k DComLaunch     ( Terminal Services executeable path as per services entry ) As terminal services already running may not work but Zone Alarm should still pop up ( my equivalent did )

or if this doesn't work then

Start services.msc
Go to terminal services service ( note if manual or automatic )
Disable it
Reboot
Change back to auto / manual
Press play to start

Cheers
Ian

The service is allowed access to the internet in zonealarm.

I checked the log, and here is the line that shows the blocking of the remote desktop

FWIN,2004/10/12,00:13:20 -4:00 GMT,67.20.246.57:1796,192.168.1.100:3389,TCP (flags:S)

Ian, I tried your steps, but it didn't work. The service, svchost.exe, is already in zonealarm, and nothing popped up.

Thanks,
Bill

Bill,
I am on my home machine now trying to replicate.
Firstly can you run remote desktop from the local machine ( ie the one with Zone Alarm on)

If you can then chances are Zone Alarm Network is blocking the application not Zone Alarm Programmes. The fact that C:\WINDOWS\System32\svchost.exe is already enabled also points to this.

Check the Zone Alarm network settings and see if you are trusting the local subnet.

Also what version of XP ( ie sp1 or SP2 ) if running SP2 then it could be ICF that is stopping the connection not Zone Alarm.

Check control panel networking to see if enabled / disabled.

Let us know how you go

Cheers
Ian

Amir,

Thank you very much for your help.

I did was change both settings (trusted and internet zone) to the med level. This has fixed the problem.

Thanks,
Bill

Hi Cornellian,
Glad to be or help, and, thanks for the grade.
:-)
Amir