Server VPN Setup Causes Internal Network to Stop - WIN2K Pro Serve

  • Thread starter Thread starter SCNetworks
  • Start date Start date
S

SCNetworks

Guest
Hello All,

First - I apologize for my ignorance. I've been doing DB work for the past 5
years and find myself thrown in to all things Server / System Admin related
recently. Setup is as follows: 1 DC running Win2K Pro Server with AD Domain.
XP SP2 Clients, DSL Internet connection on non-static assigned IP address by
telco. Siemens DSL Modem.

To get to the server remotely right now I RDP in to it's IP address by doing
a "whatismyipaddress.com" before going home.

Others in the office now want to work remotely from home - remoting to their
desktops directly. Company wants to spend minimally amount on hardware if
any. This past weekend I followed the instructions on setting up TS using VPN
and it killed the internal network when services were activated. We use
several DB's / Applications from the server.

I know this should be simple - but would like to ask the easiest way to set
this up. VPN is now not required - simple re-directs using RDP OK. In one
place I've seen someone use a web address with a port number at the end
indicating a respective static IP to a desktop on the inside.

Any way you slice it, am looking to implement a simple remote solution using
RDP. Any and all help is greatly appreciated ...
 
RE: Server VPN Setup Causes Internal Network to Stop - WIN2K Pro Serve

this can be easy and simple and only be limited by
1. Nr of workstations to be accessed using RDP (let's assume it's n)
2. Nr of rules you can create on the firewall/router for port forwarding

First of all if the public IP is not static, you may use free Dynamic DNS
hosting to get rid of remembering the IP address everytime

You'd need to change the default RDP port to anything else but 3389 ports
for n workstations

Create port forwarding rules on your router/firewall so that any internet
incoming traffic on respective port is forwarded to one of the workstations
which is configured to listen on that port

For ex. say i've 5 machine which need to be accessed by using RDP

Server - 3389
Machine1 - 3390
Machine2 - 3391
Machine3 - 3392
Machine4 - 3393
Machine5 - 3395

I'd modify those 5 machines so that their TS listens on respective port
Use the following reg key on each of them to modify the default Port Number
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal
Server\Wds\rdpwd\Tds\tcp
PortNumber REG_DWORD (Port Number) in decimal

:)

"SCNetworks" wrote:

> Hello All,
>
> First - I apologize for my ignorance. I've been doing DB work for the past 5
> years and find myself thrown in to all things Server / System Admin related
> recently. Setup is as follows: 1 DC running Win2K Pro Server with AD Domain.
> XP SP2 Clients, DSL Internet connection on non-static assigned IP address by
> telco. Siemens DSL Modem.
>
> To get to the server remotely right now I RDP in to it's IP address by doing
> a "whatismyipaddress.com" before going home.
>
> Others in the office now want to work remotely from home - remoting to their
> desktops directly. Company wants to spend minimally amount on hardware if
> any. This past weekend I followed the instructions on setting up TS using VPN
> and it killed the internal network when services were activated. We use
> several DB's / Applications from the server.
>
> I know this should be simple - but would like to ask the easiest way to set
> this up. VPN is now not required - simple re-directs using RDP OK. In one
> place I've seen someone use a web address with a port number at the end
> indicating a respective static IP to a desktop on the inside.
>
> Any way you slice it, am looking to implement a simple remote solution using
> RDP. Any and all help is greatly appreciated ...
 
RE: Server VPN Setup Causes Internal Network to Stop - WIN2K Pro S

RE: Server VPN Setup Causes Internal Network to Stop - WIN2K Pro S

Dear Ninin K,

Thank you so much for this solution, it fits the bill perfectly. Only 3-4
computers
will need remote access and I will implement later this week. Thank you also
for the
Dynamic DNS hosting information ...

:) :) :)

"Nitin K" wrote:

> this can be easy and simple and only be limited by
> 1. Nr of workstations to be accessed using RDP (let's assume it's n)
> 2. Nr of rules you can create on the firewall/router for port forwarding
>
> First of all if the public IP is not static, you may use free Dynamic DNS
> hosting to get rid of remembering the IP address everytime
>
> You'd need to change the default RDP port to anything else but 3389 ports
> for n workstations
>
> Create port forwarding rules on your router/firewall so that any internet
> incoming traffic on respective port is forwarded to one of the workstations
> which is configured to listen on that port
>
> For ex. say i've 5 machine which need to be accessed by using RDP
>
> Server - 3389
> Machine1 - 3390
> Machine2 - 3391
> Machine3 - 3392
> Machine4 - 3393
> Machine5 - 3395
>
> I'd modify those 5 machines so that their TS listens on respective port
> Use the following reg key on each of them to modify the default Port Number
> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal
> Server\Wds\rdpwd\Tds\tcp
> PortNumber REG_DWORD (Port Number) in decimal
>
> :)
>
> "SCNetworks" wrote:
>
> > Hello All,
> >
> > First - I apologize for my ignorance. I've been doing DB work for the past 5
> > years and find myself thrown in to all things Server / System Admin related
> > recently. Setup is as follows: 1 DC running Win2K Pro Server with AD Domain.
> > XP SP2 Clients, DSL Internet connection on non-static assigned IP address by
> > telco. Siemens DSL Modem.
> >
> > To get to the server remotely right now I RDP in to it's IP address by doing
> > a "whatismyipaddress.com" before going home.
> >
> > Others in the office now want to work remotely from home - remoting to their
> > desktops directly. Company wants to spend minimally amount on hardware if
> > any. This past weekend I followed the instructions on setting up TS using VPN
> > and it killed the internal network when services were activated. We use
> > several DB's / Applications from the server.
> >
> > I know this should be simple - but would like to ask the easiest way to set
> > this up. VPN is now not required - simple re-directs using RDP OK. In one
> > place I've seen someone use a web address with a port number at the end
> > indicating a respective static IP to a desktop on the inside.
> >
> > Any way you slice it, am looking to implement a simple remote solution using
> > RDP. Any and all help is greatly appreciated ...
 
Back
Top