Problem binding to port 139 - SMB

This is a discussion on Problem binding to port 139 - SMB ; I'm playing with tunneling SMB via SSH. Both end points are Win2K PCs running CYGWIN SSH. I have uninstalled MS File and Print Sharing on the client system, as directed by a number of Web sites which explain this process. ...

+ Reply to Thread
Results 1 to 3 of 3

Thread: Problem binding to port 139

  1. Problem binding to port 139

    I'm playing with tunneling SMB via SSH. Both end points are Win2K
    PCs running CYGWIN SSH. I have uninstalled MS File and Print Sharing on the
    client system, as directed by a number of Web sites which explain this
    process. For example...

    http://www.csuglab.cornell.edu/Info/ssh-smb.html

    I can now successfully connect to the server machine and map drive letters to
    it. My SSH command looks something like this:

    ssh -L139:w2ksrv:139 w2ksrv.fqdn

    (w2ksrv is defined in the client system's LMHOSTS file to point to 127.0.0.1.)
    I also use SSH to connect to w2ksrv to tunnel a number of other protocols.
    This command includes the -g switch, which provides for connectivity via
    the remote (client) system for other remote systems on the same network
    as the client. For some reason, even though File and Print Sharing isn't
    running, there's still something listening on port 139 on the client. This
    is preventing me from integrating the forwarding of port 139 with the
    command I'm using to tunnel the other protocols. Does anyone know what might
    be listening on port 139 on the client system and if it's possible to
    disable it?

    Thanks,
    Mike
    --
    Michael T. Davis | Systems Specialist: ChE,MSE
    E-mail: davism@er6.eng.ohio-state.edu | Departmental Networking/Computing
    -or- DAVISM+@osu.edu | The Ohio State University
    http://www.er6.eng.ohio-state.edu/~davism/ | 197 Watts, (614) 292-6928

  2. Re: Problem binding to port 139

    Windows Name Services. It's part of the Workstation or Server service and
    cannot be disabled without serious impact to the rest of the system.

    Mike Ober.

    "Michael T. Davis" wrote in message
    news:buh7e6$gd5$1@charm.magnus.acs.ohio-state.edu...
    > I'm playing with tunneling SMB via SSH. Both end points are Win2K
    > PCs running CYGWIN SSH. I have uninstalled MS File and Print Sharing on

    the
    > client system, as directed by a number of Web sites which explain this
    > process. For example...
    >
    > http://www.csuglab.cornell.edu/Info/ssh-smb.html
    >
    > I can now successfully connect to the server machine and map drive letters

    to
    > it. My SSH command looks something like this:
    >
    > ssh -L139:w2ksrv:139 w2ksrv.fqdn
    >
    > (w2ksrv is defined in the client system's LMHOSTS file to point to

    127.0.0.1.)
    > I also use SSH to connect to w2ksrv to tunnel a number of other protocols.
    > This command includes the -g switch, which provides for connectivity via
    > the remote (client) system for other remote systems on the same network
    > as the client. For some reason, even though File and Print Sharing isn't
    > running, there's still something listening on port 139 on the client.

    This
    > is preventing me from integrating the forwarding of port 139 with the
    > command I'm using to tunnel the other protocols. Does anyone know what

    might
    > be listening on port 139 on the client system and if it's possible to
    > disable it?
    >
    > Thanks,
    > Mike
    > --
    > Michael T. Davis | Systems Specialist:

    ChE,MSE
    > E-mail: davism@er6.eng.ohio-state.edu | Departmental

    Networking/Computing
    > -or- DAVISM+@osu.edu | The Ohio State University
    > http://www.er6.eng.ohio-state.edu/~davism/ | 197 Watts, (614) 292-6928




  3. Re: Problem binding to port 139

    In article ,
    Michael T. Davis wrote:
    > I'm playing with tunneling SMB via SSH. Both end points are Win2K


    Is this the goal or a means to an end? IOW, there might be better ways
    to make this filesharing happen. I'd use OpenVPN clients on both ends.
    You don't even need cygwin that way, IIUC. Lots of other possibilities.

    > it. My SSH command looks something like this:
    >
    > ssh -L139:w2ksrv:139 w2ksrv.fqdn
    >
    > (w2ksrv is defined in the client system's LMHOSTS file to point to 127.0.0.1.)


    Does Cygwin use LMHOSTS for TCP/IP name resolution? I wouldn't think it
    should.

    > command I'm using to tunnel the other protocols. Does anyone know what might
    > be listening on port 139 on the client system and if it's possible to
    > disable it?


    Is there a Windows equivalent of netstat? Or does the one with cygwin
    also show the Windows processes?
    --
    /dev/rob0 - preferred_email=i$((28*28+28))@softhome.net
    or put "not-spam" or "/dev/rob0" in Subject header to reply

+ Reply to Thread