RDP and Vista

  • Thread starter Thread starter Cezar
  • Start date Start date
C

Cezar

Is there a Newsgroup just like this one but for Vista? I keep getting
directed to microsoft answers beta and i really don't like it at all.

So I'll ask my question in here in hopes that the procedure is similar. I've
properly setup my router so that I can connect into it remotely. Port 3389 (I
think that's the one) has been forwarded. Now prior to my Vista install, I
was able to access my XP Pro pc at home w/o issues. Now I'm unable to after a
clean install of Vista Ultimate. I can still access my router by typing in
the numbers in the IE address bar but I'm unable to use RDP to connect to the
computer.

Is there a good how-to anywhere for this? I'm kinda lost.
 
Cezar said:
Is there a Newsgroup just like this one but for Vista? I keep
getting directed to microsoft answers beta and i really don't like
it at all.

So I'll ask my question in here in hopes that the procedure is
similar. I've properly setup my router so that I can connect into
it remotely. Port 3389 (I think that's the one) has been forwarded.
Now prior to my Vista install, I was able to access my XP Pro pc at
home w/o issues. Now I'm unable to after a clean install of Vista
Ultimate. I can still access my router by typing in the numbers in
the IE address bar but I'm unable to use RDP to connect to the
computer.

Is there a good how-to anywhere for this? I'm kinda lost.
Click to expand...

Please detail your setup more clearly.

What machine got the Vista Ultimate clean installation?

Are you trying to remote into your Windows XP Professional machine (at your
home) from a Windows Vista Ultimate machine (located remotely) - is that it?

What error/messages do you get when you attempt to make the connection?
Can you remote to the home PC from any other PCs (even ones behiond the same
NAT device/router?)
Is the port-forward still valid or was your router giving out only DHCP
addresses and your home machine has obtained a new IP?
 
Thanks for the quick responses. I'm at work currently so I'm unable to do any
testing with the RDC since I disabled the feature in my router.

But here's the basic setup..

Home machine is a brand new p4 e8400 with a Gigabyte board in it. It's a
screamer. It's the computer with the Vista on it and I use Comcast both at
home and at work (home and business accounts, respectively). I have the
Netgear WG824 Rangemax Mimo v1 with the latest firmware. RDC worked with this
update when the home computer had XP Pro on it.

The machine at work is not part of the corporate domain and uses Comcast
business (so nothing special like VPN or SSL is needed). Other employess are
on the same connection and RDC appears to work for them.

The computer is an HP dx2300 so it's pretty new. I've got XP Pro SP3 on it
witll ALL of the available MS updates. The home PC with Vista has all of the
updates, too as well as the latest hardware updates for video, audio, bios,
lan and I think that's it.

I've always been able to connect to my router at home from work using the IP
address and 8080 at the end (I think it was 8080).

I'll add more to this once my wife is awake and enables the remote
connection in the router....
 
Remember if your trying to use the web based method you need to have both TCP
Port 3389 [RDC] and TCP Port 8080 [IIS, you apparently changed the default
port from TCP Port 80] open on the home router. Is that the case?

If you don't use the web based method all you need its TCP Port 3389 open.
You can test this by going to the http://www.canyouseeme.org site while on
the home PC.

--

Al Jarvi (MS-MVP Windows – Desktop User Experience)

This posting is provided "AS IS" with no warranties, and confers no
rights...
The MS-MVP Program - http://mvp.support.microsoft.com
 
Cezar said:
I've always been able to connect to my router at home from work
using the IP address and 8080 at the end (I think it was 8080).
Click to expand...
<snip>
Remember if your trying to use the web based method you need to
have both TCP Port 3389 [RDC] and TCP Port 8080 [IIS, you
apparently changed the default port from TCP Port 80] open on the
home router. Is that the case?
Click to expand...
<snip>

8080 is for the router remote managment... ;-)
(I know that is default for Netgear and a few other brands.)
 
Cezar said:
I've always been able to connect to my router at home from work
using the IP address and 8080 at the end (I think it was 8080).
Click to expand...
<snip>
Remember if your trying to use the web based method you need to
have both TCP Port 3389 [RDC] and TCP Port 8080 [IIS, you
apparently changed the default port from TCP Port 80] open on the
home router. Is that the case?
Click to expand...
<snip>

Shenan said:
8080 is for the router remote managment... ;-)
(I know that is default for Netgear and a few other brands.)
Click to expand...

Bill said:
It *can* be for router configs but nothing standardizes it that
way. D-link doesn't, nor does Linksys.

Most routers will let you change this. Or, and this is a better
solution, disable remote admin connections entirely. There aren't
many situations that justify leaving the router admin port open to
the internet. The hack risks are just too great to make it
worthwhile. If you disable the connection you can then configure
the router to pass that port to an internal host. Some of the low
end routers will let you setup such a rule but won't give an error
about the remote admin being on the same port.
Click to expand...

I left the context from the original posting in on-purpose. The OP *said*
it was the router. ;-)

Don't disagree with you at all.
 
Back
Top