Re: Network from home to office, etc.

From: Shenan Stanley (news_helper_at_hushmail.com)
Date: 10/31/04 

Date: Sun, 31 Oct 2004 10:31:56 -0600

Rich wrote:
> I need some elementary, one syllable words to help me in this
> scenario:
> I have 4 computers in my office, one of which I must network to my
> home and to an employees home. I have an 8 port router at the office
> and a 4 port at home. Employee has one computer at home. We are using
> cable modem all around. Can anyone help me step through the proper
> hookup.

Question:
"... one of which I must network to my home and to an employees home..."

What does that mean?
Do you mean you must be able to remotely connect to the machine as if you
were sitting in front of it?
Do you need access to the hard disk drive shares?

In simplest terms, you will have to do the following:
(Assuming you want remote desktop capabilities)

1) Discover the IPs of the routers you have connected(record these.)
    This entails finding out if those routers have static or dynamic IPs.
    If Dynamic, you need to read the manuals and find out if they support
    "Dynamic DNS".
    Otherwise, sooner or later the IP will change and you may not be able
    to connect until you re-discover the IP again.

2) Configure the routers in question (using their manuals) to properly
forward
    port requests to the internal IP of the machine you need to access.
    What ports are determined by what you are trying to do.
    I suggest port 3389 for remote desktop to be your easiest solution.
   (Of course, that assumes Windows XP Professional, Windows 2000 Server
     or Windows 2003 server is the host PC at work. It also assumes you
have
     turned on remote desktop.)

3) The "home computer" must have the remote desktop client as well, in
    the 3389 port forwarding scenario given above. It's free, Microsoft
will
    let you download it and it runs on most Microsoft Windows OSes.

The home router situation should not matter much, as it will be requesting
the connection be made. The pass-throughs should be automatically
configured.

Only the host should need special attention in your case.

Now you should use Google and Microsoft Searches to fill in the holes. You
routers
came with manuals to help you do such things as well as they usually have
web pages
with information that can help you further.

Good luck. 

-- 
<- Shenan ->
-- 
The information is provided "as is", it is suggested you research for
yourself before you take any advice - you are the one ultimately
responsible for your actions/problems/solutions.   Know what you are
getting into before you jump in with both feet.

Relevant Pages

  • RE: Remote Desktop vs VPN on Windows 2003
    ... Honeypots for Windows book. ... So, if a RDP buffer overflow worm came out, it would probably attack TCP port 3389. ... Now tell me again how changing the default port doesn't add ANY security value? ... Remote Desktop vs VPN on Windows 2003 ...
    (Security-Basics)
  • RE: Remote Desktop vs VPN on Windows 2003
    ... Remote Desktop vs VPN on Windows 2003 ... PORT STATE SERVICE ... If someone was looking to hack your network your security through obscurity ...
    (Security-Basics)
  • Re: Remote Desktop Connection Security
    ... Remote Desktop is natively encrypted at a 128-bits... ... You might consider changing the default client connection encryption level to "High" versus the ... If you need to feel a bit safer you can always change the listening port on the XP Pro box to ... Al Jarvi (MS-MVP Windows Networking) ...
    (microsoft.public.windowsxp.work_remotely)
  • RE: Remote Desktop vs VPN on Windows 2003
    ... Remote Desktop vs VPN on Windows 2003 ... PORT STATE SERVICE ... If someone was looking to hack your network your security through obscurity ...
    (Security-Basics)
  • RE: Remote Desktop vs VPN on Windows 2003
    ... Remote Desktop vs VPN on Windows 2003 ... Security through obscurity is a type of security, ... simply changing the port number one port up. ...
    (Security-Basics)