locked
ISP blocking ports 135-139 & 445. Workaround??? RRS feed

  • Question

  • I'm a server newbie, so thank you in advance for speaking plainly.

    We recently upgraded from DSL to Uverse and are now unable to map our network drive to our server (Windows 2008 R2).  Apparently Uverse is unwilling to unblock ports 135-139 & 445 (why they don't block them in their DSL service??? IDK).  We can RDC to the server, but it is not ideal.

    I have scoured the forums for a workaround, but nothing specifically speaks to my issue.

    Is there a Windows based solution?  Here are the following suggestions I have gleaned, but I don't want to start installing things and messing around with my server if they aren't going to solve my problem.  I'm not sure how they work, so any more info would be great:

    Microsoft loopback adapter

    FTPUSE

    LogMeIn

    Tunnelier

    Will any of these allow me to map the drive on ports other than 135-139 & 445?  Or are they no better than RDC?

    All our clients are running Win7 and map the drive perfectly thru any other ISP.

    Thanks for your help.

    Sunday, January 22, 2012 5:14 PM

Answers

  • Hi mopsmom1,

     

    Thanks for posting here.

     

    A possible workaround but never tested so not sure if will work.

    Consider to have another host that obtained valid internet address that provided by another ISP that has not such restriction policy and configure it as a port/interface proxy server by using the netsh Interface Portproxy feature on Windows:

     

    Netsh commands for Interface Portproxy

    http://technet.microsoft.com/en-us/library/cc731068(WS.10).aspx

     

    Thanks.

     

    Tiger Li


    Tiger Li

    TechNet Community Support

    Monday, January 23, 2012 7:51 AM
  • Hi,

    i hope, i understand right, your clients are connected directly to the internet. You can configure your server as a ras server and using sstp. Look at http://technet.microsoft.com/en-us/library/cc731352(WS.10).aspx.

    I know, it needs time and effort, but you need only to open port 443 and all traffic is encrypted. Your users can acces the networkdrive as known.

    Regards,

    M.Hivner

    Monday, January 23, 2012 9:16 AM

All replies

  • Hi mopsmom1,

     

    Thanks for posting here.

     

    A possible workaround but never tested so not sure if will work.

    Consider to have another host that obtained valid internet address that provided by another ISP that has not such restriction policy and configure it as a port/interface proxy server by using the netsh Interface Portproxy feature on Windows:

     

    Netsh commands for Interface Portproxy

    http://technet.microsoft.com/en-us/library/cc731068(WS.10).aspx

     

    Thanks.

     

    Tiger Li


    Tiger Li

    TechNet Community Support

    Monday, January 23, 2012 7:51 AM
  • Hi,

    i hope, i understand right, your clients are connected directly to the internet. You can configure your server as a ras server and using sstp. Look at http://technet.microsoft.com/en-us/library/cc731352(WS.10).aspx.

    I know, it needs time and effort, but you need only to open port 443 and all traffic is encrypted. Your users can acces the networkdrive as known.

    Regards,

    M.Hivner

    Monday, January 23, 2012 9:16 AM