WIN NT 4.0 NO GO & YES I HAVE ENCRYPTED PASSWORDS

[Joseph]

Try increasing the debug level a little and see if you get anything 
useful in the log files.

Gerry Maddock wrote:

> I thought it might have been some of the "optimizations" I added to
> /etc/sysctl.conf,so I reverted back to the orinal sysctl.conf with no
> optimizations straight off the RH7.1 install, rebooted and still nothing.
> However, once I lost the "optimizations" I did notice a log.shadow, which
> Shadow is one of the NT boxes I'm trying to connect from, but the log.shadow
> was empty. Currently, I'm still running the default sysctl.conf from the
> RH7.1 install (with no added "optimizations" just to rule this out....
> 
> -----Original Message-----
> From: samba-ntdom-admin at lists.samba.org
> [mailto:samba-ntdom-admin at lists.samba.org]On Behalf Of Bruno Gimenes
> Pereti
> Sent: Thursday, October 11, 2001 1:04 PM
> To: samba-ntdom at lists.samba.org
> Subject: Re: WIN NT 4.0 NO GO & YES I HAVE ENCRYPTED PASSWORDS
> 
> 
> I got a problem this week that may be related to your problem. I'd blocked
> icmp to the PDC (RedHat 7.1 Samba 2.2.1a rpm). No problem to access the
> server but when I tried to join the domain with a W2k I couldn't. I allowed
> the icmp traffic and still couldn't join. When I restarted the smb daemon I
> could join the domain as before.
> 
> Maybe this can help you.
> 
> Bruno Gimenes Pereti.
> 
> ----- Original Message -----
> From: "Chris" <cknorton.nei-inc.com at mail.nei-inc.com>
> To: "Gerry Maddock" <gerrym at futuremetals.com>
> Cc: "William L. Terry" <bill at lynden2.sweye.com>;
> <samba-ntdom at lists.samba.org>
> Sent: Thursday, October 11, 2001 1:30 PM
> Subject: Re: WIN NT 4.0 NO GO & YES I HAVE ENCRYPTED PASSWORDS
> 
> 
> 
>>I also, had this problem running RedHat 7.1 with samba -2.0.10-2.  I
>>would get the "\\SambaShare is not accessible" from my NT, W2K, and
>>WinMe machines but I  rebooted my samba server and then all of a sudden
>>I could access the samba share.
>>
>>Maybe this will give someone a clue as to what might be the problem.
>>
>>
>>Gerry Maddock wrote:
>>
>>
>>>Thanks! I'm glad I'm not the only one! If I hear anything or somehow rig
>>>
> it
> 
>>>to work, I'll let you know what I did. Please do the same for me.
>>>
>>>-----Original Message-----
>>>From: samba-ntdom-admin at lists.samba.org
>>>[mailto:samba-ntdom-admin at lists.samba.org]On Behalf Of William L. Terry
>>>Sent: Thursday, October 11, 2001 11:47 AM
>>>To: samba-ntdom at lists.samba.org
>>>Subject: Re: WIN NT 4.0 NO GO & YES I HAVE ENCRYPTED PASSWORDS
>>>
>>>
>>>Gerry Maddock wrote
>>>
>>>
>>>>I am in the process of upgrading my existing samba 2.05a PDC on an
>>>>old box running RH6.2 to a new faster box running Samba 2.2.1a on a
>>>>RH7.1 box. I have all the same files and directories as the old samba
>>>>box including the same smb.conf file (the only thing changed in the
>>>>smb.conf were changes to its PDC so I wouldn't have 2 PDC's on the same
>>>>subnet). All of my Nt 4.0 boxes are sp6 with all of the latest security
>>>>patches. Whenever I try to connect to the new Samba box from my NT box I
>>>>get:>
>>>>
>>>>\\Penguin is not accessible.
>>>>
>>>>The remote procedure call failed and did not execute.
>>>>
>>>>
>>>
>>>I also have this problem with redhat 7.1 and samba 2.2.1a .  It is to the
>>>outside world as if this machine does not exist.   I have 16 samba boxes
>>>out there around the state serving up domains for our locations.  I have
>>>used everything from samba-tng2.5 to samba2.2.0 with success. The last
>>>
> good
> 
>>>combination I got was 2.2.0 with a redhat 7.0 box.  I also use a 2.0.7 as
>>>
> a
> 
>>>non domain controller on a redhat 7.1 box successfully.  I have tried
>>>
> with
> 
>>>two
>>>separate installs to use 2.2.1a with redhat7.1.   I also suspected the
>>>firewall
>>>rules, but I intentionally blew these away with no positive results.  The
>>>only
>>>indication I get that the samba domain exists is that when I give the
>>>
> domain
> 
>>>a
>>>name, the client sees that that domain exists, but can't see any machines
>>>
> in
> 
>>>it.
>>>You can also do "nmblookup -B ACLIENT '* '" successfully.
>>>
>>>I am also stumped, but I will continue to slog along and see If I can
>>>stumble
>>>across something.
>>>
>>>--
>>>William L. Terry             (bill at sweye.com)
>>>Southwestern Eye Center       http://www.sweye.com/
>>>Information Systems
>>>480-892-8400 ext. 142
>>>
> 
>