Re: Como Resetear Una Gateway Laptop
Hedy Madrid
how is it possible to reset a Codesys 2.3 gateway password ?
A machine is controlled by a Codesys PLC and in part by a PC. Codesys 2.3 is installed on the PC.
From time to time I connect via TeamViewer to that PC, to download a modified project to the PLC. However a support engineer that recently left the company seems to have set a password for the gateway on the PC, and now a connection to the PLC from that particular PC is no longer possible - because no one knows the password. How to reset the password?
As the PLC itself is not protected, it's easy to resolve the problem - just connect from another PC. That's what we do now.
However it only sounds easy but is practically very inconvenient because the guys there have to bring a laptop to the machine, I have to inform them in advance, the laptop owner can't use it while I'm online etc. etc.
Is there a way to force the refresh of the portal agent config on connected clients? We have multiple portals and multiple gateways for VPN load distribution and fail-over capabilities. When developing/testing changes to the GP VPN I will often take a gateway out of rotation by deleting it from the portal external gateway config. The following day, when clients authenticate to the portal, they get the updated portal config and stop using the gateway to be used for testing (default 24 hour portal app config refresh timeout, custom 18 hour gateway timeout).
However, we have a small number of clients that for some reason will go multiple days to a week without authenticating against/refreshing their portal config (instead using a cached copy). This is even though they are actively authenticating to the gateway every morning/disconnecting every night. Does anyone know why this is happening or how to force the client to refresh its portal config?
I don't have official statement, but I am completely sure that portal refresh timer is reset on every gateway login. I could be wrong, but based on my personal observation I believe the following is happening:
- Upon next connection GP will try to connect straight to the last known good gateways and used the cased config. If the connection to the gateways fail only then it will connect to GP portal and get the latest config
- However in some cases the user disconnect the gateway before the portal refresh timer run out. On the next connect it will again use the cased config and since the gateway is till alive it will connect straight to the gateway, skipping the portal. On this connect it will start the clock again, but if the user reconnects again before it run out, it will never connect to the portal.
My only solution and suggestion is to use shorter portal config refresh timer. We previously used 4hours, which still causing several users to skipping portal refresh for months. I am only guessing that user connect in the morning, around the 3rd hour went to lunch or just go to a meeting putting his laptop to sleep. After lunch he connects but again little before the 4th hour he disconnect and go home.
One way is to tell the user to open the GP agent GUI --> go to setting -> Refresh connection. This will force the client to reach out to the portal authenticate and get fresh pair of config and gateway list, and of course run the gateway selection again and connect to gateway. Refreshing connection from GUI is sure way to refresh client portal config instantly, unfortunately it requires the user to do it manually. I am not aware (and I am almost certain it does not exist) of a way to do it remotely or via command prompt.
@aleksandar.astardzhiev Yes, that has been my experience, kicking users from the portal did not result in the GP client refreshing the portal config, just reconnected to the same gateway. Looking at my own config, with a 24 hour portal refresh timer and 7 day gateway timeout, It has been nearly 48 hours without refreshing the portal config:
I thought I'd replied with a further quert but can't see it listed so will try to rpeat what I typed before.We found the default gateway / IP address for the BT Home Hub (192.168.1.254) but after enetering in Step B6 we had an error, "illegal IP address from 192.168.0.234". This is different from the IP address above.
What is the static IP Address you have set for the GS724TPS switch? Since you found out that the default gateway / LAN IP address of the BT Home Hub is 192.168.1.254, then the static IP Address you should set for the GS724TPS switch should be 192.168.1.x (where x can be any number from 1 to 253).
4. After 30 seconds, release the paper clip from the factory reset button. Check if the GS724TPS switch will boot up properly. The Power LED should lit up solid green. The FAN LED should be off which indicates that it operates normally.
3. Open a browser like Google Chrome or Firefox then at the address bar of it, type 192.168.0.239 then press Enter. Login to the web-GUI of switch. Enter "admin" and "password" as the username and password respectively without the quotation marks.
6. Enter a static IP address that is within the IP range of your existing network in the field provided (for example: if the LAN IP address of your BT broadband router is 10.0.0.1 then you can set a static IP address of 10.0.0.9 on the GS724TPS switch). Also, enter the corresponding subnet mask and default gateway then click Apply. Take note that the default gateway is the LAN IP address of your BT broadband router.
9. Open a browser like Google Chrome. Then, at the address bar of it, type the static IP Address you have set to the GS724TPS then press Enter. If you are able to access it, then it means that the GS724TPS is now a part of your existing network and you can now connect devices such as PCs, network printer to any LAN port.
Note: You may also perform a connectivity test. Open command prompt on your PC/laptop then ping the static IP address you have set to the GS724TPS. If you receive replies then it means that the GS724TPS is reachable within your existing network.
Possibly, your subnet mask is 255.255.255.0 and your default gateway is the LAN IP Address of your router. To know the default gateway, connect a Windows PC directly to your router then open command prompt then type ipconfig and press Enter. As reference, kindly access the links below on how to find the subnet mask and default gateway:
All this may seem straightforward to those in the know but to the unitiated it's daunting. Without my daughter's intervention I would not have been able to do this on my own. It didn't help that the PC and router are on the ground floor and the switch is in an attic two floors up. Nor did it help that the old laptop we'd identified to connect to the switch wouldn't connect. Even after we got started in earnest, we had many failed attempts eg getting to step B6 then realising we didn't have the default gateway so had to take the PC back to the router on the ground floor (switch is in second floor attic). Each time we failed we had to start from scratch again at step A1 otherwise we couldn't proceed.
I've looked through older posts and my story is pretty similar. I was just using my laptop last night. I closed the laptop. This morning, when I tried to turn it on, it wouldn't turn on. The power button wouldn't even light up. I noticed that that the laptop feels pretty cold - so I think it's the battery.
So I unplugged the laptop, plugged it into another outlet. And nothing happened. Finally, I unplugged the laptop, removed the battery, put it back in, plugged the laptop in and turnned it on again and the charging light light up purple. It was only purple for a couple of moments and turnned blue.
The second I press the power button on, the charging light will go out completely and I have to go through the above process to get the charging light turnned on again. If I just unplug and replug, the light charging light won't turn on again.
Information:
Your computer or monitor has no power at all or cannot boot properly. In some situations this can be caused by an external device or an electrical problem. This can usually be solved by removing all external devices and resetting the power supply.
1. Disconnect all external devices you have, including the keyboard and the mouse.
2. Unplug the power cord.
3. Press the power button and hold it for at least 15 seconds.
4. Reconnect the power cord. If your computer is a desktop, please make sure the wall socket you are using is grounded.
Do not yet reconnect the external devices, they should stay disconnected.
5. Switch on your computer and test if it boots normally.
1. Disconnect all external devices you have.
2. Unplug the power adapter from the notebook.
3. Remove the battery from the notebook (if possible).
4. Press the power button and hold it for at least 15 seconds.
5. Reconnect the power adapter.
Do not yet reconnect the external devices, they should stay disconnected. Do not yet reseat the battery.
6. Switch your computer on and test if it boots normally and watch if the power LED lights up.
7. If the power LED still does not lights up, continue with the next steps.
8. Disconnect the power adapter from the notebook.
9. Press the power button and hold it for at least 15 seconds.
10. Reseat the battery. Do not reconnect the power adapter.
11. Switch your computer on and test if it boots normally.