ISP blocking ports 135-139 & 445. Workaround???


i'm server newbie, thank in advance speaking plainly.

we upgraded dsl uverse , unable map our network drive our server (windows 2008 r2).  apparently uverse unwilling unblock ports 135-139 & 445 (why don't block them in dsl service??? idk).  can rdc server, not ideal.

i have scoured forums workaround, nothing speaks issue.

is there windows based solution?  here following suggestions have gleaned, don't want start installing things , messing around server if aren't going solve problem.  i'm not sure how work, more info great:

microsoft loopback adapter

ftpuse

logmein

tunnelier

will of these allow me map drive on ports other 135-139 & 445?  or no better rdc?

all our clients running win7 , map drive thru other isp.

thanks help.

hi mopsmom1,

 

thanks posting here.

 

a possible workaround never tested not sure if work.

consider have host obtained valid internet address provided isp has not such restriction policy , configure port/interface proxy server using netsh interface portproxy feature on windows:

 

netsh commands interface portproxy

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

 

thanks.

 

tiger li


tiger li

technet community support



Windows Server  >  Network Access Protection



Comments

Popular posts from this blog

some help on Event 540

WMI Repository 4GB limit - Win 2003 Ent Question

Event ID 1302 (error 1307) DFS replication service encountered an error while writing to the debug log file