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 ...
.

Relevant Pages

  • Re: SPAMBOT Symptoms?
    ... I'm going to study this and test it on my home server before trying on ... To block port 25 from workstations, ... have the tool for it...the Trend CSM client firewall. ... then delete the exception for the SMTP port. ...
    (microsoft.public.windows.server.sbs)
  • Re: Remote Desktop Connection
    ... Not commonly, Exchange can take port 3389 at the server, which is the port ... On the SBS 2003 server, run the netstat command below and notice the output. ... This is the terminal services or RDP port. ... I'm trying to establish a Remote Desktop Connection to my SBS 2003 ...
    (microsoft.public.windows.server.sbs)
  • Re: Urgent Information - Relaying Spam (Mail Server)
    ... A firewall usually is configured to block inbound traffic. ... company works with email then it allows port 25 outbound. ... Workstations can get infected and start to ... pop for incoming I have the server collect that pop mail. ...
    (microsoft.public.windows.server.sbs)
  • Re: Remote Desktop Connection
    ... I went ahead and looked at which processor was using port 3389; ... the server. ... This is the terminal services or RDP port. ... I'm trying to establish a Remote Desktop Connection to my SBS ...
    (microsoft.public.windows.server.sbs)
  • Re: SPAMBOT Symptoms?
    ... To block port 25 from workstations, ... then delete the exception for the SMTP port. ... and that pronounces that server is not an open relay. ... The sender of messages in almost every SMTP queue entry was a single ...
    (microsoft.public.windows.server.sbs)
Loading