This appears to be a well documented glitch in the BT firmware and you can read about to your heart's content on the web. I connect to the router with my main home mac by Ethernet and have yet to try connecting with wifi in the hope that it is only an Ethernet connection that is dropped and not the wifi. Having spent the best part of what seems a lifetime talking to BT customer technical help and getting nowhere I have given up at the moment. I have configured Teamviewer 11 to WOL in my local network but am failing for remote because whenever I try to access my BT home hub 5 port forwarding setting, the router immediately drops the connection. The only time I have to reset the Com port is when I update SGP to a new version I think this is because of the serial/usb adapter not 'remembering' the port. I have had to upgrade to a Win 10 pc last week and do not have a problem with my Lakeside and Com ports. Let me know if you have problems, I have to delete the COM1 entry in ASCOM profile, change it to COM5 and set it to COM5 in Lakeside utility and try connect quickly, if it fails, turn it off and on and try it all again.Īccording to Peter at Lakeside there shouldn't be any problems That will mean that I will have to enter the new Broadband Network IP address of the hub in TeamViewer on the obsy PC every time it is restarted. The only issue that I foresee is that the BT Home Hub Broadband Network IP will probably change when the hub is restarted as I think that address is allocated dynamically. In the Advanced Settings/Firewall/Port Forwarding section on the BT Home Hub, I have coupled TeamViewer with my Obsy PC using UDP Port 9. I have assigned a static IP address to my Obsy PC in the Advanced Settings/Home Network section.Ģ. The other settings required to get this to work, as far as I can make out, were on the BT Home Hub as follows:ġ. I put this into TeamViewer on the Obsy PC and it was accepted straight away and it now works. Instead, I checked the details on my BT Home Hub (my home router) and found its 'Broadband Network IP'. I was trying to put in the IP address of the Obsy PC itself. The thing that I was getting wrong was the IP address that I was trying to enter into the Public Address field in TeamViewer. But I don't know how to confirm that.I just managed to configure TeamViewer to Wake-On-Lan my Obsy PC through the Public Address option and, even better, I managed to actually start up the obsy PC while using an internet connection through my phone, so not on my home network. Since the PC wakes up just fine when it's on my own LAN, i dont think it's an issue with my PC, it seems more likely it's something to do with their network. I'm not really sure what else it could be at this point. I emailed them to see if there was some sort of DOS protection that might have been blocking multiple packets, they say there isnt any DOS protection. I dont think thats the issue since the IP address hasnt even changed in the last few days, and certainly hasnt changed in the last few minutes between each wake request. As soon as i switch the ethernet cable back to their router, it stops working. I can put it to sleep/hibernate and it wakes up every time. It DOES work if i plug my pc directly into my own router and send the wake request over my own LAN. Other than those two times, it hasn't worked. and then earlier today my PC was on for several hours, and i put it to sleep just to test the WoL and it worked. Once when the PC was off all night and i was able to get to power back on (from hibernate). So far, i've been able to wake my PC twice using this. I had them setup UDP ports 7 and 9 for Wake on Lan. I have one set up for rdp which is working. But they are willing to set up port forwards for me. I have to use the fiber router they provided and don't have access to it's admin interface. My apartment building recently switched to an new internet provider.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |