Forum Home
Press F1
Thread ID: 100892	2009-06-24 10:47:00	Changing LAN IP - Thompson TG585V7	Geek4414 (12000)	Press F1

Post ID	Timestamp	Content	User
785483	2009-06-25 12:07:00	Home Network -> Interfaces -> Local Network -> Configure Wish it was that simple, tried every clickable option and menu I can find, no such luck. Don't understand your problem. My LAN address is the default 192.168.1.254 but I can click edit and change it. Let's face it, it HAS to be changeable. I know how to configure adsl modem/routers, have done zillions of them, this is the only one I have come acrossed that has no option to configure the LAN IP. I am not sure if your Thompson is the Telecom issued one? This one has no editible LAN IP option for the router itself, you can only change the IP for the other connected device. Common sense would dictate that it has to be changable but I have read from a few places that the LAN IP setting is in fact not accessible in this router from the GUI, only when you telnet into the CLI. But accurate May not relate to your modem but..... If its one of those Telecom modems, dont waste your time (honestly) The cheaper one evidently has a secret Telecom login/pass they that wont give out as well as the user login/no-pass. The secret login may give more config options. evidently it uses 2 ip subnets, 2nd one is for the secret login. This info was from a telecom Tech, he said they wont give out that 2nd secret login/pass to anyone. That doesn't sound very promising. >_< In that case, does anyone have any advice on how to get around the VPN & RDP problem if I can't change the LAN IP of this modem/router?? I have successfully connected to the destination PC via VPN & RDP, so long as I am doing it from a router with a different IP segment (i.e. 10.1.1.x), but not able to connect from any router with the IP segment of (192.168.x.x) because it 'appears' to clash with the destination LAN segment. I suspect that is because the destination IP segment being the same as the local one, the RDP session would not try to reach over the VPN to find the destination PC but instead trying to find it within the local LAN? Is this correct? If not, does anyone have any explanations?? Or better still, a solution??	Geek4414 (12000)
785484	2009-06-25 22:02:00	Wish it was that simple, tried every clickable option and menu I can find, no such luck. I suspect that is because the destination IP segment being the same as the local one, the RDP session would not try to reach over the VPN to find the destination PC but instead trying to find it within the local LAN? Is this correct? If not, does anyone have any explanations?? Or better still, a solution?? Then it is an issue related to the login you are using not having the rights to change it, as I have changed the LAN IP of this exact model router with the method above. As for the VPN problem - you need to have two different IP ranges.	inphinity (7274)
1 2