Need Help with Linksys wrt54g router and RDP?

[Bob]

I have a Linksys WRT54G on a office network. I set up one PC to accept
remote connections using port 3390. I have tried this internal to the
router on the local network and can connect to the PC from any other PC on
the local network using 192.168.1.71:3390. Once I go outside the local
network I get the prompt, enter my credentials, and get bounced right away.
Externally I use the static IP for my router xxx.xxx.xxx.xxx:3390.

Any ideas greatly appreciated!

Bob

 

[Shenan Stanley]

I have a Linksys WRT54G on a office network. I set up one PC to
accept remote connections using port 3390. I have tried this
internal to the router on the local network and can connect to the
PC from any other PC on the local network using 192.168.1.71:3390. Once I
go outside the local network I get the prompt, enter my
credentials, and get bounced right away. Externally I use the
static IP for my router xxx.xxx.xxx.xxx:3390.
Any ideas greatly appreciated!

So you changed the listening port on the computer...
But did you forward the port on the router to machine in question?

 

[Bob]

Yes I changed the port from 3389 to 3390. When I do it locally it connects
just fine. I then went to the router and forwarded port 3390 to
192.168.1.71 which is the static Port I set for the PC and selected TCP and
enabled it. I've done this on a number of other PCs over the last week but
none with a Linksys router. They all work fine except this one so I thought
there might be something different with this router.

I also have the windows firewall disabled.

Thanks

 

[Everett H. Leaper]

I too am having problems with a WRT54G router. I just upgraded the firmware
to v4.71.1. I cannot connect from within my LAN. Did you find anything
specifically wrong with that router?

I have the Port Triggering set to allow 3389 but can't get it going. It was
workign fine before I upgraded the firmware.

Yes I changed the port from 3389 to 3390. When I do it locally it connects
just fine. I then went to the router and forwarded port 3390 to
192.168.1.71 which is the static Port I set for the PC and selected TCP and
enabled it. I've done this on a number of other PCs over the last week but
none with a Linksys router. They all work fine except this one so I thought
there might be something different with this router.

I also have the windows firewall disabled.

Thanks

 

[texas snowman]

I've found Linksys routers to sometimes be somewhat "stubborn". Just
a suggestion, but try this. On your Remote Desktop host, do NOT assign
a static IP. Allow it to obrain its IP from the router. Make note of
what IP the host is assigned and forward the correct port in your
router to that IP address. If that works, everything will be fine
unless the host reboots and obtains a different IP. However, that is
still ok if your Linksys router has a static public IP. Set your
router to allow remote access. (Usually on port 8080) Then you can
access your router from any remote location and navigate to the local
network settings to see what IP your RD host has been assigned. (DHCP
Client Table) Then forward the port to the new IP.

I too am having problems with a WRT54G router. I just upgraded the firmware
to v4.71.1. I cannot connect from within my LAN. Did you find anything
specifically wrong with that router?

I have the Port Triggering set to allow 3389 but can't get it going. It was
workign fine before I upgraded the firmware.

 

[Everett H. Leaper]

Interesting. Sounds valid. I ended up getting it to work prior to seeing
Texas Snowman's (is that a Young Jeezy type of reference?) post. I allowed
the client to assign the IP automatically. Then I allowed that IP address on
the host to be allowed in. I also reflashed the firmware on the router....
I'm not sure which one worked, but in the end one of them did.

 

[texas snowman]

<chuckle> We must definitely be from different generations. I had to
Google that "Young Jeezy" thing to figure out what the heck you were
talkin' about. No...I'm just a Fat, White guy who lives in Texas and
smokes a pipe...thus the nickname Glad you got your problem fixed.
Happy Holidays

Interesting. Sounds valid. I ended up getting it to work prior to seeing
Texas Snowman's (is that a Young Jeezy type of reference?) post. I allowed
the client to assign the IP automatically. Then I allowed that IP address on
the host to be allowed in. I also reflashed the firmware on the router....
I'm not sure which one worked, but in the end one of them did.