joao alberto m. dos reis
2004-Jun-30 13:02 UTC
[Samba] changing password with a windows client
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I have a SAMBA (samba 3.0.0) with PDC configuration where users are stored with smbpasswd in /etc/samba/smbpasswd. When I change a user password from a windows client, I get a error that the domain can't be reached, but the password actualy changes. How can I fix this problem? How can I make windows show that the password was succefuly changed? TIA, Joao Reis. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQFA4rnncfDZuH0KEiERAt3JAJ4pdaCyT9RjA8j7ewc1Za8/JX9oSwCfX6n3 kDOAJc0iUnI/Hs+OxVRf64Q=rLho -----END PGP SIGNATURE-----
On Wed, 2004-06-30 at 23:02, joao alberto m. dos reis wrote:> -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Hi, > > I have a SAMBA (samba 3.0.0) with PDC configuration where users are stored > with smbpasswd in /etc/samba/smbpasswd. > > When I change a user password from a windows client, I get a error that > the domain can't be reached, but the password actualy changes. > > How can I fix this problem? How can I make windows show that the password > was succefuly changed?Upgrade to Samba 3.0.4, where we fixed Samba bugs that MS became stricter on in the implementation of MS04-11/KB828741 Andrew Bartlett -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part Url : http://lists.samba.org/archive/samba/attachments/20040630/45fdd971/attachment.bin
I'm having a hard time figuring this one out. I've done this before
when I had a PDC on one end of the VPN, and a BDC on the other. This is
what my setup looks like now.
Clients(XP)
|
PDC(192.168.0.4), windows 2000
|
|
WINS Server Samba(192.168.0.1), also the gateway for this network
|
|
Internet
|
|
WINS Server Samba(192.168.2.1), also the gateway for this network
|
|
Clients(XP)
With this setup I'm not sure how I'm suppose to setup each wins server.
Do I need to have one on each subnet, and then have them both remote
announce and remote browse sync to each other? Or maybe some like
that? When I'm using remote announce, should it be 192.168.0.1 or
192.168.0.0 or 192.168.0.255? Same with remote browse sync, does it
need to be the actual address of the other wins server? or do I just
send it to that subnet? Does anyone have a working configuration with
this setup(Domain on one side of the tunnel and just a workgroup on the
other, both are the same workgroup). All the machines can ping each
others ip, so I know its not a tunnel issue. Thanks for your guys help.
Jason
Charles,
The clients behind each gateway, do they point to the local wins
server then? So for the clients on the 192.168.0.0 network, they would
point to 192.168.0.1, where samba is running a wins server and announces
to 192.168.2.255? You have wins server = 192.168.1.50, would I just
have wins
support = yes if its on the same machine? Let me clear up what I'm
trying to say.
Should my network look like this: Option A
Clients on network A(192.168.0.0) have a wins server of 192.168.0.1(the
vpn gateway for them as well as a samba wins server)
192.168.0.1(Samba wins server with these settings, wins support = yes,
remote announce = 192.168.2.255)
192.168.2.1(Samba wins server with these settings, wins support = yes,
remote announce = 192.168.0.255)
Clients on network B(192.168.2.0) have a wins server of 192.168.2.1(the
vpn gateway for them as well as a samba wins server)
Or this: Option B
Clients on network A(192.168.0.0) have a wins server of 192.168.0.1(the
vpn gateway for them as well as a samba wins server)
192.168.0.1(Samba wins server with these settings, wins support = yes,
remote announce = 192.168.2.255)
192.168.2.1(Samba wins server with these settings, wins server =
192.168.0.1, remote announce = 192.168.0.255)
Clients on network B(192.168.2.0) have a wins server of 192.168.2.1(the
vpn gateway for them as well as a samba wins server)
Or this: Option C
Clients on network A(192.168.0.0) have a wins server of 192.168.0.1(the
vpn gateway for them as well as a samba wins server)
192.168.0.1(Samba wins server with these settings, wins support = yes,
remote announce = 192.168.2.255)
192.168.2.1(Samba wins server with these settings, wins server =
192.168.0.1, remote announce = 192.168.0.255)
Clients on network B(192.168.2.0) have a wins server of 192.168.0.1(the
vpn gateway for them as well as a samba wins server)
Thanks for your help
Charles Hamel wrote:
>Hi Jason,
>
>I have a similar setup and all I need to do was to enable ip directed
>broadcast on the router and enter the following settings in smb.conf:
>
>wins server = 192.168.1.50
>remote announce = 192.168.1.255
>
>HTH
>
>Charles
>
>On Wed, 30 Jun 2004 09:23:18 -0400, Jason C. Waters wrote
>
>
>>I'm having a hard time figuring this one out. I've done this
before
>>when I had a PDC on one end of the VPN, and a BDC on the other.
>>This is what my setup looks like now.
>>
>> Clients(XP)
>> |
>>PDC(192.168.0.4), windows 2000
>> |
>> |
>>WINS Server Samba(192.168.0.1), also the gateway for this network
>> |
>> |
>> Internet
>> |
>> |
>>WINS Server Samba(192.168.2.1), also the gateway for this network
>> |
>> |
>> Clients(XP)
>>
>>With this setup I'm not sure how I'm suppose to setup each wins
>>server. Do I need to have one on each subnet, and then have them
>>both remote announce and remote browse sync to each other? Or
>>maybe some like that? When I'm using remote announce, should it be
>>192.168.0.1 or 192.168.0.0 or 192.168.0.255? Same with remote
>>browse sync, does it need to be the actual address of the other wins
>>server? or do I just send it to that subnet? Does anyone have a
>>working configuration with this setup(Domain on one side of the
>>tunnel and just a workgroup on the other, both are the same
>>workgroup). All the machines can ping each others ip, so I know
>>its not a tunnel issue. Thanks for your guys help.
>>
>>Jason
>>
>>--
>>To unsubscribe from this list go to the following URL and read the
>>instructions: http://lists.samba.org/mailman/listinfo/samba
>>
>>
>
>
>--
>Open WebMail Project (http://openwebmail.org)
>
>
>