[Samba] problem with samba server

[Jennifer Fountain]

that file looks pretty strange to me...
I don't think you should use 1.1.1.1 since that IP space does not
pertain to your company (i doubt it anyway) and it is not in the private
IP space.
-1.1.1.1 isn't the real Ip for the wins. (security reason i had to change

Why are you using update encrypted=yes?
that is really only for transitioning to encrypted passwords.
- this option is set by default and recommened for allow for logon

> 	interfaces = lan4 127.0.0.1
this looks unusual to me - what os is this?
this is an hp unix box - has 4 interfaces. in order for this machine to
always use the correct interface we had to use this option

what do you see in the logs when a 95/98 client tries to log on?
check logs now.


-----Original Message-----
From: Bradley W. Langhorst [mailto:brad at langhorst.com]
Sent: Tuesday, October 08, 2002 11:21 AM
To: Jennifer Fountain
Cc: 'samba at samba.org'
Subject: Re: [Samba] problem with samba server


On Tue, 2002-10-08 at 10:33, Jennifer Fountain wrote:
> here is my config file - 
> 
> # Samba config file created using SWAT
> # from ws09573.rb.net (10.27.52.177)
> # Date: 2002/10/08 10:25:55
> 
> # Global parameters
> [global]
> 	client code page = 437
> 	workgroup = domain1
> 	netbios name = server1
> 	server string = ares
> 	interfaces = lan4 127.0.0.1
> 	bind interfaces only = Yes
> 	security = DOMAIN
> 	encrypt passwords = Yes
> 	update encrypted = Yes
> 	allow trusted domains = No
> 	password server = server2
> 	admin log = Yes
> 	log level = 4
> 	name resolve order = wins lmhosts bcast host
> 	character set = ISO8859-1
> 	os level = 0
> 	local master = No
> 	domain master = False
> 	wins server = 1.1.1.1
> 	socket address = 
> 	guest account = smbnull
> 
> 
that file looks pretty strange to me...
I don't think you should use 1.1.1.1 since that IP space does not
pertain to your company (i doubt it anyway) and it is not in the private
IP space.

Why are you using update encrypted=yes?
that is really only for transitioning to encrypted passwords.

> 	interfaces = lan4 127.0.0.1
this looks unusual to me - what os is this?

what do you see in the logs when a 95/98 client tries to log on?

brad