Remote Access to Server 2003 Network

[Sickboy]

Some time ago I set up a small network for a client (it was my first try). It's a server running Server 2003 with clients running XP Pro. All works fine but now they have a 3rd party software supplier who wants remote access to update and troubleshoot their software. Our client has a static IP but I can't seem to access it remotely either by setting up a VPN or using remote desktop. They connect to the web via a BT Voyager 240 ADSL modem. I must admit that I'm no expert, and have been told that they need a public IP in order to set up a VPN, but that this would neccessitate more stringent and compicated security measures. Is this correct and, if so, what measures would be neccessary?
TIA

[cat5e]

The it is presented seems to be verbal misunderstanding.

Private IP is the internal LAN IP, like the 192.168.xxx.xxxx

A public IP is the external IP assigned to the system when it is connected to the Internet.

A public IP can be dynamic (I.e. changes frequently at the discretion of the ISP) or Static. (I.e. a public address number that assigned to you by the ISP and stays the same).

Therefore, if the server has an Internet connection it must have already a public IP, if it is not static talk to your ISP and get a static account.

Might be that the problem related to the combo Voyager 240. The remote service provider probably wants your client to bypass the Router and put the computer directly on the Internet.

Doing so is highly unsecured, and should be avoided. I am not familiar with the Voyager 240 (combos usually “sux”). Might be that replacing the thingie with a Good Router that has flexible way to forward ports might solve the problem.

[Sterling_Aug]

I'm sure there are loads of consultants in your area that could look over your setup, check each device, verify the settings of everything, then recommend several solutions that would work for your company.

Nothing is free, so expect to pay for this service. Any advise you may get here or at other support sites is just that, advise. Without checking out the details in person, we can never be 100% sure of the best way to solve your issue.

[Baddog]

I might be wrong but couldn't they use PC Anywhere or XP's Remote Connection. That what we do when Corporate office need to change or trouble shoot something for us.

[cat5e]

I might be wrong but couldn't they use PC Anywhere or XP's Remote Connection. That what we do when Corporate office need to change or trouble shoot something for us.It does not matter what application they use, any good remote control can be used through a good Router if set correctly.

[Sickboy]

I suspect the router is the issue here. I will investigate configuration options and report back. Thanks

[Gokudan]

Hi!

They should be able to connect via Remote Desktop trough your public IP; of course, assuming it's a public static ip. Maybe RD port is blocked on the router.

Att.
Gokudan

[Sickboy]

Configured the Voyager 240 to forward port 3389 but still doesn't connect. I haven't configured the software firewall yet (Trend Micro SMB Messaging Suite), so I'll report back after I've done that.

[Sickboy]

Still struggling with this. I'm determined to set up a VPN connection using Server 2K3 built in feature. Am I right in thinking that the internal clients need to have static IPs rather than dynamically assigned in order to forward ports?

[Sterling_Aug]

I think you will be struggling with this for quite some time if you insist on using the built in software for remote desktop administration.

You may want to try a FREE utility such as Ultra VNC instead.

[Sickboy]

Sounds good, but won't we have the same problems configuring the router to allow this through? Incidentally I've given up on Remote Desktop and would prefer to set up a VPN using 2K3's inbuilt VPN Server if possible.