Advertisement
If you have a new account but are having problems posting or verifying your account, please email us on hello@boards.ie for help. Thanks :)
Hello all! Please ensure that you are posting a new thread or question in the appropriate forum. The Feedback forum is overwhelmed with questions that are having to be moved elsewhere. If you need help to verify your account contact hello@boards.ie

Remote Access/Port Forwarding on Virgin Hub 3.0

Options
  • 22-03-2017 5:03pm
    #1
    ratedR
    Registered Users Posts: 334 ✭✭


    Hi all,

    I see similar questions have been asked here but I couldn't find anything specific to the issue I seem to be having.

    I've got that new router from Virgin and am trying to enable remote access to it.
    I have an IPv4 address not an IPv6, I've got remote access enabled and I've manually set up a port forward to the internal IP address of the machine I want to connect to remotely. I've also made sure no firewall or anti-virus software is interfering.
    I've got the router in router mode as I need it that way for the bunch of wireless connections I've got around the house. I've seen mention of it being in modem mode.

    This setup worked fine with the older modem/router. I'm also aware it's not the safest setup that can be done, but I should still be able to do it.

    Anyone see what my issue might be?

    Thanks.

    Edit* All connections are being refused is the issue, if it wasn't clear! The only thing I'm slightly unclear on is the internal/external port numbers with port forwarding. Say I'm going with good old port 3389, should I set all the fields to 3389? Or should one be set to 80 for http access?
    Tagged:


Comments

  • Options
    #2
    ratedR
    Registered Users Posts: 334 ✭✭ratedR


    Noone has any insight on this??


  • Options
    #3
    28064212
    Registered Users Posts: 10,494 ✭✭✭✭28064212


    First thing to check: is remote access to the machine working from inside the network?

    Boardsie Enhancement Suite - a browser extension to make using Boards on desktop a better experience (includes full-width display, keyboard shortcuts, dark mode, and more). Now available through your browser's extension store.

    Firefox: https://addons.mozilla.org/addon/boardsie-enhancement-suite/

    Chrome/Edge/Opera: https://chromewebstore.google.com/detail/boardsie-enhancement-suit/bbgnmnfagihoohjkofdnofcfmkpdmmce



  • Options
    #4
    ratedR
    Registered Users Posts: 334 ✭✭ratedR


    28064212 wrote: »
    First thing to check: is remote access to the machine working from inside the network?

    Yup, having no issues there, can log in via a laptop or with the iPhone app.


  • Options
    #5
    28064212
    Registered Users Posts: 10,494 ✭✭✭✭28064212


    ratedR wrote: »
    Yup, having no issues there, can log in via a laptop or with the iPhone app.
    And within the network, you're using port 3389? Then in the port-forwarding on the router, you should have internal and external port set to 3389.

    Also, make sure when you're connecting to your external address that you're not currently on your internal network. Virgin doesn't support "loopback" so you can't connect to your own external IP address from within your network

    Boardsie Enhancement Suite - a browser extension to make using Boards on desktop a better experience (includes full-width display, keyboard shortcuts, dark mode, and more). Now available through your browser's extension store.

    Firefox: https://addons.mozilla.org/addon/boardsie-enhancement-suite/

    Chrome/Edge/Opera: https://chromewebstore.google.com/detail/boardsie-enhancement-suit/bbgnmnfagihoohjkofdnofcfmkpdmmce



  • Options
    #6
    ratedR
    Registered Users Posts: 334 ✭✭ratedR


    28064212 wrote: »
    And within the network, you're using port 3389? Then in the port-forwarding on the router, you should have internal and external port set to 3389.

    Also, make sure when you're connecting to your external address that you're not currently on your internal network. Virgin doesn't support "loopback" so you can't connect to your own external IP address from within your network

    Yup, that's exactly what I've done with the port. Using a different network to try to connect - no dice.


  • Advertisement
  • Options
    #7
    ED E
    Registered Users Posts: 36,166 ✭✭✭✭ED E


    Use GRCs shields up to test.


  • Options
    #8
    ratedR
    Registered Users Posts: 334 ✭✭ratedR


    I'm away from the house at the moment so will try it when I get back. You reckon it's a firewall problem most likely so?


  • Options
    #9
    ED E
    Registered Users Posts: 36,166 ✭✭✭✭ED E


    It could be multiple things. A closed port gives the same response as a listener not working.


  • Options
    #10
    [Deleted User]
    Posts: 0 ✭ [Deleted User]


    Why would you open up RDP to the world???


  • Options
    #11
    ratedR
    Registered Users Posts: 334 ✭✭ratedR


    NoDrama wrote: »
    Why would you open up RDP to the world???
    ratedR wrote: »
    I'm also aware it's not the safest setup that can be done, but I should still be able to do it.

    Wicked helpful. Cheers mate :rolleyes:


  • Advertisement
  • Options
    #12
    [Deleted User]
    Posts: 0 ✭ [Deleted User]


    ratedR wrote: »
    Wicked helpful. Cheers mate :rolleyes:
    ratedR wrote: »
    Wicked helpful. Cheers mate :rolleyes:

    I work in IT and the only time I would open RDP to the outside is when it can be locked to a static WAN IP on the firewall.

    You would be mad to open RDP, some script kiddie running a scan and finding it open would just open metasploit and open every attack sector possible, and in the process your network quality would take a hit.

    There is a multitude of reasons for not opening RDP 3389
    https://zeltser.com/remote-desktop-security-risks/

    I would recomened using VPN, reverse SSH and then VPN, RDP, etc, or "Go to my PC"..

    I was and I am trying to help.
    Nothing else...


  • Options
    #13
    ratedR
    Registered Users Posts: 334 ✭✭ratedR


    NoDrama wrote: »
    I work in IT and the only time I would open RDP to the outside is when it can be locked to a static WAN IP on the firewall.

    You would be mad to open RDP, some script kiddie running a scan and finding it open would just open metasploit and open every attack sector possible, and in the process your network quality would take a hit.

    There is a multitude of reasons for not opening RDP 3389
    https://zeltser.com/remote-desktop-security-risks/

    I would recomened using VPN, reverse SSH and then VPN, RDP, etc, or "Go to my PC"..

    I was and I am trying to help.
    Nothing else...

    You were being condescending without offering help or advice.

    I'd already stated that I know it's not the safest way. It isn't a long term solution at all, im trying to configure a network share for plex and have no knowledge of this new virgin router. I want to see if it will work first, and will go down the vpn route after.

    I've got a degree in computer security - I have a good idea of this risks involved.

    Don't bother with a smart reply to that last sentence. This thread can be locked.


  • Options
    #14
    [Deleted User]
    Posts: 0 ✭ [Deleted User]


    It was far from being smart..

    All I can say is that I am sorry..

    /thread


Advertisement