samba - Jun 2009 - Changing samba PDC version but keeping the same IP address

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello

We are facing a bit boring problem

We are on the way to upgrade our PDC from 2.2.8 to 3.2.11
as we do not want to reconfigure the PDC IP address on several
hundreds of windows XP clients we have chosen to keep the same
IP address for the new PDC.

The problem is windows clients does not update the name of network
drives and keep the old names even connected to the new PDC server
and it's new shares ...

I suspect there are some caching mechanisms that are not completely
cleaned (!!!) by windows.


Any infos on "how to clean widows caches" are welcome.

Thanks

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.11 (FreeBSD)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkoneusACgkQ6f7UMO5oSsVzqwCgj5NxAHLneeNybWmif7msv1sn
wZ0AoJ0FTmj8fAon0lq7/rL16yNPtdp8
=7H8F
-----END PGP SIGNATURE-----

Frank Bonnet schrieb:
> We are on the way to upgrade our PDC from 2.2.8 to 3.2.11
> as we do not want to reconfigure the PDC IP address on several
> hundreds of windows XP clients we have chosen to keep the same
> IP address for the new PDC.
Why you use IPs on the client instead of names? Here we resolve everything by 
Wins/DNS. So no need for using IPs.


> The problem is windows clients does not update the name of network
> drives and keep the old names even connected to the new PDC server
> and it's new shares ...
You mean the name of the server or from the shares?
If you keep the IP you can also name the new server as the old one (what I 
would suggest). And if the shares also keep their names, nothing changes out 
of client sight.

How are the shares connected? If you use a logon script, you can change this.
Just disconnect all old shares before you map it. And if the shares are mapped 
with "/PERSISTENT:NO", they are automatically disconnected after
logoff.

And don't forget to set the domain SID of the new server to the one of your 
old server. Otherwise your clients doesn't accept the new server as PDC for 
the domain, even if the domain name is the same.


Regards,
Marc



-- 
Marc Muehlfeld (Leitung IT)
Zentrum fuer Humangenetik und Laboratoriumsmedizin Dr. Klein und Dr. Rost
Lochhamer Str. 29 - D-82152 Martinsried
Telefon: +49(0)89/895578-0 - Fax: +49(0)89/895578-780
http://www.medizinische-genetik.de

Frank Bonnet wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Hello
> 
> We are facing a bit boring problem
> 
> We are on the way to upgrade our PDC from 2.2.8 to 3.2.11
> as we do not want to reconfigure the PDC IP address on several
> hundreds of windows XP clients we have chosen to keep the same
> IP address for the new PDC.
> 
> The problem is windows clients does not update the name of network
> drives and keep the old names even connected to the new PDC server
> and it's new shares ...
> 
> I suspect there are some caching mechanisms that are not completely
> cleaned (!!!) by windows.
> 
> 
> Any infos on "how to clean widows caches" are welcome.
> 
If I understand you correctly, you mean everything is working just fine, 
but the server name displayed in file explorer for the network drive 
letter is still the old server name.


If that's it, check the registry:

[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\ComputerDescriptions]

Delete the entries for the server & it will automatically refresh to the 
current setting.


-- 
tkb