Connecting NAS kills my connection!

Discussion in 'Home Networking' started by strid, Sep 3, 2008.

  1. strid

    strid Guest

    I have connected a NAS drive directly to a PC as a temporary measure while I
    do a lot of re-jigging of my data. This PC get's it's internet connection
    from a USB wireless adapter. However, I've noticed that when the NAS is
    switched on, I can't get any connection via the wireless - despite it
    showing as connected. Switch off the NAS and bingo, pages show up OK.

    I'm wondering why is it that these 2 cannot just work independantly to one
    another??

    Wireless Adapter (manual I.P.)
    192.168.1.101 subnet 255.255.255.0

    Wired Network Port (Auto I.P. from NAS DHCP)
    192.254.0.100 subnet 255.255.0.0
     
    strid, Sep 3, 2008
    #1
    1. Advertisements

  2. strid

    Rob Morley Guest

    First things first - the reserved private address space starting 192 is
    a class C network i.e. only 192.168.0.0/255.255.0.0 so 192.254.0.0/16
    isn't reserved for private use and may appear on the internet. You're
    already running a wireless network on one subnet of the reserved
    address range, so set the NAS to use another of the subnets e.g.
    192.168.0.0/255.255.255.0

    But that's probably nothing to do with your problem, which is most
    likely the default gateway setting. Assuming you're using Windows
    2k/XP/Vista, open a terminal and enter

    route delete 0.0.0.0 mask 0.0.0.0
    route add 0.0.0.0 mask 0.0.0.0 192.168.1.1

    (substitute the address of your router if it's not 192.168.1.1).
    That deletes the existing default route (which was set by the NAS when
    the NIC acquired its address via DHCP) and sets a new one that points
    at your router instead.
     
    Rob Morley, Sep 3, 2008
    #2
    1. Advertisements

  3. strid

    Conor Guest

    Manually assign an IP address to the wired port and in the default
    gateway, don't enter anything.
     
    Conor, Sep 3, 2008
    #3
  4. strid

    strid Guest

    That was the way I had it when the NAS was pugged into my router in another
    part of the house, but when I plugged it into the PC it wasn't showing up
     
    strid, Sep 4, 2008
    #4
  5. strid

    Bernard Peek Guest

    That masks restricts the adapter to work only with 192.168.1.*
    addresses.
    That masks restricts the adapter to work only with 192.254.*.*
    addresses.

    If you replace the mask for both of them with 255.0.0.0 then they could
    see each other. But even better would be to make sure that every device
    used an address in the 192.168.1 range.

    You can only have one DHCP server in the network. Set it up to issue
    addresses in a limited subset of the 192.168.1 range, and choose any
    static addresses from the rest of that range. For instance my DHCP
    server here serves addresses from 192.168.0.2 up to 192.168.0.20 while
    my static addresses start at 192.168.0.40 and go up from there.
     
    Bernard Peek, Sep 4, 2008
    #5
  6. strid

    Rob Morley Guest

    That's because the NAS couldn't see the router to get a DHCP address -
    you'd have to bridge the two network devices in the PC for that to work.
     
    Rob Morley, Sep 5, 2008
    #6
  7. Those different netmasks have different broadcast addresses so they can not
    "see" each other by using ARP to discover the other's MAC address. You
    must set all devices on the LAN with the same mask and in the same subnet.

    Tone
     
    Anthony R. Gold, Sep 9, 2008
    #7
  8. strid

    Rob Morley Guest

    He said he wants them to work independently i.e. different subnets.
     
    Rob Morley, Sep 9, 2008
    #8
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.