RDC into win2k from home

[GUJUm0deL]

I have a win2k machine which I'd like to RDC into from home. But every time I attempt to connect I get a message saying "client could not connect to the remote computer". What am I doing wrong?

The server is connected to a router at the office, if that helps in any way. I enabled "RDC sharing" from the control panel.

What are all the steps needed in being able to RDC into my win2k machine from home?

Thanks.

_____________________________
Just Imagine.

http://www.imajinarts.com

 

[ShackDaddy]

Where did you enable "RDC Sharing"? To my knowledge, W2K Workstation does not support remote desktop. I've always had to RDC to the server and then use VNC or something to control the client system.

Dave Shackelford
Shackelford Consulting

 

[GUJUm0deL]

Well, the win 2003 (sorry, I mistyped, it's actually a win 2003 not win2k) is the server. I have a PC from home which I'd like to RDC into. I enabled the Terminal Services like MS says and still get the error.

What exactly are the steps needed to enable this feature? When I RDC into a client's machine I get a UID and PSWD -- don't I need to create those in my case? Where do I create that?

_____________________________
Just Imagine.

http://www.imajinarts.com

 

[GUJUm0deL]

PS - I thought that maybe Windows firewall may be preventing the connection from happening, but when I try to disable it for a test I get an error saying that I can't disable because another app may be using the service and refers to ipnet.sys or ipnat.sys



_____________________________
Just Imagine.

http://www.imajinarts.com

 

[ShackDaddy]

Normally this is what you'd do:

Go to the system control panel and pull up the Remote tab. Enable remote desktop there.

Then (if your server doesn't have a public IP address bound to the NIC) configure your firewall/router to allow port 3389 in to your server's private IP.

If you can't pull up the Windows Firewall, try pulling up the Routing and Remote Access Server admin console. Does it show that RRAS is running? There's an area in there you can configure specific open ports on too, and you may need to configure TCP 3389 in there. But this step isn't always mandatory, depending on how your server's been set up. Do you have one or two NICs on your server?

Dave Shackelford
Shackelford Consulting

 

[GUJUm0deL]

I did the first part, where I enabled remote desktop.

The server is attached to a router (and we have a static IP address). I enabled port 3389 for Terminal Services. Like I mentioned above, I can't access the windows FW. Every time I try I get an error saying some service is using ipnat.sys (and I have no idea what that service is).

I believe I have one NIC on the server. Does it matter if the server is attached to a router?

_____________________________
Just Imagine.

http://www.imajinarts.com

 

[ShackDaddy]

Are you able to look at the Routing and Remote Access console? When that's open, does it say that RRAS is running?

Dave Shackelford
Shackelford Consulting

 

[GUJUm0deL]

I get the same ipnat.sys error when I attempt to get to that console. What is ipnat.sys?

_____________________________
Just Imagine.

http://www.imajinarts.com

 

[ShackDaddy]

Go into Computer Management and look at the Services and Applications area. Instead of going into the Services list, do you see RRAS in that list with a red X on it? Right click it and choose Disable if you can.

IPNat.sys error ususally comes up if RRAS is enabled but not running, and the answer is usually to disable it in your situation.

Dave Shackelford
Shackelford Consulting