![]() So the really dumbed down version (for people like me!) is to open a command prompt on your desktop, run ipconfig /all, and then it will tell you your internal IP address. So, if anyone else has this problem, what happened was that the new router was assigning IP addresses to my PC's at home in the 192.168.1.x range, which was also the server at work's IP address. I finally got it resolved one of my coworkers suggested checking to make sure that the IP addresses were not in conflict, and they were. If anyone could help I would REALLY appreciate it! I honestly have no ideas at all this is not my area of expertise to say the least. Nothing at work has changed everyone else can log in with no problems, including everyone else with FIOS. There is another location to which I log in using a Cisco VPN and then Remote Desktop - that still works just fine. I tried to connect to the IP address of it (after connecting through the VPN) and then it says it's found but cannot connect. ![]() But when I open the the RDC and try to connect using the PC name it says that the computer cannot be found. The VPN seems to be connecting OK it says it is and it is sending/receiving a small bit of data. Since I switched to FIOS it no longer works on either my laptop with wireless or my desktop which is connected to the router. ![]() The way that I was doing it before was to connect with a regular Microsoft VPN (I have Windows XP Professional), and then I would use Remote Desktop Connection to log into the work PC. I just switched from Comcast to FIOS and I can no longer remote desktop to work - so I'm not getting paid until I can get it fixed. Hi, I really hope someone can please help me.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |