Solved

Need Help With Network Issue: New Computers connecting to network have internet access, but no local network access.

Hello all,

First a little back story...I work for a small business where the owner has built his own local network. He setup all the servers, client machines, etc...

Although it's not technically my job, I've kind of been entrusted with a lot of the computer related aspects at the company. I'm probably the second most computer literate at the company by far so, it falls to me. I am by no means an expert though. I have no IT related degrees or formal training. I just kind of have always been somewhat adept at it.

Onto the problem at hand:

We've been having an issue with connecting new computers to our network. The issue being when we connect the computer to the network, whether it be wired or wireless, it has local network access but no internet access. To remedy this we tried setting the IP of the machines having issues to static ones. Unfortunately when we did this it just reversed the issue. Instead of having Local but not Internet access we had Internet but not Local access. This issue has only come of late and the only change is that we've setup a wireless router as AP, but on my work laptop I had the same problem before we even got the new router.

Like I said earlier I'm not trained in this so I'm not sure where to go next. The owner also doesn't know what to do and has asked me to look into it.

I understand that this problem could be specific to our setup so I will try and give any information about it that you all might need to know.

Any help would very much appreciated.
4 answers Last reply Best Answer
More about network issue computers connecting network internet access local network access
  1. hmm interesting..

    I think if i was asked to look at this the first thing I would do is log in to the router/ap, which i assume is also acting as the DHCP server.

    I'd have a look at the DHCP settings and check that the pool of addresses is big enough.

    Next id see if the router is set to remember which ip it gives to computers and how long its set to remember for? If this is a long time it could be that everyone connecting has filled up the current list of available addresses.
    I'd either turn this option off, or I'd flush the table and shorten the time it remembers for.

    Once thats done, Id ensure all of the computers on the network are set to automatic ip, and reboot them.
    If still having issues can you run iconfig and post the results?

    Also im assuming your router/ap is the only DHCP server on the network? you havent chained any routers together or anything like that? what router are you using?
  2. Urumiko said:
    hmm interesting..

    I think if i was asked to look at this the first thing I would do is log in to the router/ap, which i assume is also acting as the DHCP server.

    I'd have a look at the DHCP settings and check that the pool of addresses is big enough.

    Next id see if the router is set to remember which ip it gives to computers and how long its set to remember for? If this is a long time it could be that everyone connecting has filled up the current list of available addresses.
    I'd either turn this option off, or I'd flush the table and shorten the time it remembers for.

    Once thats done, Id ensure all of the computers on the network are set to automatic ip, and reboot them.
    If still having issues can you run iconfig and post the results?

    Also im assuming your router/ap is the only DHCP server on the network? you havent chained any routers together or anything like that? what router are you using?


    Thanks for responding, Urumiko.

    We're using a ASUS RT-N66U router setup in AP mode. In this mode it does not handle the DHCP at all. My boss assures me that the pool is large enough and he doesn't think that the time setting for remembering an IP is too long.

    Here are two ipconfig results:

    (This first one is with a manually set IP)

    Windows IP Configuration


    Wireless LAN adapter Wireless Network Connection 2:

    Media State . . . . . . . . . . . : Media disconnected
    Connection-specific DNS Suffix . :

    Wireless LAN adapter Wireless Network Connection:

    Connection-specific DNS Suffix . :
    Link-local IPv6 Address . . . . . : fe80::5048:ea82:e05f:93aa%13
    IPv4 Address. . . . . . . . . . . : 10.0.6.15
    Subnet Mask . . . . . . . . . . . : 255.255.255.0
    Default Gateway . . . . . . . . . : 10.0.6.1

    Ethernet adapter Local Area Connection:

    Media State . . . . . . . . . . . : Media disconnected
    Connection-specific DNS Suffix . : sentry.local

    Tunnel adapter isatap.sentry.local:

    Media State . . . . . . . . . . . : Media disconnected
    Connection-specific DNS Suffix . :

    Tunnel adapter Local Area Connection* 12:

    Media State . . . . . . . . . . . : Media disconnected
    Connection-specific DNS Suffix . :

    Tunnel adapter Teredo Tunneling Pseudo-Interface:

    Connection-specific DNS Suffix . :
    IPv6 Address. . . . . . . . . . . : 2001:0:9d38:6ab8:2044:c8d:74c8:2281
    Link-local IPv6 Address . . . . . : fe80::2044:c8d:74c8:2281%15
    Default Gateway . . . . . . . . . : ::

    Tunnel adapter isatap.{1074B805-2B3B-4733-A508-3B7711B5A421}:

    Media State . . . . . . . . . . . : Media disconnected
    Connection-specific DNS Suffix . :

    Tunnel adapter isatap.{E44E851A-8430-4280-9208-258990E57459}:

    Media State . . . . . . . . . . . : Media disconnected
    Connection-specific DNS Suffix . :

    Tunnel adapter Reusable ISATAP Interface {EF76F1A3-6E20-4741-9B64-D7949743A1F7}:


    Media State . . . . . . . . . . . : Media disconnected
    Connection-specific DNS Suffix . :


    Here is the second one with an automatically set IP:

    Windows IP Configuration


    Wireless LAN adapter Wireless Network Connection 2:

    Media State . . . . . . . . . . . : Media disconnected
    Connection-specific DNS Suffix . :

    Wireless LAN adapter Wireless Network Connection:

    Connection-specific DNS Suffix . : sentry.local
    Link-local IPv6 Address . . . . . : fe80::5048:ea82:e05f:93aa%13
    IPv4 Address. . . . . . . . . . . : 10.0.6.106
    Subnet Mask . . . . . . . . . . . : 255.255.255.0
    Default Gateway . . . . . . . . . : 10.0.6.61

    Ethernet adapter Local Area Connection:

    Media State . . . . . . . . . . . : Media disconnected
    Connection-specific DNS Suffix . : sentry.local

    Tunnel adapter isatap.sentry.local:

    Media State . . . . . . . . . . . : Media disconnected
    Connection-specific DNS Suffix . :

    Tunnel adapter Local Area Connection* 12:

    Media State . . . . . . . . . . . : Media disconnected
    Connection-specific DNS Suffix . :

    Tunnel adapter Teredo Tunneling Pseudo-Interface:

    Media State . . . . . . . . . . . : Media disconnected
    Connection-specific DNS Suffix . :

    Tunnel adapter isatap.{1074B805-2B3B-4733-A508-3B7711B5A421}:

    Media State . . . . . . . . . . . : Media disconnected
    Connection-specific DNS Suffix . :

    Tunnel adapter isatap.{E44E851A-8430-4280-9208-258990E57459}:

    Media State . . . . . . . . . . . : Media disconnected
    Connection-specific DNS Suffix . :

    Tunnel adapter Reusable ISATAP Interface {EF76F1A3-6E20-4741-9B64-D7949743A1F7}:


    Media State . . . . . . . . . . . : Media disconnected
    Connection-specific DNS Suffix . :

    Let me know if there is any other information I can give. Thanks again.
  3. Best answer
    Hi.

    The default gateway looks to be different for these devices?
    An incorrect default gateway might explain this issue as computers cold talk to devices on the same subnet but not outside.

    Check the default gateway handed out by the DHCP server is correct? This should be the router/the first router the PC will hit.
  4. Thanks again, Urumiko.

    We have resolved the issue. What we ended up doing was we completely reset the new router. Then we set it back up in access point mode and for some reason that fixed the issue. There must have been something that got messed up the first time we setup the router.

    Anyway the problem is 100% resolved now.
Ask a new question

Read More

Network Access Internet Access Networking Computers