Create alternate port for 445 traffic?

[RRinTetons]

We have a server on a web hosting site on which I need to map a share. I've used standard Windows mapping (either net use of just Map a Network Drive) in the past, but I just moved to a new place and the ISP that serves it blocks traffic on port 445, the standard port, and is not interested in assisting me to work around the problem. I have admin access on the server at the web hosting site and here on my machine.

It seems like I should be able to listen on an alternate port on the server I want to connect to, and connect to it from an alternate port from my own machine using private port up in the unregistered upper reaches. Before I start hacking away at it I wanted to ask if: a) it's actually a reasonable way to address the problem, and, b) if there are any pointers on doing it or addressing the issue some other way?

Windows Server 2003 on the server end, Windows Vista Business on the client end.

-
Richard Ray
Jackson Hole Mountain Resort

 

[North323]

you want to map a drive from your home to this server? why not set up a vpn and not worry what the ISP is blocking. I doubt they would open it...the conficker worm listens on that port.

 

[RRinTetons]

Yeah, I didn't expect the ISP to open 445. I hadn't thought of a software vpn from me to the hosting service, I use a Cisco vpn concentrator at work and my brain just went in that direction as far as vpn is concerned. I've never worked with software-based vpn's, any pointers or hints?

-
Richard Ray
Jackson Hole Mountain Resort

 

[North323]

you can download the cisco vpn client and create a user group on your concentrator. import the pcf file and your 'in'

 

[RRinTetons]

Wrong network. The web server I'm trying to access is at a hosting farm, not on our company LAN where the concentrator is. I've got the Cisco VPN client on my machine and I use it to connect to the company LAN. I tried connecting to the company LAN via the Cisco vpn and then trying to connect to the share. Naturally enough, the traffic headed for the web server isn't going to an address on our LAN, so it still gets sent over the connection directly to the ISP that's blocking 445. I can't find a way to tell the Cisco client to send all 445 traffic to the company LAN for routing.

I am now looking at just setting up a Windows Server 2003 VPN as described in

http://articles.techrepublic.com.co/5100-10878_11-5805260.html

For only a couple of connections that might do the job.

-
Richard Ray
Jackson Hole Mountain Resort

 

[North323]

that would work... point to point vpn

 

[burtsbees]

the traffic headed for the web server isn't going to an address on our LAN, so it still gets sent over the connection directly to the ISP that's blocking 445. I can't find a way to tell the Cisco client to send all 445 traffic to the company LAN for routing."

Either it is not NATted correctly (static NAT, or "port-forward"), or VPN pool is not excluded from NAT (if this is an IPSEC tunnel).

/

 

[compuveg]

Most hosted servers have FTP access. Open the URL to that, ftp://whatever and you can pull-down the 'Page' button/menu in the top-right, to the 'Open FTP site in Windows Explorer'. When you do that, you have to login again, but can drag and drop files in and out of the site. You don't get a drive letter, but it feels like one.