SMB 139 over PuTTY/SSH "network path was not found"

From: Chuck Kuczaj (chuck@erasethis.iamtoast.com)
Date: 09/14/02 

From: Chuck Kuczaj <chuck@erasethis.iamtoast.com>
Date: Fri, 13 Sep 2002 22:26:11 GMT

Hi,

I'm trying to get remote SMB port 139 tunneled through
PuTTY/SSH to a server at work. Both client and server
are Windows 2000 SP2.

Non-PuTTY/SSH session work fine. I simply added

X.X.X.X server.domain.com

to my hosts file, and imported it into my lmhosts,
then tried accessing \\server.domain.com\share.
No problem.

In preparation for the PuTTY/SSH tunnel, I removed
"File and Printer Sharing for Microsoft Networks",
which eliminates the "Server" service, and
added a "dummy" entry of

127.0.0.1 dummybox

to my hosts and imported it, and in my PuTTY session,
added port forwarding of port 139 so that it looks like:

L139 server.domain.com:139

I established the PuTTY/SSH session, and the event log
indicates that the local port 139 is being forwarded.

However, when I try to map

\\dummybox\share

I get a "The network path was not found" error.

I took a look at the windump output and saw the following:

15:08:53.746308 0:1:3:d7:ec:42 > 3:0:0:0:0:1 netbeui ui/C len=44
15:08:53.746341 0:1:3:d7:ec:42 > 3:0:0:0:0:1 netbeui ui/C len=44
15:08:53.747928 IP client.137 > 192.168.0.255.137: udp 50
15:08:53.748105 IP client.137 > 192.168.0.255.137: udp 50
15:08:54.244846 0:1:3:d7:ec:42 > 3:0:0:0:0:1 netbeui ui/C len=44
15:08:54.244888 0:1:3:d7:ec:42 > 3:0:0:0:0:1 netbeui ui/C len=44
15:08:54.495245 IP client.137 > 192.168.0.255.137: udp 50
15:08:54.495449 IP client.137 > 192.168.0.255.137: udp 50
15:08:54.745555 0:1:3:d7:ec:42 > 3:0:0:0:0:1 netbeui ui/C len=44
15:08:54.745589 0:1:3:d7:ec:42 > 3:0:0:0:0:1 netbeui ui/C len=44
15:08:55.246345 IP client.137 > 192.168.0.255.137: udp 50
15:08:55.246546 IP client.137 > 192.168.0.255.137: udp 50

which indicates no traffic going outbound to my server on the
SSH port 22. Why it is still attempting port 137 traffic
remains to be understood.

I have two netbios-ssn entries in my netstat -a output:

TCP client:netbios-ssn client:0 LISTENING
TCP client:netbios-ssn client:0 LISTENING

One comes from the PuTTY/SSH session, the other from my
"Enable NetBIOS over TCP/IP" setting.

At this point, I'm stumped as to why port 139 tunneling
is being stubborn. Thanks in advance for any help.

Chuck

Relevant Pages

  • Re: remote web workplace server admin login problem
    ... You need to forward port 444 too. ... >> Microsoft SBS-MVP ... > I can also use it to connect to the servers console session. ... >>> tried it right after the server install and it worked and it won't ...
    (microsoft.public.windows.server.sbs)
  • Re: SSH connection thru corporate firewall to home sshd on Port 80
    ... > session and perhaps someone can explain this to me. ... > I have a FreeBSD server running sshd listening on port 80 at home. ... > internet to this SSHD:80 server (no firewall involved). ...
    (comp.security.ssh)
  • Can a session cookie be distinguished by IP:port?
    ... I have two browser windows of MSIE open with only one IEXPLORE.EXE ... I point one window at a server on port 8080 and the other at ... invalidating the server session on each. ...
    (microsoft.public.windows.inetexplorer.ie6.browser)
  • Re: How does that tcp traffic work
    ... For each session the server fork() the request and give them a id ... For data arriving at port 80 the server check the process id ... For example, host A is a client, host B is a webserver ...
    (RedHat)
  • Re: SMB 139 over PuTTY/SSH "network path was not found"
    ... > PuTTY/SSH to a server at work. ... > In preparation for the PuTTY/SSH tunnel, ... > added port forwarding of port 139 so that it looks like: ...
    (comp.security.ssh)
Quantcast