The Notebook Review forums were hosted by TechTarget, who shut down them down on January 31, 2022. This static read-only archive was pulled by NBR forum users between January 20 and January 31, 2022, in an effort to make sure that the valuable technical information that had been posted on the forums is preserved. For current discussions, many NBR forum users moved over to NotebookTalk.net after the shutdown.
Problems? See this thread at archive.org.

    setting up server connection

    Discussion in 'Networking and Wireless' started by Jarhead, May 27, 2011.

  1. Jarhead

    Jarhead 恋の♡アカサタナ

    Reputations:
    5,036
    Messages:
    12,168
    Likes Received:
    3,134
    Trophy Points:
    681
    Hello all,


    So far, my server project is going along pretty smoothly...

    ...only in my local network. Once I leave my home, I have no access via VNC (also can't use Wake-on-LAN).

    I narrowed the problem down to how my home network is set up. I have a DSL modem (Westell 6200) that is directly-connected to my ISP, and the single Ethernet port on it is taken up by my wireless router (Netgear WGR614v7), where all my computers are hooked up to. The Westell's LAN port is set to 192.168.1.254, with the DHCP on that giving my Netgear 192.168.1.97. Currently, my Netgear gives it's own DHCP to the clients, using the 192.168.5.0 network (router being .1, and a static NAT address of .2 to the server).

    I can communicate between my laptop and my server just fine when both are on the local LAN, but in order to connect outside of home, I have to share my public IP (going into the Westell) to the server (connected to Netgear). Tried disabling DHCP on the Netgear (didn't work) and changing the Netgear's DHCP to the same network as the Westell, but it refuses to use that and reverts to the default 10.0.0.0 network if I try that.

    Is there any way to try forcing the Netgear to accept the 192.168.1.0 network settings in its DHCP, or should I simply toss out the Westell and use the Netgear to connect to my ISP?
     
  2. downloads

    downloads No, Dee Dee, no! Super Moderator

    Reputations:
    7,729
    Messages:
    8,722
    Likes Received:
    2,230
    Trophy Points:
    331
    Have you forwarded proper port for VNC (usually 5900)?
     
  3. Jarhead

    Jarhead 恋の♡アカサタナ

    Reputations:
    5,036
    Messages:
    12,168
    Likes Received:
    3,134
    Trophy Points:
    681
    Yes, I set both the modem and the router to forward VNC. I'm thinking that the VNC packets can't forward through two private networks...
     
  4. downloads

    downloads No, Dee Dee, no! Super Moderator

    Reputations:
    7,729
    Messages:
    8,722
    Likes Received:
    2,230
    Trophy Points:
    331
    So you set it up to forward WAN (5900) to 192.168.1.97 (5900) on a modem and then 192.168.5.1 (5900) to 192.168.5.2 (5900) on the router?
     
  5. focusfre4k

    focusfre4k Notebook Evangelist

    Reputations:
    149
    Messages:
    569
    Likes Received:
    0
    Trophy Points:
    30
    I would ditch the router you have now and get a layer 3 device that supports multiple "zones"(juniper term).

    It would make this much easier.