
Mailing List Archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[tlug] smbclient/smbprint problems to w2k box
- Date: Mon, 20 Jan 2003 17:35:02 +0700
- From: "Jonathan Q" <jq@example.com>
- Subject: [tlug] smbclient/smbprint problems to w2k box
I've been googling and reading for days and am kind of a loss here.  My Samba
server that I just set up seems to be working fine, the people in my office
have mapped network drives to their home directories and everything is great. 
It's another story with smblclient.
I can get a share listing from my Samba host:
[jq@example.com jonathan]$ smbclient -L LUDENS -U jonathan
added interface ip=192.168.0.108 bcast=192.168.0.255 nmask=255.255.255.0
Password: 
Domain=[WORKGROUP] OS=[Unix] Server=[Samba 2.2.7]
	Sharename      Type      Comment
	---------      ----      -------
	SASAKIH        Disk      
	stomilson      Disk      
	yen            Disk      
	IPC$           IPC       IPC Service (LUDENS)
	ADMIN$         Disk      IPC Service (LUDENS)
	Server               Comment
	---------            -------
	LUDENS               LUDENS
	SASAKI               
	Workgroup            Master
	---------            -------
	WORKGROUP            SASAKI
But if I try to actually log in using smbclient I get this:
[jq@example.com jonathan]$ smbclient  //LUDENS/jonathan  -I 192.168.0.108
-U jonathan
added interface ip=192.168.0.108 bcast=192.168.0.255 nmask=255.255.255.0
Password: 
Domain=[WORKGROUP] OS=[Unix] Server=[Samba 2.2.7]
tree connect failed: NT_STATUS_BAD_NETWORK_NAME
Here's another look, connecting to an actual W2K Pro box on which I have an
account:
[jq@example.com jonathan]$ smbclient  //YEN/jonathan -I 192.168.0.7 -U
jonathan
added interface ip=192.168.0.108 bcast=192.168.0.255 nmask=255.255.255.0
Password: 
Domain=[WORKGROUP] OS=[Windows 5.0] Server=[Windows 2000 LAN Manager]
tree connect failed: NT_STATUS_BAD_NETWORK_NAME
My /etc/samba/lmhosts contains:
127.0.0.1 localhost
192.168.0.7 YEN
192.168.0.108 LUDENS
192.168.0.11 SASAKI
Our workgroup name is a very generic WORKGROUP.
I'm at wit's end here.  Anybody got a wit or two they can spare ? :-P
TIA,
Jonathan
Home |
Main Index |
Thread Index