Operating System - HP-UX
1832018 Members
2970 Online
110034 Solutions
New Discussion

Samba 3 - W2K network path was not found

 
Garry Kibler
Occasional Advisor

Samba 3 - W2K network path was not found

Ok, I'm having trouble getting connections from my W2K pc's to my Samba server running under HP/UX 11.0. (All new install of Samba) I'm on an isolated network; no server, just simple W2K Pro systems. All my pc's are part of the workgroup intranet, and are sharing files amongst themselves. The same accounts and passwords exist on the pc's and the hpux system. Here's the details:

Hp/UX 11.0 / Samba 3.0.0 / Misc hpux patches.
Samba daemons smbd and nmbd start fine. No errors. Here's the testparm:

./testparm
Load smb config files from /usr/local/samba/lib/smb.conf
Processing section "[homes]"
Processing section "[public]"
Loaded services file OK.
Server role: ROLE_STANDALONE
Press enter to see a dump of your service definitions

# Global parameters
[global]
workgroup = INTRANET
null passwords = Yes
smb passwd file = /etc/samba/smbpasswd

[homes]
comment = Home Directories
read only = No
create mask = 0750

[public]
path = /data
read only = No
guest ok = Yes

The findsmb shows that it sees my W2K pc's (deepthot is the hpux box):
./findsmb

IP ADDR NETBIOS NAME WORKGROUP/OS/VERSION
---------------------------------------------------------------------
192.168.1.50 DEEPTHOT +[ INTRANET ]
192.168.1.100 dlk
192.168.1.102 dell
192.168.1.135 gakcpq

I also have ran these commands:

exportfs -i /data

/usr/local/samba/bin/smbpasswd -a garry -n (done for each account)

The W2K pc's are all at SP4, and running a nbtstat command produces the message "Host not found", but sometimes, (no consistency), it produces:

C:\>nbtstat -a deepthot

Local Area Connection:
Node IpAddress: [192.168.1.135] Scope Id: []

NetBIOS Remote Machine Name Table

Name Type Status
---------------------------------------------
DEEPTHOT <00> UNIQUE Registered
DEEPTHOT <20> UNIQUE Registered
DEEPTHOT <03> UNIQUE Registered
DEEPTHOT <20> UNIQUE Registered
..__MSBROWSE__.<01> GROUP Registered
INTRANET <1D> UNIQUE Registered
INTRANET <1E> GROUP Registered
INTRANET <00> GROUP Registered
INTRANET <1E> GROUP Registered

MAC Address = 00-00-00-00-00-00


But anytime I try to make a connection from any pc to the hpux host by doing a start/run \\deepthot or \\192.168.1.50 I get the message "The Network Path Was Not Found". I'm open for any suggestions or things I need to try!

garry

Don't panic
3 REPLIES 3
Steven E. Protter
Exalted Contributor

Re: Samba 3 - W2K network path was not found

I was wondering if anyone was using Samba 3.0

I would first check the samba log files while this is happening. On the HP side tail -f logfilename

I noticed the Mac Address is all zeros. That can not be right. It could be teh cause of some problems.

The shares are all right on the Windows and HP side? What about the user id's. Are the ID's that need to share the same on both environments?

Just wondering if CIFS/9000 Samba 2.2.3 is an option for you. I know thats solid, using it on five boxes.

SEP
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
Garry Kibler
Occasional Advisor

Re: Samba 3 - W2K network path was not found

Cleared the log files, and tried some commands. This is the only thing that's appeared in smbd.log (nothing in the nmdb.log):

cat ../var/log.smbd
[2003/11/17 22:30:57, 0] lib/util_sec.c:assert_gid(113)
Failed to set gid privileges to (-1,-2) now set to (0,0) uid=(0,0)
[2003/11/17 22:30:57, 0] lib/util.c:smb_panic(1400)
PANIC: failed to set gid

I've added the host/ip addr to my hosts files on Windows, so they can all ping it by name, and the accounts on hpux & windows match; id's and passwords.

I agree that the MAC address isn't correct, but I don't understand why?

I had tried Samba 2.2.3a, and had similar results, so I tried the 3.0. I'm obviously missing something somewhere, and probably something simple, but I haven't talked about it enough to get the light to come on...

Thanks...
Don't panic
Darren Prior
Honored Contributor

Re: Samba 3 - W2K network path was not found

Hi Garry,

I'd suggest that you turn up the logging a little and ensure that you have a separate log for each client that connects. The following
2 lines should be added to your smb.conf:

log file = /var/opt/samba/log.%m
log level = 2

I believe the default log level is 0; which won't tell you much more than the daemons starting and people connecting so 2 is a reasonable level to start troubleshooting.

regards,

Darren.
Calm down. It's only ones and zeros...