TL-SG2428P Password/Username issue
Hello dear community!
I run 2x TL-SG2428P switches and encountered an issue which I can't resolve:
It seems on both switches the password eem to have changes. I use a password manager and I am very organized with passwords in general.
Whilst the omada controller can find one of the switches and connects successfully, it won't connect/adopt to the other switch, saying user/password are needed and the ones I stored are incorrect. Still it will show up in the list of unknwon devices in the omada app. It won't show up in my home network in my router but still the omada controller sees the switch as unknown device ready for adoption.
Also logging in manually in the other switch, which still connects successfully to the omada controller, is not possible with the stored username/password.
Does anyone have an idea?
Thank you in advance for your help.
Dudson
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
RESOLVED:
I managed to enter the web interface of the switch by changing my IP area.
I found that in the switch a VLAN setting was enabled with the funny new domain 10.0.1.xxx
I deleted this setting and rebooted the switch and now it can be adopted normally. From all I have found, the reason seems to be an activaed DHCP service on the NAS.
Things work fine for now. Thank for all the help!
- Copy Link
- Report Inappropriate Content
Hi @Dudson
Thanks for posting in our business forum.
Could be this case? Do not use auto-fill which may break the login if it fills the extra characters.
It seems to be a problem with the browser which will automatically fill in the characters. There is no way for it yet.
- Copy Link
- Report Inappropriate Content
Hello @Clive_A
Thank you for your reply.
I tried this in different browser and carefully observed any auto-fill function and key lock but unfortunately it still won't work.
I was playing around with things a bit further and this is the current picture I see with my two TL-SG2428P switches:
Switch 1
- can be adopted by omada controller and seems to work fine
- visible in my local network device list of my router
- just user/password access via web interface is not possible anymore, because user/pass seem to have changed (but still the ones stored in the omada controller work)
Switch 2
- visible in the omada controller interface as unadopted switch, MAC address and IP are visible
- adoption fails, omada says (after I am asked to enter user/pass), the device does not react to adoption commands
- not visible in my local network device list of my router
I used to configure my switches before via web interface with user/pass which I store in my password manager. It has always worked fine until yesterday.
If you have any more ideas, I'd appreciate it. I understand switched can go defect in time, however these are less than 2 years old. What puzzles me more is the user/pass change issue, because I am afraid this will happen with a new device.
I also haven't found a feasable option to hard reset user/pass, as I don't have a windows pc and console cable.
- Copy Link
- Report Inappropriate Content
Hi @Dudson
Thanks for posting in our business forum.
Dudson wrote
Hello @Clive_A
Thank you for your reply.
I tried this in different browser and carefully observed any auto-fill function and key lock but unfortunately it still won't work.
I was playing around with things a bit further and this is the current picture I see with my two TL-SG2428P switches:
Switch 1
- can be adopted by omada controller and seems to work fine- visible in my local network device list of my router
- just user/password access via web interface is not possible anymore, because user/pass seem to have changed (but still the ones stored in the omada controller work)
Switch 2
- visible in the omada controller interface as unadopted switch, MAC address and IP are visible
- adoption fails, omada says (after I am asked to enter user/pass), the device does not react to adoption commands
- not visible in my local network device list of my router
I used to configure my switches before via web interface with user/pass which I store in my password manager. It has always worked fine until yesterday.
If you have any more ideas, I'd appreciate it. I understand switched can go defect in time, however these are less than 2 years old. What puzzles me more is the user/pass change issue, because I am afraid this will happen with a new device.
I also haven't found a feasable option to hard reset user/pass, as I don't have a windows pc and console cable.
If it does not respond to the commands, that's a different error message and it has nothing to do with the password.
What should I do when the Omada Controller (V4) fails to adopt the devices?
- Copy Link
- Report Inappropriate Content
@Clive_A
Thank you for your further response.
I could not get the switch to run. As this was critical for my home network I decided to buy a new switch, it was the same model.
I adopted it and after 2 weeks only it ran into the same problem yesterday. The IP address of the switch changes to 10.0.1.xxx whilst my normal IP range is 192.168.178.xxx.
Also many of the AP retrieved this new IP address 10.0.1.xxx and stopped connecting. I could only reconnect them with a factory reset. This just happened over night. Things were working normal the evening before and after waking up all things had changed.
I could get the APs back to connect but the switch is not going to connect:
I can see the switch in the Omada controller App with the IP 10.0.1.140 as available. Adopting will not work. I have properly recorded all used passwords but it won't help. As long as it is shown with that IP, the user and password doesn't seem to be the issue.
Restarting the switch with a disconnected Omada controller to reset in a stand alone device also won't work as I cannot connect to the switch via web interface.
*Edit: My router sees the switch with its MAC address but doesn't show an IP address.
Also a ping to this address will not work.
Do you have any idea how I can reset or enter this switch? It is just 2 weeks old.
Thank you for your help.
- Copy Link
- Report Inappropriate Content
RESOLVED:
I managed to enter the web interface of the switch by changing my IP area.
I found that in the switch a VLAN setting was enabled with the funny new domain 10.0.1.xxx
I deleted this setting and rebooted the switch and now it can be adopted normally. From all I have found, the reason seems to be an activaed DHCP service on the NAS.
Things work fine for now. Thank for all the help!
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 304
Replies: 5
Voters 0
No one has voted for it yet.