Welcome to TP-LINK Tech Support Forum
+ Reply to Thread
Results 1 to 4 of 4
  1. #1

    Thumbs up Unmanaged Switch wrong IP assignment

    Model :

    Hardware Version :

    Firmware Version :

    ISP : [/COLOR]

    Model : TP-SG1048

    Hardware Version : Not Clear

    Firmware Version : v6

    ISP : none


    I connected 20 computers to the switch. Nothing else (nor router, internet or any other network device). For some reason during this installation, the range of IPs assigned changed from 169.X to 192.X
    2 computers still had assigned IPs 169.X and they dont have connection to the rest of the LAN.
    Both were windows pc, network cables were OK. IP settings were set to Dynamic.
    Restarting window or re-plugging network cable did not make the trick.

    The only solution was to restart the switch (poweroff - poweron)...but that a really nasty solution...

    Question 1: Why IP range change suddenly?
    Question 2: Why IPs got stucked in a wrong IP range?

  2. #2
    Members R1D2 is on a distinguished road
    Join Date
    Dec 2015
    Posts
    1,009
    Quote Originally Posted by cepix View Post

    I connected 20 computers to the switch. Nothing else (nor router, internet or any other network device). For some reason during this installation, the range of IPs assigned changed from 169.X to 192.X


    Uhm, the 169.254.0.0/16 IP range is allocated to the "link local block" according to RFC3927. Your systems get an address from this range by auto-configuration if there is no DHCP server running in your network. The 192.168.0.0/16 IP range is the
    IP address space for private networks assigned by IANA. This range is often is used by DHCP servers to dynamically assign an address.

    The TL-SG1048 is an unmanaged (dumb) switch. It neither does auto-configuration, nor does it have a DHCP server. Auto-configuration is done by your OS and DHCP is done by your DHCP server.

    Question 1: Why IP range change suddenly?
    See above.

    Question 2: Why IPs got stucked in a wrong IP range?


    It's not a wrong IP range, it's a private range defined in your DHCP server. Still has nothing to do with the switch.

  3. #3
    It makes sense. Seems that there was a DHCP server around in the network ...is the only reason i can think of for this happening.

    So If i connect a home router (linksys WRT54G) It can serve as DHCP server and all assigments will be done using this device?

  4. #4
    Members R1D2 is on a distinguished road
    Join Date
    Dec 2015
    Posts
    1,009
    Quote Originally Posted by cepix View Post
    So If i connect a home router (linksys WRT54G) It can serve as DHCP server and all assigments will be done using this device?
    Yes. But make sure to disable the other DHCP service in the same subnet and use a non-conflicting (free) static IP for the WRT54.


 

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts

Copyright 1996-2017 TP-LINK Technologies Co., Ltd. All rights reserved.