Cable Forum - View Single Post

General Maximus · 09-02-2016, 17:44

Follow Kosh's wise words, they have solved many an issue such as this in the past. Just to clear up a few bits for you though because you are getting confused; modems do not assign ip addresses, routers and dhcp servers do. If your shub was in router mode then you would get a 192.... address but not in modem mode. If your laptop was directly connected to the shub in modem mode it would either get a wan ip from VM or it won't. So that would look like 82....... or 169.254......(which is what Windows assigns itself when it can't get a proper address).
If the shub is in modem mode and you are using a 3rd party router and connecting your devices to the router then you would expect the router to have the VM wan ip (which you would be able to see in the gui) and any attached devices to have a local ip issued by the router like 192.168......

If you haven't got yourself confused and knew all that then the problem you might have had, and would partially explain your connectivity issues, is if you are swapping cables and configurations around without rebooting anything like Kosh has intimated then things aren't going to work properly. You have probably had your laptop connected to your 3rd party router and let it get a local address, realised internet wasn't working, put the shub in modem mode and then connected the laptop to the shub. If that is the case then the laptop hasn't got a new ip address. The shub would need to be rebooted anyway and you would need to do an ipconfig /release /renew on the laptop to get it to look for a new ip address.

Come back and let us know if it works.

09-02-2016, 17:44	#3
General Maximus cf.mega poster Join Date: Nov 2008 Location: Lincoln Services: phone + 1gbit BB + SkyQ Posts: 11,021	Re: No WAN IP Follow Kosh's wise words, they have solved many an issue such as this in the past. Just to clear up a few bits for you though because you are getting confused; modems do not assign ip addresses, routers and dhcp servers do. If your shub was in router mode then you would get a 192.... address but not in modem mode. If your laptop was directly connected to the shub in modem mode it would either get a wan ip from VM or it won't. So that would look like 82....... or 169.254......(which is what Windows assigns itself when it can't get a proper address). If the shub is in modem mode and you are using a 3rd party router and connecting your devices to the router then you would expect the router to have the VM wan ip (which you would be able to see in the gui) and any attached devices to have a local ip issued by the router like 192.168...... If you haven't got yourself confused and knew all that then the problem you might have had, and would partially explain your connectivity issues, is if you are swapping cables and configurations around without rebooting anything like Kosh has intimated then things aren't going to work properly. You have probably had your laptop connected to your 3rd party router and let it get a local address, realised internet wasn't working, put the shub in modem mode and then connected the laptop to the shub. If that is the case then the laptop hasn't got a new ip address. The shub would need to be rebooted anyway and you would need to do an ipconfig /release /renew on the laptop to get it to look for a new ip address. Come back and let us know if it works.