Tilted Forum Project Discussion Community - View Single Post

j8ear · 12-18-2003, 07:40 PM

From XP to a windows 2000 server is simple...start and configure the terminal services server service on the target machine (w2kserver) and use the remote desktop application to connect to it from the XP workstation via IP address (or FQDN).

You must configure the user which will be TSing into to have permission to do so.

More then likely your work PC is firewalled and has a private NAT IP. If this is the case, you will first need to tunnel into your office network somehow....or have your company's firewall do some port address translation.

If your office PC has a public IP (i.e one that is not a 10.x.x.x or 192.168.x.x or 172.x.x.x) then it should be no problem. Although if this is the case your office has other problems to worry about.

Also more then likely your office PC is running w2k pro and not server. I'll have to research exactly what needs to be done. More then likely you will need to add the TS service to the w2k pro workstation before connectivity can be established. I have never actually done it though.

All of these (in fact any that I can think of) will use the TCP/IP protocol for the connection. Terminal Services runs on tcp/udp ports 3389.

Before you get to into figuring this out, make sure your work PC is publically addressable. If not clear the desired remote connectivity with your firewall guy.

I probably threw alot out there that might not make sense. Ask away and I or someone will be able to answer your questions.

We've definately got to know the specifics of the OS's in question.

-bear

12-18-2003, 07:40 PM	#6 (permalink)
j8ear Gentlemen Farmer Location: Middle of nowhere, Jersey	From XP to a windows 2000 server is simple...start and configure the terminal services server service on the target machine (w2kserver) and use the remote desktop application to connect to it from the XP workstation via IP address (or FQDN). You must configure the user which will be TSing into to have permission to do so. More then likely your work PC is firewalled and has a private NAT IP. If this is the case, you will first need to tunnel into your office network somehow....or have your company's firewall do some port address translation. If your office PC has a public IP (i.e one that is not a 10.x.x.x or 192.168.x.x or 172.x.x.x) then it should be no problem. Although if this is the case your office has other problems to worry about. Also more then likely your office PC is running w2k pro and not server. I'll have to research exactly what needs to be done. More then likely you will need to add the TS service to the w2k pro workstation before connectivity can be established. I have never actually done it though. All of these (in fact any that I can think of) will use the TCP/IP protocol for the connection. Terminal Services runs on tcp/udp ports 3389. Before you get to into figuring this out, make sure your work PC is publically addressable. If not clear the desired remote connectivity with your firewall guy. I probably threw alot out there that might not make sense. Ask away and I or someone will be able to answer your questions. We've definately got to know the specifics of the OS's in question. -bear __________________ It's alot easier to ask for forgiveness then it is to ask for permission.