RDP, VPN not working with one ISP?

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

After days of frustration, I have come us with the following in trying to connect to my WinXP Pro laptop via the internet

1. I can connect successfully when my laptop is on my network at the office, behind a router. The appropriate ports are of course open; running ZoneAlarm. I can also connect to it from my home DSL network when my laptop is connected via dial-up. I therefore make the assumption that my laptop is configured properly
2. However, I cannot connect to the laptop when it is on my home network. This uses a Linksys BEFW11S4 v2 router, with the latest firmware installed. Ports 3389 and 1723 are forwarded to my static ip for the laptop. I still cannot connect if I bypass the router and directly connect my laptop

Is it possible that my home ISP somehow blocks RD and VPN connections? Or am I missing something really basic here

THANKS
 
After days of frustration, I have come us with the following in trying to connect to my WinXP Pro laptop via the internet:

1. I can connect successfully when my laptop is on my network at the office, behind a router. The appropriate ports are of course open; running ZoneAlarm. I can also connect to it from my home DSL network when my laptop is connected via dial-up. I therefore make the assumption that my laptop is configured properly.
2. However, I cannot connect to the laptop when it is on my home network. This uses a Linksys BEFW11S4 v2 router, with the latest firmware installed. Ports 3389 and 1723 are forwarded to my static ip for the laptop. I still cannot connect if I bypass the router and directly connect my laptop.

Is it possible that my home ISP somehow blocks RD and VPN connections? Or am I missing something really basic here?

THANKS!
Click to expand...

Since you have a Linksys BEF series router, you can use WallWatcher to
capture an activity log.

http://www.wallwatcher.com/

Be sure to get the graphics library too.

Then get PortDetective from TZO:

http://www.portdetective.com/

Put the ports you suspect may be blocked in PD and watch the log. If
you see a hit in the log, then obviously that port is not blocked.

HTH

--

Map Of The Vast Right Wing Conspiracy:
http://www.freewebs.com/vrwc/

You know you are in Hell when you have to make a
distinction between what is moral and what is legal.
 
Bob,

Thanks for the suggestions. I have installed both utilities. Port Detective tells me that 3389 is In Use; Wall Watcher doesn't show any activity re: 3389
From another thread, I tried the suggestion of running netstat -ano. I get the following

Active Connection

Proto Local Address Foreign Address State PI
TCP 0.0.0.0:135 0.0.0.0:0 LISTENING 100
TCP 0.0.0.0:445 0.0.0.0:0 LISTENING
TCP 0.0.0.0:1025 0.0.0.0:0 LISTENING 105
TCP 0.0.0.0:1026 0.0.0.0:0 LISTENING
TCP 0.0.0.0:1027 0.0.0.0:0 LISTENING 185
TCP 0.0.0.0:1112 0.0.0.0:0 LISTENING 361
TCP 0.0.0.0:1115 0.0.0.0:0 LISTENING 361
TCP 0.0.0.0:1122 0.0.0.0:0 LISTENING 361
TCP 0.0.0.0:1723 0.0.0.0:0 LISTENING
TCP 0.0.0.0:3389 0.0.0.0:0 LISTENING 105
TCP 0.0.0.0:5000 0.0.0.0:0 LISTENING 126
TCP 0.0.0.0:34249 0.0.0.0:0 LISTENING 64
TCP 0.0.0.0:39681 0.0.0.0:0 LISTENING 64
TCP 0.0.0.0:40019 0.0.0.0:0 LISTENING 155
TCP 127.0.0.1:1027 127.0.0.1:1123 TIME_WAIT
TCP 127.0.0.1:1091 0.0.0.0:0 LISTENING 134
TCP 192.168.254.102:139 0.0.0.0:0 LISTENING
TCP 192.168.254.102:1112 207.46.249.252:80 ESTABLISHED 361
TCP 192.168.254.102:1115 207.46.249.252:80 ESTABLISHED 361
TCP 192.168.254.102:1122 64.233.167.99:80 ESTABLISHED 361
TCP 192.168.254.102:1124 192.168.254.106:139 TIME_WAIT
TCP 192.168.254.102:1125 192.168.254.106:139 TIME_WAIT
TCP 192.168.254.102:1127 0.0.0.0:0 LISTENING
TCP 192.168.254.102:1127 192.168.254.106:139 ESTABLISHED
TCP 192.168.254.102:1129 192.168.254.105:139 TIME_WAIT
UDP 0.0.0.0:162 *:* 46
UDP 0.0.0.0:445 *:*
UDP 0.0.0.0:500 *:* 84
UDP 0.0.0.0:1030 *:* 123
UDP 0.0.0.0:1645 *:* 105
UDP 0.0.0.0:1646 *:* 105
UDP 0.0.0.0:1701 *:*
UDP 0.0.0.0:1812 *:* 105
UDP 0.0.0.0:1813 *:* 105
UDP 127.0.0.1:123 *:* 105
UDP 127.0.0.1:1028 *:* 105
UDP 127.0.0.1:1029 *:* 105
UDP 127.0.0.1:1111 *:* 361
UDP 127.0.0.1:1900 *:* 126
UDP 192.168.254.102:123 *:* 105
UDP 192.168.254.102:137 *:*
UDP 192.168.254.102:138 *:*
UDP 192.168.254.102:491 *:* 185
UDP 192.168.254.102:1900 *:* 126

Do I understand from the line "TCP 0.0.0.0:3389 0.0.0.0:0 LISTENING 1052" that this is the expected result for a successful RD connection

Telnet is unsuccessful when my laptop is at this location

Thanks again


----- Bob wrote: ----

On Sat, 3 Apr 2004 05:21:05 -0800, =?Utf-8?B?Um9k?
After days of frustration, I have come us with the following in trying to connect to my WinXP Pro laptop via the internet
2. However, I cannot connect to the laptop when it is on my home network. This uses a Linksys BEFW11S4 v2 router, with the latest firmware installed. Ports 3389 and 1723 are forwarded to my static ip for the laptop. I still cannot connect if I bypass the router and directly connect my laptop.
Click to expand...

Since you have a Linksys BEF series router, you can use WallWatcher to
capture an activity log.

http://www.wallwatcher.com/

Be sure to get the graphics library too.

Then get PortDetective from TZO:

http://www.portdetective.com/

Put the ports you suspect may be blocked in PD and watch the log. If
you see a hit in the log, then obviously that port is not blocked.

HTH

--

Map Of The Vast Right Wing Conspiracy:
http://www.freewebs.com/vrwc/

You know you are in Hell when you have to make a
distinction between what is moral and what is legal.
 
Port Detective tells me that 3389 is In Use;
Click to expand...

I would not pay a great deal of attention to that. You only want PD to
send a packet to a specified port.
Wall Watcher doesn't show any activity re: 3389.
Click to expand...

The fact that WallWatcher does not show any activity for port 3389
seems to indicate that the packet you sent with PD is not making it to
your computer.

Check with a port you know should work to convince yourself that this
test is set up correctly. See what happens when you send a packet to
port 21 (FTP). Or look at some of the ports in the log to see what is
getting to your router and test them to see if everything is working
properly.


--

Map Of The Vast Right Wing Conspiracy:
http://www.freewebs.com/vrwc/

You know you are in Hell when you have to make a
distinction between what is moral and what is legal.
 
----- Bob wrote: ----

On Fri, 9 Apr 2004 06:01:04 -0700, =?Utf-8?B?Um9k?
Check with a port you know should work to convince yourself that thi
Click to expand...
test is set up correctly. See what happens when you send a packet t
port 21 (FTP).

Thanks again. I can successfully telnet port 21 from this location, both with the router connected and bypassing it. No-go with 3389 and 1723, though

Ro

Map Of The Vast Right Wing Conspiracy
http://www.freewebs.com/vrwc

You know you are in Hell when you have to make
distinction between what is moral and what is legal
 
test is set up correctly. See what happens when you send a packet to
port 21 (FTP).
Click to expand...
Thanks again. I can successfully telnet port 21 from this location, both with the router connected and bypassing it. No-go with 3389 and 1723, though.
Click to expand...

It's time to make call your ISP and tell them not to block ports you
need.

Be prepared, however, to be hustled for a "business" connection.

That's why they blocked VPN ports in the first place.


--

Map Of The Vast Right Wing Conspiracy:
http://www.freewebs.com/vrwc/

You know you are in Hell when you have to make a
distinction between what is moral and what is legal.
 
Thanks, I'll be going back to my ISP with this info and press the case again. I can't think of any other possibility other than those ports being blocked at their end, even though they say that is not the case

Rod
 
Back
Top