breynolds01
asked on
Unable to connect to ftp - rdc - thightvnc through vpn checkpoint firewall
I have a server at a COLO. I have a checkpoint firewall in place with VPN access. I'm able to establish a VPN tunnel to the firewall and ping the server behind the firewall. However, I'm unable to access or FTP to the server, connect to the server using RDC (the server is configured to allow remote connections), and I'm unable to connect to the server in order to administer the server using TightVNC (server services are running, and configured correctly).
This is a new Dell server, fresh install Server 2003 R2 no internal firewall running (ICS services not running and disabled), and no third party firewall configured on the machine.
I can receive ping replies back from the server... just unable to access the server for remote administration.
Ideas? This is an emergency project, I've assigned 500 points to this questions.
Best,
Bryan
This is a new Dell server, fresh install Server 2003 R2 no internal firewall running (ICS services not running and disabled), and no third party firewall configured on the machine.
I can receive ping replies back from the server... just unable to access the server for remote administration.
Ideas? This is an emergency project, I've assigned 500 points to this questions.
Best,
Bryan
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
It could be, yes. If they terminated the tunnel inside the firewall, then yes, all ports should be open.
You can download PortQry and check it after you connect with the VPN client.
http://www.microsoft.com/downloads/details.aspx?FamilyID=89811747-c74b-4638-a2d5-ac828bdc6983&DisplayLang=en
http://www.microsoft.com/downloads/details.aspx?FamilyID=8355e537-1ea6-4569-aabb-f248f4bd91d0&DisplayLang=en
You can download PortQry and check it after you connect with the VPN client.
http://www.microsoft.com/downloads/details.aspx?FamilyID=89811747-c74b-4638-a2d5-ac828bdc6983&DisplayLang=en
http://www.microsoft.com/downloads/details.aspx?FamilyID=8355e537-1ea6-4569-aabb-f248f4bd91d0&DisplayLang=en
ASKER
I've tried scanning the server behind the firewall and almost all of the returns say "FILTERED" with almost all of the procedures failing with this message: "exits with return code 0x00000002".
Here is a query for port 21:
Starting portqry.exe -n x . x . x . x -e 21 -p TCP ...
Querying target system called:
x . x . x . x
Attempting to resolve IP address to a name...
IP address resolved to xxxxxx.com
querying...
TCP port 21 (ftp service): FILTERED
portqry.exe -n x . x . x . x -e 21 -p TCP exits with return code 0x00000002.
Here is a query for port 21:
Starting portqry.exe -n x . x . x . x -e 21 -p TCP ...
Querying target system called:
x . x . x . x
Attempting to resolve IP address to a name...
IP address resolved to xxxxxx.com
querying...
TCP port 21 (ftp service): FILTERED
portqry.exe -n x . x . x . x -e 21 -p TCP exits with return code 0x00000002.
Then they don't have many ports open.
Do you have FTP running inside your LAN? You may want to test domain ports using the GUI.
Do you have FTP running inside your LAN? You may want to test domain ports using the GUI.
ASKER
Yes, I have FTP open on the LAN. We have a public ip of 69.x.x.x which points to the firewall. Behind the firewall they have given us another public IP of 69.x.x.x, could this be part of the issue?
I would think so, yes. You can't have the same subnet on both sides of the firewall. Packets will be dropped.
ASKER
Looks like they had the firewall misconfigured. Now can load the underconstruction page, but I'm still unable to pass RDC traffice, and FTP traffic.
RDP uses TCP port 3389.
FTP uses TCP ports 20 and 21.
These ports must be allowed through the firewall. You would want to allow them using a rule so that the whole world doesn't have access.
FTP uses TCP ports 20 and 21.
These ports must be allowed through the firewall. You would want to allow them using a rule so that the whole world doesn't have access.
ASKER
I've been told that the rules are in place and that the only thing allowed through our VPN is port 3389 for RDC. After establishing the VPN tunnel and initiating a RDC connection to our ip address, I receive the error "the connection to the server cannot be established". We do not have a internal firewall on the server at this point.
In the past all I've had to do is open port 3389 and point it to the internal server which I would like to connect to remotely from the outside world.
This is enabled under > system properties > remote > Enable Remote Desktop on this computer.
Is this correct, or do I have to configure Terminal Services on Server 2003 in order to use RDC through the VPN?
In the past all I've had to do is open port 3389 and point it to the internal server which I would like to connect to remotely from the outside world.
This is enabled under > system properties > remote > Enable Remote Desktop on this computer.
Is this correct, or do I have to configure Terminal Services on Server 2003 in order to use RDC through the VPN?
ASKER
Update, it seems that the server isn't listening for port 3389, after doing a netstat -n
No, you don't need to configure Terminal Services. Simply right-click on My Computer, select Properties, select the Remote tab and check the box at the bottom for "Enable Remote desktop on this computer".
ASKER
Which is what I have done. What would cause the server not to respond to RDC request?
How many NICs are in this server?
If you try to RDP into the server from the inside of the firewall, can you?
If you try to RDP into the server from the inside of the firewall, can you?
ASKER
No, I can't and there are two nics, one is disabled. I have since removed the IP address of the NIC I was using and have enabled the other NIC and entered the IP address I was previously using. Still nothing.
When I do a netstat -a I can see the port 3389 but it's not boud to a IP address:
Proto Local Address Foreign Address State
TCP 0.0.0.0:3389 0.0.0.0:0 Listening
Here's what's listed on the IP address I'm using.
TCP 69.30.x.x:135 69.30.x.x:3444 Established
TCP 69.30.x.x:139 0.0.0.0:0 Listening
TCP 69.30.x.x:389 69.30.x.x:3442 Established
TCP 69.30.x.x:3442 69.30.x.x:389 Established
TCP 69.30.x.x:3444 69.30.x.x:135 Established
TCP 69.30.x.x:3457 66.30.x.x:80 Established
TCP 69.30.x.x:3458 69.30.x.x:139 Time_Wait
TCP 69.30.x.x:3459 69.30.x.x:139 Time_Wait
When I do a netstat -a I can see the port 3389 but it's not boud to a IP address:
Proto Local Address Foreign Address State
TCP 0.0.0.0:3389 0.0.0.0:0 Listening
Here's what's listed on the IP address I'm using.
TCP 69.30.x.x:135 69.30.x.x:3444 Established
TCP 69.30.x.x:139 0.0.0.0:0 Listening
TCP 69.30.x.x:389 69.30.x.x:3442 Established
TCP 69.30.x.x:3442 69.30.x.x:389 Established
TCP 69.30.x.x:3444 69.30.x.x:135 Established
TCP 69.30.x.x:3457 66.30.x.x:80 Established
TCP 69.30.x.x:3458 69.30.x.x:139 Time_Wait
TCP 69.30.x.x:3459 69.30.x.x:139 Time_Wait
Do you have RRAS installed? If so, you may need to rerun the setup and remove the filters.
ASKER
No RRAS installed. The only thing installed is IIS, .net framework 1.1 / 2.0, dhcp, dns are the only things installed on the server.
Have you rebooted this server lately? There is an issue with Remote Desktop after any patches are installed. Most of the time it takes 2 reboots after patching to get RDP back online.
I have this issue with my server and you'll find a number of people on here do also.
I have this issue with my server and you'll find a number of people on here do also.
ASKER
I've reboot the server about four times, I'll head back into the colo and boot the server a couple of times to see if that fixes the issue. I'll post after doing so. Thanks for the heads up.
ASKER
The problem seems to be the firewall and passing the 3389 traffic to the IP/Machine behind the firewall. I've created a segmented LAN and I'm able to RDP with no issues. I've also been able to use the LAN side of the firewall and RDP behind the firewall. Seems the issue is still with the VPN connection and the traffic passing through thte VPN / Firewall.
At this point I've pushed the issue back to the COLO who's managing our firewall. Thank you for your help, and as we both stated at the begining of this thread... RDP isn't that complicated.
At this point I've pushed the issue back to the COLO who's managing our firewall. Thank you for your help, and as we both stated at the begining of this thread... RDP isn't that complicated.
ASKER