Re: Port forwarding & failure to get out to port 3389 w/ remote de
From: jason (jason_at_discussions.microsoft.com)
Date: 01/26/05
- Next message: rob p: "Re: Whats preventing connect?"
- Previous message: jason: "RE: Port forwarding & failure to get out to port 3389 w/ remote de"
- In reply to: Sooner Al: "Re: Port forwarding & failure to get out to port 3389 w/ remote de"
- Next in thread: Jim, MCSE: "Re: Port forwarding & failure to get out to port 3389 w/ remote de"
- Reply: Jim, MCSE: "Re: Port forwarding & failure to get out to port 3389 w/ remote de"
- Reply: Sooner Al: "Re: Port forwarding & failure to get out to port 3389 w/ remote de"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 26 Jan 2005 12:15:03 -0800
I'm using the Linksys BEFW11S4 with the latest firmware (i upgraded it
yesterday). I know what no-ip.com can do for me but I am reluctant to do
that because my IP has remained static thoughout this entire experiment to
get RDC to work. When I go to whatismyip.com or run ipconfig, the public IP
shown is 24.44.xxx.xx. I assume this is for the router.
I agree that it's unlikely that 3389 is being blocked outbound from verizon
dsl and our cable modem though maybe on the T3. If that is the case, could
it be anything else besides my router settings? Is there anything else I
could be missing there?
Thanks,
Jason
"Sooner Al" wrote:
> You might consider using a dynamic naming service like No-IP.com... A small program runs on one of
> your home PCs and contacts the No-IP.com servers on a scheduled basis. The servers then know what
> your current IP is and map that to a fully qualified domain name that you can use to call from a
> remote site. I use this for access to my home LAN via VPN or Remote Desktop... It works very well
> for me...and its FREE...
>
> http://www.no-ip.com
>
> Personally, I think it doubtful that TCP Port 3389 is blocked by Verizon outgoing from a residential
> account, although anything is possible. I do know that some network administrators at work sites may
> block pretty much everything outbound as a security measure...
>
> I think its an issue with your router or addressing scheme when calling from a remote site.
>
> What Linksys router are you using? Have you installed the latest firmware?
>
> Also, note that when testing this from one PC to another PC on your local LAN that in most cases
> using the public IP of your router will not work. You must use the local LAN IP or be at a remote
> site and use the true public IP of the router.
- Next message: rob p: "Re: Whats preventing connect?"
- Previous message: jason: "RE: Port forwarding & failure to get out to port 3389 w/ remote de"
- In reply to: Sooner Al: "Re: Port forwarding & failure to get out to port 3389 w/ remote de"
- Next in thread: Jim, MCSE: "Re: Port forwarding & failure to get out to port 3389 w/ remote de"
- Reply: Jim, MCSE: "Re: Port forwarding & failure to get out to port 3389 w/ remote de"
- Reply: Sooner Al: "Re: Port forwarding & failure to get out to port 3389 w/ remote de"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|