Establishing Remote Desktop Connection

[Guest mc]

I run a small business and I double up as the tech guy running the company's

small network. The server is still the old NT4.0, although all workstations

are XP Pro. Internet connection is via a TI, and all computers are on

private IP with the server static and all workstations dynamic. I have

enables the host desktop to accept remote connection. The computer that is

intended to be the remote is a laptop. With the laptop connected locally on

the LAN I can invoke remote desktop from the laptop and sign-on to the host

desktop by specifying the host machine name. The problem I ran into is when

I am truely remote with the laptop connected to the Internet via wireless.

 

When being asked the computer name to connect to, I think I am supposed to

give it an IP address since we do not have a VPN. But then the only public

IP is the router. What should I enter as the computer name?

 

Thanks.

[Guest nass]

RE: Establishing Remote Desktop Connection

 

 

 

"mc" wrote:

> I run a small business and I double up as the tech guy running the company's

> small network. The server is still the old NT4.0, although all workstations

> are XP Pro. Internet connection is via a TI, and all computers are on

> private IP with the server static and all workstations dynamic. I have

> enables the host desktop to accept remote connection. The computer that is

> intended to be the remote is a laptop. With the laptop connected locally on

> the LAN I can invoke remote desktop from the laptop and sign-on to the host

> desktop by specifying the host machine name. The problem I ran into is when

> I am truely remote with the laptop connected to the Internet via wireless.

>

> When being asked the computer name to connect to, I think I am supposed to

> give it an IP address since we do not have a VPN. But then the only public

> IP is the router. What should I enter as the computer name?

>

> Thanks.

 

It is really a mix of software and hardware in your issue, what Security

software are you using on the Old NT4 server?, what your hardware sepcs

(router and can you access the UI for the router and assign the Laptop IP/MAC

address to be trusted, you can use VNC or VPN to connect and be secure on

the remote Connection, especiall you mentioned Wireless, you can easily be

sniffed and monitored and broken into your server (old NT4).

Best if you ask your Question here on the Wireless Networking group, you

will get better advice after providing more info about the Software and

hardware involved:

Wireless Networking Newsgroup:

http://www.microsoft.com/communities/newsgroups/en-us/default.aspx?dg=microsoft.public.windows.networking.wireless&cat=en_US_f7139501-144b-4e8e-baf9-03f78faf7e85&lang=en&cr=US

HTH.

nass

----

http://www.nasstec.co.uk

[Guest Nepatsfan]

Re: Establishing Remote Desktop Connection

 

"mc" <mc@discussions.microsoft.com> wrote in message

news:7FD4E538-654C-453A-A385-0D699E5095AF@microsoft.com...

>I run a small business and I double up as the tech guy running the company's

> small network. The server is still the old NT4.0, although all workstations

> are XP Pro. Internet connection is via a TI, and all computers are on

> private IP with the server static and all workstations dynamic. I have

> enables the host desktop to accept remote connection. The computer that is

> intended to be the remote is a laptop. With the laptop connected locally on

> the LAN I can invoke remote desktop from the laptop and sign-on to the host

> desktop by specifying the host machine name. The problem I ran into is when

> I am truely remote with the laptop connected to the Internet via wireless.

>

> When being asked the computer name to connect to, I think I am supposed to

> give it an IP address since we do not have a VPN. But then the only public

> IP is the router. What should I enter as the computer name?

>

> Thanks.

 

 

If you haven't done so already, you might want to post your question to the

Windows XP Working Remotely newsgroup.

 

There are a couple of factors which will impact your ability to access the host

desktop from a remote location. First, you have to use the public IP address

when initiating the connection. If you've got a static IP address from your ISP,

that's not a big problem.

 

If your ISP assigns you a dynamic IP address, you might consider using a dynamic

DNS service such as No-IP.com. That way you could enter your chosen address,

something like mycompay.myvnc.com, and it would work even if your ISP changed

your IP address.

 

https://www.no-ip.com/index.php

 

Next, you have to configure your router to forward traffic on port 3389 to the

host desktop. Here's a web site with instructions for various routers.

 

http://www.portforward.com/routers.htm

 

If you wanted to access multiple computers at your office, you'd change the

default listening port on the machines.

 

How to change the listening port for Remote Desktop

http://support.microsoft.com/kb/306759

 

You'd then add configure these additional port numbers to point to the

corresponding computers. When you want to connect, enter your public IP address,

or dynamic DNS, a colon, followed by the port number.

 

As I noted earlier, you've got a better chance of getting help on the Working

Remotely newsgroup. When you start talking about NT 4.0 servers, T1 lines, and

VPNs, I'm not sure what impact those factors would have on accessing your office

desktops from a remote location.

 

Good luck

 

Nepatsfan