logo elektroda
logo elektroda
X
logo elektroda
Advanced Search
logo elektroda

RDP from an external network - Remote desktop access from an external network

czarnk 22383 38
ADVERTISEMENT
Treść została przetłumaczona polish » english Zobacz oryginalną wersję tematu
Reply | New topic
  • #31 14306373
    przeqpiciel
    Network and Internet specialist  
    then if you still have 8080 working, then in the vicinity of the port redirection, try to find the possibility of setting the public 8080 forward to the local 3389
  • ADVERTISEMENT
  • #32 14307788
    czarnk
    Level 10  
    Could you say a little more exactly what you mean? The provider said that now I have all ports redirected to my router address 192.168.23.1. That's why I'm surprised that after port forwarding on my router, I can't access any more.
  • ADVERTISEMENT
  • #33 14308513
    rwisniewski1
    Level 23  
    czarnk wrote:
    Could you say a little more exactly what you mean? The provider said that now I have all ports redirected to my router address 192.168.23.1. This is why I am surprised that after forwarding the ports on my router, I do not deny access.


    But you know 192.168.23.1 is not your router's address, right?
  • ADVERTISEMENT
  • #34 14309887
    hipekk
    Level 19  
    rwisniewski1 wrote:
    czarnk wrote:
    Could you say a little more exactly what you mean? The provider said that now I have all ports redirected to my router address 192.168.23.1. This is why I am surprised that after forwarding the ports on my router, I do not deny access.


    But you know 192.168.23.1 is not your router's address, right?


    How do you know the address of his router?
  • #35 14309891
    przeqpiciel
    Network and Internet specialist  
    hipekk wrote:
    rwisniewski1 wrote:
    czarnk wrote:
    Could you say a little more exactly what you mean? The provider said that now I have all ports redirected to my router address 192.168.23.1. This is why I am surprised that after forwarding the ports on my router, I do not deny access.


    But you know 192.168.23.1 is not your router's address, right?


    How do you know the address of his router?


    just look at the screenshot
    https://www.elektroda.pl/rtvforum/topic2959891.html#14297895
  • #36 14309899
    hipekk
    Level 19  
    Of course you are right, I didn't look at the screen ...
    I return my honor :) .

    In that case, as suggested by the zapicel, you have set up redirection to the wrong IP address (not to your router)
  • ADVERTISEMENT
  • #37 14313294
    czarnk
    Level 10  
    Of course, my mistake. My ports are redirected to the address 192.168.23.132
  • #38 14313404
    jprzedworski
    Network and Internet specialist  
    Maybe try to connect directly, without a router, the computer giving it the address 192.168.23.132
    Then you can be sure if it is really being redirected.
  • #39 14315196
    hipekk
    Level 19  
    Exactly...
    Set the computer address to .132, turn off the Windows firewall and firewall if you have one and test if the redirection is going (turn on the remote desktop, set up the FTP server, install the VNC server, HTTP or something like that) ;) .
    Additionally, you can install a network monitor (e.g. WireShark) to see what is going on.
Reply | New topic
Report a violation of the law

Topic summary

The discussion revolves around the challenges of accessing a computer remotely via Remote Desktop Protocol (RDP) from an external network using a TP-LINK TL-WR740N router. The user has configured port forwarding for port 3389 to the internal IP address 192.168.1.102 but is unable to connect using the external IP. Responses suggest checking firewall settings, ensuring the correct public IP is being used, and verifying if the ISP is providing a public IP or if it is shared among multiple users. Alternatives such as using TeamViewer or purchasing a public IP from the ISP are also discussed. The user later confirms that the ISP has redirected the public IP to the correct internal address but still faces issues with port forwarding. Suggestions include testing direct connections and using network monitoring tools to diagnose the problem.
Summary generated by the language model.
ADVERTISEMENT