- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
GC752X Switch Login Failure
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I have a curious issue with the GC752X switch. After running for a while, the switch seems to lock up and will not allow any further logins. We have all the switches on a separate Management VLAN. We have one connection from a Linux server using FireFox that the technicians use when making VLAN changes to the switch. A few of the technicians also connect using a separate VNC session on the Linux server to the switch using FireFox as well. When the issue occurred with one of the technicians, I tried from my own VNC session and could not get in. I could ping the switch. I could access it and get a login screen but when I entered the password it would give me Login Failure. So I accessed the VNC session that the technicians share for VLAN configuration changes and it would let me login fine. There was not an issue with the password.
I checked the Linux server and there were about 10 VNC sessions with connections to the switch. I disconnected those sessions as I was told sometimes when there are too many connections to the switches they get the Login Failure issue. I was still unable to login and kept getting the error message. I stopped and started working on another issue and came back to it after about 2 hours or so and then I was able to connect.
The next day another technician had problems again getting the Login Failure error message and he simply rebooted the switch and was able to get in again.
Is this common? Has anyone else seen this issue before? Any ideas how we can get around this issue? We run space flight simulations that can last days or weeks at a time. Flight systems need constant communications with each other at all times to remain in sync with each other. We cannot afford to be rebooting switches when they start acting up.
Model Name Boot Version Software Version
GC752X B1.0.0.4 1.0.5.25
Thanks
Solved! Go to Solution.
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi @akio63,
Were there any events that occurred that may have caused this issue the first time you noticed it?
Would it be possible to update the FW of the switch to v1.0.5.35? Have you also tried a different browser when logging in and if the issue still persists?
Regards,
JeraldM
NETGEAR Community Team
All Replies
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi @akio63,
Were there any events that occurred that may have caused this issue the first time you noticed it?
Would it be possible to update the FW of the switch to v1.0.5.35? Have you also tried a different browser when logging in and if the issue still persists?
Regards,
JeraldM
NETGEAR Community Team
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: GC752X Switch Login Failure
When this has happened in the past there were no network events prior to it's occurrence that I know of. Yes I can upgrade the firmware. I need to wait for a maintenance window but I was planning to do that anyway.
We are a government shop so we are limited in what we can use for software. Normally I would have tried a different browser but due to the restrictions I couldn't. I was already reprimanded, verbally, for using Chrome and it was quickly removed when it was discovered.
I'll let you know what happens when I upgrade the firmware.
Thank you.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: GC752X Switch Login Failure
I have upgraded the switch to v1.0.5.35 and we have not had any issues with the switch for 4 days now. The Integration Team has been running scenarios all weekend long so the switch has been behaving perfectly. I will let you know if I still have issues but I believe this has been corrected.
Thank you.