RDP issue with pix

Answered Question
Dec 1st, 2007


I have a pix 506 installed replacing linksys. After this is installed, when I try to RDP to a computer internally (within LAN) I see the remote PC is getting rebooted. I have no issues to RDP into the server from outside. once on the server, when I try to make a virtual connection to any of the computer, I see the computer is getting restarted itself.

I just tried doing telnet internally to the remote ip on port 3389 and see it is getting restarted.

As this is within LAN, I dont think PIX has anything to do with this, however it seems that it happened after the pix installation.

Any input on this is greatly appreciated.


Correct Answer by husycisco about 9 years 2 months ago

Are there any dmp files in %SystemRoot%\Minidump with up to date creation date? Any 3rd party firewalls or antiviruses running?

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 3.5 (2 ratings)
husycisco Sun, 12/02/2007 - 06:55

Pretty interesting. I would first suggest you to shutdown the inside interface of PIX, you wont need the gateway since you RDP to a PC which is in same subnet. This will eliminate the possibilty of PIX. If computer restarts itself again although the PIX interface is disabled, that means PIX is not involved in this. Then I would suggest you Right-click My computer>Properties>Advanced>Startup and recovery and uncheck "Auto reboot" . This time you will see the Blue screen error when you try to RDP. Please tell us what Blue scree error you see.

techtips03 Sun, 12/02/2007 - 08:00


Thanks very much for the response. I am actually remote to the location. I should be able to do this remotely right by RDPing to the server and then shut down the inside interface of the pix? Just want to make sure that I dont lose connectivity to the location as the site is unmanaged. Or do I have to be on site to do this? Here is what I have on pix.

Inside interface -

server -

access-list outside_in permit tcp any host eq 3389

static (inside,outside) tcp 3389 3389 netmask

access-group outside_in in interface outside

ip address inside

nat (inside) 0 access-list 102

nat (inside) 1 0 0

global (outside) 1 interface

access-list 102 permit ip --> this is for my remote vpn clients

Please advise

Thank you for your time

husycisco Sun, 12/02/2007 - 08:08

You shouldnt take the steps if you are remote to the location.

Your config looks OK. Please follow the steps I posted when you are on site, and post the results. Lets see if server reboots itself when a server in local network try remote desktop to it. It is really a weak possibilty that the issue is PIX related. Might be an mtu issue.

techtips03 Fri, 12/07/2007 - 21:56

I have eliminated the PIX unit by shutting it down and did an RDP between the PCs and the remote pc started rebooting. I unchecked the auto restart option, however it started rebooting when I try to RDP leaving no error message.

Any further advise?

Correct Answer
husycisco Mon, 12/10/2007 - 01:48

Are there any dmp files in %SystemRoot%\Minidump with up to date creation date? Any 3rd party firewalls or antiviruses running?

techtips03 Thu, 12/13/2007 - 14:11

I am still waiting to visit the client and get information on this.

Another question

I have a remote user logging into this PIX through Microsoft Windows PPTP client. And once on VPN, he is not able to access his Internet. I believe it is a characteristic of software VPN but is there anyway he can browse the Internet changing routing tables etc or should I have to go for L2TP?

Please advise


This Discussion