Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

So I'm continuing to attempt to set up a Network Drive that will write to a Linux box in the sky.

I made the NTLM change suggested by this question, but I still can't understand a few things to do with the original question.

1) The first is, __what does using \\\ as the network folder mean? If I set up the port 139 forward to tunnel to port 22 on an SSH connection, that means the network drive should "point to the SSH connection", is that right?

2) So assuming that PuTTY maintains the SSH connection, and the Windows Network Drive is mapped to that SSH connection, what can the network drive do with that connection? Are file reads and writes going to be automatically converted to wget or something?

share|improve this question

closed as off topic by Zoredache, Chris S, Iain, RobM, John Gardeniers Apr 15 '11 at 22:35

Questions on Server Fault are expected to relate to server, networking, or related infrastructure administration within the scope defined by the community. Consider editing the question or leaving comments for improvement if you believe the question can be reworded to fit within the scope. Read more about reopening questions here.If this question can be reworded to fit the rules in the help center, please edit the question.

How is this a professional system administration question? – Zoredache Apr 15 '11 at 20:44
Fits in site's tagging system – bobobobo Apr 15 '11 at 21:11
The tags are irrelevant. You seem to be an end-user asking an end-user question which means your question is probably more appropriate for superuser not here. A professional sysadmin would almost certainly know that a) a SMB server is required on the remote end b) that the output of netstat would show that putty was not bound to the port, and c) Windows has almost certainly already bound the SERVER service to the port 139 on the local system and putty is failing to allocate the port, and that \\ actually IS your local computer and is not being forwarded at all. – Zoredache Apr 15 '11 at 21:42
@bobobobo - this is your third question in a row that have been closed due to them being in appropriate for a professional sysadmin site. If you continue to ignore the FAQ your account will be temporarily suspended. – Chopper3 Apr 15 '11 at 22:42
  1. The location \\\ means open the SMB root folder on the local computer. SMB communicates over port 139; Putty is listening on Port 139 on the local computer, it takes that traffic and sends it over it's SSH Tunnel (running on Port 22 by default) to the remote destination of the Tunnel. The remote destination is a Linux server running Samba which communicates via SMB.

  2. The Tunnel doesn't translate anything at all, it's just shipping the data to the remote end. The server at the remote end speaks the same protocol. The Tunnel is just allowing you to connect to a remote network, very similar to a VPN.

share|improve this answer
So how do you make sure Samba "picks up" the connection at the other end, and not the Command Terminal bash? – bobobobo Apr 15 '11 at 21:06
Perhaps its port 139 that does it. Samba must be on port 139. What goes in the login dialog box, my Samba user/pass? It doesn't seem to work. – bobobobo Apr 15 '11 at 21:11
The Tunnel specifies where the connection goes. In the putty configuration, you specify the Source Port (the Localhost [aka] is implied); then you specified the Destination, which should be the name or IP of the remote computer and the Port 139, which is where Samba will be listening for the connection. – Chris S Apr 15 '11 at 21:20

Not the answer you're looking for? Browse other questions tagged or ask your own question.