IP address keeps switching back to wrong address

Thanks for your suggestion. Although the router (an ADB Broadband Centro Grande provided by the telephone company) does have a base station connected to it through ethernet in bridge mode, this did not appear to be the problem as I disconnected it and the problem continued.

The problem occurring with both WiFi and Ethernet on my niece's computer, and despite finding nothing in the router's logs to indicate a problem, I then connected my own MBP that has never had an issue to the router using ethernet only to have the same IP problem appear. In consequence, I rebooted the router and the problem appears to have disappeared and everything is working ok again.

I am at a loss as to understand how or why this problem occurred in the first place, though I must note that the router ground to almost a halt yesterday evening and required rebooting.

All the best.

Alan

I'll follow your advice and have fun ⚠ over the next few days or so. I've had issues with the router before and it was changed this winter. Not impressed with these telecom routers and I'd bypass them completely if I could. Unfortunately, they are pretty limited in what one can tweak.

Best,

Alan

Thanks for your feedback, Bob, but you are wrong. The server address is 192.168.1.1. Having run a cybercafé (which had 3 separate networks that I set up myself) since 1998 and having set up a home network prior to that, one thing I do know is how to set up a LAN. Besides, the default setting for the router/DHCP server is 192.168.1.1. There is nothing else on the network that is serving out addresses as the base station is a slave in bridge mode. The network has worked fine for the last couple of years or so unchanged and this issue appeared suddenly out of the blue yesterday. To connect to the server, I have to use the address 192.168.1.1. 192.168.0.1 gets me nowhere. It goes without saying that one of the first things I did was to check both routers' settings.

Also, had 192.168.0.1 been the correct server address, then I would assume that I would have been able to connect to the Internet, which was not the case. It would not explain how all the other machines having a 192.168.1.xx address connected to the Internet normally if the gateway was 192.168.0.1.

Furthermore, what is equally odd, is that the router's logs have no reference to handing out a DHCP 192.168.0.xx address unlike when it issues a 192.168.1.xx address, even when this happened with the slave disconnected and the router isolated.

However, since rebooting the router, the problem appears to have disappeared and everything has gone back to normal. The whole thing is a total mystery and it's the first time that I have seen something like this.

Best regards,

Alan