WinXP client can't connect to Linux shares - SMB

This is a discussion on WinXP client can't connect to Linux shares - SMB ; When I try to connect to my Linux shares from my WinXP client, I get the message "Network path not found", however when I'm at the linuxbox I can see and access the files shared on the WinXP machine without ...

+ Reply to Thread
Results 1 to 2 of 2

Thread: WinXP client can't connect to Linux shares

  1. WinXP client can't connect to Linux shares

    When I try to connect to my Linux shares from my WinXP client, I get
    the message "Network path not found", however when I'm at the linuxbox
    I can see and access the files shared on the WinXP machine without
    even having to authenticate via username/password (which I don't like
    by the way- very big security problem).....

    When I'm at the Linuxbox and use the following command:
    smbclient //Rennyslaptop/SharedDocs/My Pictures/ -U Renny -W
    collarland

    I get the following output:
    added interface ip=192.168.1.2 bcast=192.168.1.255 nmask=255.255.255.0
    added interface ip=192.168.1.3 bcast=192.168.1.255 nmask=255.255.255.0
    added interface ip=192.168.1.4 bcast=192.168.1.255 nmask=255.255.255.0
    added interface ip=192.168.1.5 bcast=192.168.1.255 nmask=255.255.255.0
    Got a positive name query response from 192.168.1.9 ( 192.168.1.9 )
    Domain=[COLLARLAND] OS=[Windows 5.1] Server=[Windows 2000 LAN Manager]
    tree connect failed: NT_STATUS_BAD_NETWORK_NAME

    What does this mean?

  2. Re: WinXP client can't connect to Linux shares

    Ferindo Middleton, Jr wrote:

    > When I try to connect to my Linux shares from my WinXP client, I get
    > the message "Network path not found", however when I'm at the linuxbox
    > I can see and access the files shared on the WinXP machine without
    > even having to authenticate via username/password (which I don't like
    > by the way- very big security problem).....
    >
    > When I'm at the Linuxbox and use the following command:
    > smbclient //Rennyslaptop/SharedDocs/My Pictures/ -U Renny -W
    > collarland
    >
    > I get the following output:
    > added interface ip=192.168.1.2 bcast=192.168.1.255 nmask=255.255.255.0
    > added interface ip=192.168.1.3 bcast=192.168.1.255 nmask=255.255.255.0
    > added interface ip=192.168.1.4 bcast=192.168.1.255 nmask=255.255.255.0
    > added interface ip=192.168.1.5 bcast=192.168.1.255 nmask=255.255.255.0
    > Got a positive name query response from 192.168.1.9 ( 192.168.1.9 )
    > Domain=[COLLARLAND] OS=[Windows 5.1] Server=[Windows 2000 LAN Manager]
    > tree connect failed: NT_STATUS_BAD_NETWORK_NAME
    >
    > What does this mean?


    Maybe this will help:
    see if collarland is in the /etc/hosts file as
    192.168.1.9 collerland


+ Reply to Thread