1. You are viewing our forum as a guest. For full access please Register. WindowsBBS.com is completely free, paid for by advertisers and donations.

Small network with remote desktop and fixed IP

Discussion in 'Networking (Hardware & Software)' started by gengis, 2009/07/25.

  1. 2009/07/25
    gengis

    gengis Inactive Thread Starter

    Joined:
    2004/07/06
    Messages:
    105
    Likes Received:
    0
    I'm using a Windows 2003 server which has been set to provide DHCP and DNS which works well and currently enables local sharing and internet access via a router.

    I have a fixed IP address and I have previously used (on another network) remote access by logging in via a fixed IP also. I would like to create the same setup so that I can login remotely. I have fitted a second LAN card for the purpose but don't know what setting to input. Details so far are as follows.

    LAN Card 1
    Server IP 192.168.1.1
    SubNet 255.255.255.0
    Gateway 192.168.1.254
    Prefered DNS 192.168.1.1

    Router DHCP disabled IP address 192.168.1.254

    When connected my router status displays
    IP Address 212.159.26.21 (Which is my fixed IP ADdress)
    Subnet 255.255.255.255
    Gateway 195.166.128.64
    DNS1 212.159.6.10
    DNS2 212.159.6.9

    I have tried putting these details in LAN 2 (without making any changes to LAN1) but lose connection

    I would certainly apprecieate some advise here people, thanks in advance

    G
     
  2. 2009/07/29
    ReggieB

    ReggieB Inactive Alumni

    Joined:
    2004/05/12
    Messages:
    2,786
    Likes Received:
    2
    To do what you are trying each PC would need a public rather than a private IP address and each would be exposed to direct attack from the internet. Probably not what you are after as this would be more expensive (ISP accounts that provide multiple IPs are more expensive that standard accounts) as well as being harder to secure.

    Simplest solution is to use VPN. Use a router - or better still a hardware firewall - that will act as a VPN end point (not VPN pass-through). If you are on a tight budget something like this will do:

    http://www.netgear.com/Products/VPNandSSL/WiredVPNFirewallRouters.aspx

    Ideally something like one of there would be great:

    http://www.sonicwall.com/us/products/TZ_210.html

    http://www.watchguard.com/products/appliances.asp

    Then connect to the network via VPN and you'll then be able to access internal private IP addresses for things like RDP just as if you were on the same network as them.

    However, this only works if the IP subnet you are connecting to is different from the one you are connecting from. So if your home network also uses the 192.168.1.0 address space, the VPN won't work. To avoid this it might be worth changing your network addresses to a subnet that is less common. Eg. 192.168.200.0.
     

  3. to hide this advert.

Share This Page

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.