topic Re: Samba PC client network path error in Operating System - HP-UX

Samba PC client network path error

Robert Milne — Thu, 16 May 2002 06:33:15 GMT

Hello all, hope someone can help...

We run Samba v2.0.6 on HP-UX 11i over our NT network to just share some output batch user files of our ERP system to all users. All users can gain access as public for read-only access to the files. This used to work fine until recently...

Now some users PC's cannot gain access, when accessing the share the message "\\share is not accessible, the network path was not found results." appears on their PC. This appears to be by users machine, rather than logon ID, as the same user can access the share from other PC's OK. No changes were made to Samba on the HP-UX machine. All other NT shares from other Wintel servers appear OK. This was has us really stumped, but then we aren't really Samba experts either, and we don't know what we have done to make this change !

Some important output (edited for brevity !) from testparm re the config of Samba in smb.conf

[global]
workgroup = KRONENT
netbios name = KRONE
server string = MFG/PRO Batch Files
bind interfaces only = No
security = SHARE
encrypt passwords = No
update encrypted = No
allow trusted domains = Yes
guest account = smbnull
hosts allow =
hosts deny =

[mfgpro]
path = /home/mfgbatch
read only = Yes
guest ok = Yes

Any help or clues appreciated.
Regards,
Rob.

PS I hope I have the right forum for this !

Re: Samba PC client network path error

U.SivaKumar_2 — Thu, 16 May 2002 07:06:39 GMT

hi,
From the not working client
C:>\nbtstat -a "server_ip"
please paste the output.
Is the client in any NT domain ?. Can you
FIND COMPUTER the server from this client ?.

regards,
U.SivaKumar

Re: Samba PC client network path error

David Burgess — Thu, 16 May 2002 07:29:55 GMT

Hi,

Check the pc client is in the same domain as the others. Then check the pc's can all see each other in network neighborhood.

Try starting the samba web admin and see if there is an option to allow / disallow certain clients.

In the web browser goto servername:901 and login as root.

HTH,

Dave.

Re: Samba PC client network path error

T G Manikandan — Thu, 16 May 2002 09:02:17 GMT

Looks to me like a netbios issue.

just try giving a ping from that specific system to the hp server
or
do a
net use * \\hp-server-share

Now enter your hpux server name in your hosts file on the windows machine and try connecting to it.

hosts file located at C:\winnt\system32\drivers\etc\hosts

Thanks

Re: Samba PC client network path error

Keith Lautenschlager — Mon, 20 May 2002 12:38:26 GMT

Robert,

If you are still having the problem after
checking all the netbios name resolution
suggestions you may want to make sure the
new clients are configured to send
unencrypted passwords. In your smb.conf
file you have encrypt passwords = no. This
means you will need to change a parameter
in the client's s/w to allow it to send
over a cleartext password.

Re: Samba PC client network path error

kish_1 — Tue, 21 May 2002 02:21:20 GMT

since this was working before can you just try in pc run command \\sambaservername\sharename.
before connecting please make sure disconnect any mapped drive with samba server.

Re: Samba PC client network path error

Christian Briddon — Wed, 22 May 2002 08:41:33 GMT

Just a thought, does the machine you are having problems with have an entry in the smbpasswd file?

Re: Samba PC client network path error

Steve Lewis — Wed, 22 May 2002 09:13:24 GMT

Since I just got Samba going on our network, let me give some tips on what held me back on some of our PCs.
Is it just new PCs that have this issue? Maybe they have some new policy that disables WINS addressing or LMHOSTS.
Go into Control panel, Networks, TCP/IP, Properties, WINS and ensure that LMHOSTS look-up is enabled.
If the PC has no LMHOSTS file (in NT it is in the same place as hosts+services ie \winnt\system32\drivers\etc)
try creating a file called lmhosts with the IPaddresshostname of the server and see if the client can connect.
The above applies where you are using NT domain authentication and are not using the smbpasswd file.