SAMBA: Server does not permit remote access

SAMBA: Server does not permit remote access

Post by Kurt Harpe » Sat, 04 Mar 2000 04:00:00



I have now checked encryption; I have made sure I have a file called
lmhosts.  I have made sure I have a passwd and smbpasswd file.  I have set
security to USER.  I have tried WINS resolution enabled.

But I still can't access my Linux machine from my Win95/98 machines; I still
can't ping the Win machines from Linux by name, but can by IP address; and
when, in Windows, I right click my Linux server and check Properties, I get
the message "Server (name) does not accept remote access"  (or maybe the
word is "permit" instead of "accept").

What have I missed here?

 
 
 

SAMBA: Server does not permit remote access

Post by Dan William » Sat, 04 Mar 2000 04:00:00


It sounds like you do not have name resolution set up correctly.  The first
thing I would do is edit your /etc/hosts file and put in names for your
systems.  For instance if you had machine bob and machine mary your
/etc/hosts would look like:

192.168.0.1  bob
192.168.0.2  mary

Of course you will need to change the ip addresses for your environment.
After trying that verify that you can ping your systems by:

ping bob
ping mary

If that works then you have name resolution set up.  For control purposes I
usually specify the workgroup AND the netbios name in the /etc/smb.conf
file.

workgroup = SAMBA
netbios name = BOB

Also, make sure you have 'host' in the line name resolve order line:

name resolve order = wins lmhosts bcast host

Make sure you have encryption set up right.  If you followed the
instructions that tell you how to make the smbpasswd file:

cat /etc/passwd | mksmbpasswd.sh > /etc/smbpasswd

You still need to run the command smbpasswd to set the user's password.  So
if your linux username is 'joe' and password 'schmoe' then you need to run

smbpasswd joe

And enter schmoe when it asks.  Assuming all other parameters are set
correctly this should get you up and going.  If you still you have problems
I recommend that you read the documents in:

/usr/doc/samba-2.0XXX/docs/textdocs

This is better than any information you can get on the net.

Hope this helps

 
 
 

SAMBA: Server does not permit remote access

Post by Kurt Harpe » Sun, 05 Mar 2000 04:00:00


Thanks.  That's the closest I've gotten to a step by step approach identifying
the problem.

> It sounds like you do not have name resolution set up correctly.  The first
> thing I would do is edit your /etc/hosts file and put in names for your
> systems.  For instance if you had machine bob and machine mary your
> /etc/hosts would look like:

> 192.168.0.1  bob
> 192.168.0.2  mary

> Of course you will need to change the ip addresses for your environment.
> After trying that verify that you can ping your systems by:

> ping bob
> ping mary

> If that works then you have name resolution set up.  For control purposes I
> usually specify the workgroup AND the netbios name in the /etc/smb.conf
> file.

> workgroup = SAMBA
> netbios name = BOB

> Also, make sure you have 'host' in the line name resolve order line:

> name resolve order = wins lmhosts bcast host

> Make sure you have encryption set up right.  If you followed the
> instructions that tell you how to make the smbpasswd file:

> cat /etc/passwd | mksmbpasswd.sh > /etc/smbpasswd

> You still need to run the command smbpasswd to set the user's password.  So
> if your linux username is 'joe' and password 'schmoe' then you need to run

> smbpasswd joe

> And enter schmoe when it asks.  Assuming all other parameters are set
> correctly this should get you up and going.  If you still you have problems
> I recommend that you read the documents in:

> /usr/doc/samba-2.0XXX/docs/textdocs

> This is better than any information you can get on the net.

> Hope this helps

 
 
 

SAMBA: Server does not permit remote access

Post by Kurt Harpe » Sun, 05 Mar 2000 04:00:00


This is an extra thank you for your reply.  You provided exactly the
information I needed; the system now works (although I ended up using
lmhosts instead of /etc/host for resolution).  It works even without using
WINS resolution.

I supplemented your information with an EXCELLENT book which I commend to
anyone dealing with SAMBA:  Samba, Integrating UNIX and Windows, by John D.
Blair.

 
 
 

1. remote access to a samba server

I would like to install a Linux/Samba server to provide file and print
sharing for 25 win95/98 clients.  The Linux box would also need to
provide IP Masquerading for the clients.  I think I can figure that
stuff out.  But what I can't figure out is: How could a remote win95/98
client, once on the internet thru their ISP dial up connection, mount
the Samba share? Also, would a pentium 266 w/ 64MB of ram be enough
machine for these tasks.  Thanks for any suggestions.

Andy

2. MASQ errors in dmesg output

3. make remote lan access on file server SAMBA

4. BOOK REVIEW: Multiplatform Code Management

5. remote access to samba server...

6. using an enhanced audio cd in RH5?

7. Able to ping from server to remote but not from remote to server

8. calculation of (bsd accounting) ac_mem incorrect?

9. DOS FAT partitions: operation not permitted

10. rpc.mountd: getfh failed: Operation not permitted ( WinNT -> samba -> Linux -> NFS -> Solaris)

11. Kernel upgrade -> no network access (ping: sendmsg: Operation not permitted)

12. Samba : cannot access Samba server via NT Domain.

13. Dialup access to Netware through OpenLinux remote access server