G
Guest
Hi,
This company used to only run a linux server with samaba file sharing
serving windows. All was fine for years.
This weekend a Windows 2K Server was added and the clients are now
connecting to a mapped network drive on the server (The Win 2K server has SP4
installed).
Most of the XP clients logon simply when they logon to their client system
and have instant access to the shared network drive, the XP Home systems
access the sever using the servers workgroup service.
There are 2 similar age Acer AMD Athelon laptops (Aspire 13** generation)
that do not automatically logon the the shared network drives at system
stratup/logon and the users have to enter logon details a second time to get
acess to the shares.
I suspect that this is to do with the locally stored user profiles or it
might be hat a registry change was made on these systems to improve file
acess to the linux samba shares
([HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Netlogon\Parameters]
"requiresignorseal"=dword:00000000)
I have installed SP2 on one of the troublesome systems, but this has not
solved the problem.
As I am working at a very basic admin knowledge level I am need some patient
help here to figure this problem out.
Thanks in advance:
Fred.
This company used to only run a linux server with samaba file sharing
serving windows. All was fine for years.
This weekend a Windows 2K Server was added and the clients are now
connecting to a mapped network drive on the server (The Win 2K server has SP4
installed).
Most of the XP clients logon simply when they logon to their client system
and have instant access to the shared network drive, the XP Home systems
access the sever using the servers workgroup service.
There are 2 similar age Acer AMD Athelon laptops (Aspire 13** generation)
that do not automatically logon the the shared network drives at system
stratup/logon and the users have to enter logon details a second time to get
acess to the shares.
I suspect that this is to do with the locally stored user profiles or it
might be hat a registry change was made on these systems to improve file
acess to the linux samba shares
([HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Netlogon\Parameters]
"requiresignorseal"=dword:00000000)
I have installed SP2 on one of the troublesome systems, but this has not
solved the problem.
As I am working at a very basic admin knowledge level I am need some patient
help here to figure this problem out.
Thanks in advance:
Fred.