Business Community > Switches > Changed IP settings from Static to DHCP - Can't save changes
< Switches

Changed IP settings from Static to DHCP - Can't save changes

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.

Changed IP settings from Static to DHCP - Can't save changes

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Changed IP settings from Static to DHCP - Can't save changes
Changed IP settings from Static to DHCP - Can't save changes
2019-08-09 06:55:14 - last edited 2019-08-09 07:25:37
Model: T1500G-10PS(TL-SG2210P)  
Hardware Version: V2
Firmware Version: 2.0.0 Build 20180330 Rel.44639(s)

I can access the switch through a wired ethernet connection to my iMac desktop. I am able to use the GUI and administer the switch. When I connect the switch to my Synology router and try and access the switch from my iMac desktop over wi-fi, I am unable to login into the switch. The IP address of the switch is 192.168.0.4; the IP address of my iMac desktop over wi-fi is 192.168.1.x

 

I believe the reason I can't access the switch over my wi-fi network is due to the switch and my desktop belonging to different subnets. I have tried to change the IP address of my switch to the same subnet as my iMac's wi-fi subnet as in 192.168.1.x, but I am unable to apply the IP changes to my switch (the screen just hangs). Is there any way the switch's subnet can be changed, or must it always belong to 192.168.0.x?

 

When I connect the switch to my Synology router, it functions correctly, and I can attach POE IP cameras to it, and everything works as expected. But I do want to be able to access the switch from my desktop over wi-fi to perform administration as required. Synology technical support have advised me to change the IP addressing scheme of the switch from static to DHCP. With a router assigned IP address, the router should list the switch as a connected device. Currently, the switch with its static IP address, is not listed as a connected device by the router (but it works properly nonetheless).

 

Can you advise why I am unable to change the switch's IP addressing scheme from static to DHCP and apply & save the changes?

 

Thank you!

  0      
 
  0      
 
#1
Options
9 Reply
Re:Changed IP settings from Static to DHCP - Can't save changes
2019-08-09 09:32:03 - last edited 2019-08-09 09:34:32

Apply the change. It will be active as soon as you hit apply and confirm the change. You need to re-connect to the switch's web UI using the new IP address to save the new setting.

 

BTW: it's a bad idea to use DHCP on stationary devices, so consider to set a static IP from your 192.168.1.0 network instead. Same procedure as described above applies.

༺ 0100 1101 0010 10ཏ1 0010 0110 1010 1110 ༻
  0  
  0  
#2
Options
Re:Re:Changed IP settings from Static to DHCP - Can't save changes
2019-08-09 10:17:04

Thanks R1D2 for your response. If only it was that simple! The problem I am experiencing is that the change is unable to be applied. Basically, the switch won't save the configuration change. I do not know why this is the case. I have raised the issue with TP-Link Support and hopefully they can provide some advice.

 

Also, I am using a Synology router and it was Synology Technical Support who advised me to configure the switch from static to DHCP addressing. I can see that all of the DHCP clients of my Synology router maintain their IP addresses. The router can be administered to reserve DHCP addresses. Once the switch has been allocated a DHCP address, it can be reserved. But I need to be able to configure the switch to use DHCP addressing and save the changes before I can try their solution!

  0  
  0  
#3
Options
Re: Changed IP settings from Static to DHCP - Can't save changes
2019-08-09 11:01:26 - last edited 2019-08-09 11:21:38

Sapien wrote

Thanks R1D2 for your response. If only it was that simple! The problem I am experiencing is that the change is unable to be applied. Basically, the switch won't save the configuration change. I do not know why this is the case. I have raised the issue with TP-Link Support and hopefully they can provide some advice.

 

I bet that the switch applies the change, but you won't see it if you still use the old (previous) IP. How should the switch be able to send something back if it belongs to another subnet after the change has been applied?

 

Try the following:

 

  1. Connect your laptop to the switch. Do not connect any other device (router, NAS, whatever) to the switch!
  2. Set the IP of your laptop to 192.168.0.10 or some other IP in this subnet.
  3. Connect to the switch, change IP of the switch to 192.168.1.2 or any other free (unused) IP of the main network's subnet. Apply it (you will not see the success message).
  4. Change your laptop's IP back to an IP from the 192.168.1.0 subnet, for example set it to 192.168.1.10.
  5. Connect to the switch (now 192.168.1.2 or whatever you did assign it), save the new setting, done.

 

Again: it's a bad idea to use DHCP for setting the IP of a switch. That's the reason why its default IP in factory settings is always a static IP.

 

OTOH, in (very rare) cases the switch's flash memory has a defect. To find out, execute the steps 1 to 5 above.

༺ 0100 1101 0010 10ཏ1 0010 0110 1010 1110 ༻
  2  
  2  
#4
Options
Re:Re: Changed IP settings from Static to DHCP - Can't save changes
2019-08-10 07:36:09

Success!

 

After updating my switch with the latest version of firmware, I followed your instructions, but still was not able to access the switch after changing its IP address to my desktop's subnet. So I did a hard reset of the switch (rather than unplugging it from power which I had done previously to re-establish connection). Then I followed your instructions again and finally it worked!

 

I reconnected the switch to my router and can now access it over wi-fi from my desktop. Many thanks for your adviceyes

  0  
  0  
#5
Options
Re:Re:Re: Changed IP settings from Static to DHCP - Can't save changes
2019-08-11 08:39:12

Resetting to factory defaults is always recommended when deploying a device with an unknown setup. Maybe the switch was configured to only allow mgmt access from a certain subnet. Anyway, great that it works now!

༺ 0100 1101 0010 10ཏ1 0010 0110 1010 1110 ༻
  1  
  1  
#6
Options
Re:Changed IP settings from Static to DHCP - Can't save changes
2019-08-12 07:00:25

T1500G-10PS and T1500G-10MPS had problems with gateway work, when you try to access your switch from different network. Sometimes it just stops to work and you can manage it only from the same subnetwork.

Latest fws seems to fix this issue for my clients (T1500G-10PS(UN)_v2_190509 / T1500G-10MPS(UN)_V2_190424)

  0  
  0  
#7
Options
Re:Re:Changed IP settings from Static to DHCP - Can't save changes
2019-08-12 08:03:12 - last edited 2019-08-12 08:04:45

Mitya wrote

T1500G-10PS and T1500G-10MPS had problems with gateway work, when you try to access your switch from different network. Sometimes it just stops to work and you can manage it only from the same subnetwork.

Latest fws seems to fix this issue for my clients (T1500G-10PS(UN)_v2_190509 / T1500G-10MPS(UN)_V2_190424)

 

Uhm, I would not want my T1500G-10PS to route traffic to other subnets or public IPs over a gateway - except probably for NTP packtes from the switch itself, but definitely not packets from clients. Do you mean traffic from the switch itself, e.g. the web UI?

 

༺ 0100 1101 0010 10ཏ1 0010 0110 1010 1110 ༻
  0  
  0  
#8
Options
Re:Re:Re:Changed IP settings from Static to DHCP - Can't save changes
2019-08-12 08:08:58

R1D2 wrote

Mitya wrote

T1500G-10PS and T1500G-10MPS had problems with gateway work, when you try to access your switch from different network. Sometimes it just stops to work and you can manage it only from the same subnetwork.

Latest fws seems to fix this issue for my clients (T1500G-10PS(UN)_v2_190509 / T1500G-10MPS(UN)_V2_190424)

 

Uhm, I would not want my T1500G-10PS to route traffic to other subnets or public IPs over a gateway - except probably for NTP packtes from the switch itself, but definitely not packets from clients. Do you mean traffic from the switch itself, e.g. the web UI?

 

 I am talking about management vlan only, not about packets from clients, you are right. I mean, you will definitely configure default route for switch to be able to have access from different network, like we have it here 192.168.0.0/24 for switch and 192.168.1.0/24 for client. As T1500G-10PS has only 1 VLAN interface, which is management vlan, so you will configure default gateway there.

  0  
  0  
#9
Options
Re:Re:Re:Re:Changed IP settings from Static to DHCP - Can't save changes
2019-08-12 08:19:06 - last edited 2019-08-12 08:21:28

Mitya wrote

 

I am talking about management vlan only, not about packets from clients, you are right. I mean, you will definitely configure default route for switch to be able to have access from different network, like we have it here 192.168.0.0/24 for switch and 192.168.1.0/24 for client. As T1500G-10PS has only 1 VLAN interface, which is management vlan, so you will configure default gateway there.

 

I have mgmt VLAN, but still no routing needed for this. If a client is supposed to use 192.168.1.0/24 and a bad guy sets a static IP from 192.168.0.0/24, I don't want him to be able to leak packets into the mgmt VLAN through a gateway (which would be needed only for Inter-VLAN routing IMHO).

༺ 0100 1101 0010 10ཏ1 0010 0110 1010 1110 ༻
  0  
  0  
#10
Options

Information

Helpful: 0

Views: 4951

Replies: 9

About Us
Press
Copyright © TP-Link Corporation Limited. All rights reserved.