![]() ![]() Then all you need to do is start your session in the LogMeIn webpage – either using a browser extension or a Java web-based client - and you'll have immediate access to the remote computer. The client should be installed and launched in the computers you want to access remotely. So i dont know where i need to search anymore So i think that there is something wrong in the TCP ip V4 on this PC but the internet is working on the problematic pc without any problems and this is also using tcp/ip v4 When connecting using the PC name it is using tcp/ip V6 i think because when i disable on the problematic pc the TCP/IP v6 the remote desktop is not working anymore when trying to connect with the PC name.Įnable TCP ip v6 and remote desktop is working again if using the pc name. RDP is working without any problem when i try it from a normal working pc in the network when using the PC name when i use the ip adres instead it is not working. My idea is that there is something wrong with TCP / IP v4. WARNING: Ping to 192.168.0.160 failed with status: TimedOut Using IP adres of problematic PC instead of Pc name PS C:\Users\Vero> test-netconnection daan-win10 -port 3384 ![]() Test-NetConnection -ComputerName -CommonTCPPort RDPįrom normal working Win 10 Pc to problematic Pc. The commands 1-4 already done many times no solution So i cannot do some things that is important so i dont lose the TeamViewer connection. I need to solve it in the evening when the client is not working on his pc so i have to do this remotely by using TeamViewer. I have the idea that there is something corrupt in the TCP/IP v4 … So i dont know where i need to look anymore. No change.Īlready removed the 3th party Anti Virus completly. When pinging from another pc to the ip adres of the problem pc there is also no reaction.Īlready removed the LAN adapter from devices and let it detect again. Using a program to list the pc's on the network this pc is not listed. Same issue when i connect to the new ip adres no reaction. So the RDP is working but it seems something network related is wrong on this Pc.Īlready set the ip wich is fixed to automatic so the Firewall is providing a ip adress. The problematic pc has no issues to access other shared folders on other Windows pc's and no problem to access the Internet, Emails.įrom another pc i have tried to connect to the problemetic Pc with RDP by entering the internal ip adres in this case 192.168.0.5 no reaction but when i try the same with the Pc name instead of the ip adres the RDP is working. When other users search for network devices the Windows Pc with the problem is not listed. Since the pc is not responding to the RDP i have checked everything and it seems to be correct configured.įor test i created a shared folder this folder is also not visible for other users. The client is using Remote Desktop to take over his pc what has Always worked fine. I have a issue on a Windows 10 pro 64 bit 20H2 (client did update to latest version because he had this problem already before the update so it is not related to 20H2)
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |