TRACEROUTE ISSUES WORKING FROM HOME PLEASE HELP!!
I recently started working remote from home. I have to connect to my companies remote server on my pc at home. I work most of my day talking on the phone through the remote server with clients. I am having issues where my voice on the phone is choppy and clients cannot hear me. I contacted my tech team at work and they ran at tracert test and said one of my hops is timing out. they said to contact my ISP which is COX to fix this but no one at COX seems to be able to know how to fix this issue when I call. I even had a tech come out to look at it. does anyone know how to fix this issue? please help! this is how the traceroute is coming back as. as you can line 6 and 7 are timing out. C:\Users\AmeriSave>tracert remote8.amerisave.com Tracing route to remote8.amerisave.com [70.42.180.69] over a maximum of 30 hops: 1 1 ms 1 ms 1 ms 192.168.0.1 2 9 ms 8 ms 7 ms 10.35.48.1 3 12 ms 15 ms 13 ms 100.127.73.138 4 10 ms 11 ms 15 ms 100.120.100.10 5 25 ms 27 ms 19 ms 68.1.4.252 6 * * * Request timed out. 7 * * * Request timed out. 8 109 ms 87 ms 86 ms ae12.cs2.dfw2.us.zip.zayo.com [64.125.26.182] 9 81 ms 89 ms 83 ms ae5.cs2.iah1.us.eth.zayo.com [64.125.28.102] 10 * 82 ms * ae28.cs1.atl10.us.zip.zayo.com [64.125.31.171] 11 81 ms 85 ms 80 ms ae6.mpr3.atl6.us.zip.zayo.com [64.125.31.33] 12 82 ms 80 ms 94 ms 128.177.70.66.IPYX-072053-009-ZYO.zip.zayo.com [128.177.70.66] 13 73 ms 65 ms 65 ms border2.ae2-bbnet2.acs.pnap.net [64.94.0.93] 14 67 ms 65 ms 70 ms edge2.ae1-edgenet.acs002.pnap.net [107.150.129.34] 15 65 ms 71 ms 68 ms amerisave-5.edge2.acs002.pnap.net [70.42.176.126] 16 66 ms 77 ms 65 ms 70.42.180.69 Trace complete.1.7KViews0likes5CommentsRemote Desktop Connection stopped working
I am running Windows 7 Home Premium. I have a Remote Desktop Connection to my work computer (which is still in XP) which I have used successfully for years. It has now stopped working, and giving me an error message of "Remote Desktop cannot find the computer ........." I did a search for this problem, and found MANY others with the same problem. Multiple fixes were offered -- some easy, some very complicated. I performed all the suggestions that I felt comfortable with -- none worked. Among these -- I bypassed Windows Firewall; I bypassed my AVP (which is AVG). I removed "printers" from the RDC connection. I enabled Remote Desktop in "Services." I was not comfortable trying anything that would change the registry, or anything that was just too complicated for my scant amount of computer knowledge. I called Cox Support -- they "sent some changes to my router" and re-set it, but that did nothing. They told me they didn't know how to fix it, and that I would have to resort to paid support. My boss is reluctant to pay for such support because he is retiring, and I understand his position. Our tekkie was able to connect to my work computer from his home, so I know the problem lies with my computer. His hunch is that the problem lies with my ISP because he has seen this problem many times. Having this Remote Desktop Connection fail is hugely inconvenient and extremely annoying for me. Anyone have any ideas?4.5KViews0likes3CommentsSlow Incoming Connection
I have a great connection, and speedtest.net shows a very good ping (70ms or so) and great upload/download speed. But recently, over the last 2 weeks, I am no longer able to use Windows Remote Desktop or use similar services like TeamViewer. When I try, I can connect but it is incredibly slow. How slow? If I'm patient enough to see my login screen (about 60-90 seconds after I connect), typing my password takes another 60-90 seconds before it registers that I typed anything. I don't now what's going on. My router settings haven't changed (for example, the Remote Desktop port 3389 is still forwarded to my computer's correct IP address). I've tried for multiple locations (from a few miles away on another Cox connection, or from my office building where we have very high bandwidth, or even from my cell phone's hotspot and other locations like coffee shops). Any ideas what has made my incoming connections slow to a crawl?2.3KViews0likes1Comment