We eventually figured it out ... it was a registry setting having to do
with preventing loopbacks on server 2003, by halting calls to the same
server with a different name. Disabled that, and everything was fine.
Re: GUID DNS name could not be resolved ... I modified the registry setting in my server.... You can create a registry script to run on the Win2k clients,... can be done in a group policy, which is noted in the article I posted. ... (microsoft.public.win2000.dns)
Re: Moving WSS2.0 to Another Server ... you really meant \\netbios name there is a Registry setting that will ... > I need to move my Windows SharePoint Services from one ... > decided that the name of the link needs to be changed ... > are already running Windows 2003 Server.... (microsoft.public.sharepoint.windowsservices)
Re: Problem setting the "Valid To" for EFS certificates ... I have set the PeriodUnits from the default of 2. ... does not make sense to me why the registry setting would be 2 but default ... credential roaming will work is that the server will request the private key ...Basic EFS template and created a new template. ... (microsoft.public.windows.server.security)
Re: EFS error msg copying a file locally ... It's going to a server that doesn't ... > There is a registry hack that turns ... > Without this hack, I can't run my backup script. ... > Does anyone have this registry setting?... (microsoft.public.windowsxp.security_admin)
Re: WinXP hordes os/2 server connections ... Is there any registry setting for XP that ... convinces it to actually release connections when a file closes? ... Wasn't this fixed in a service pack at one point? ... it's taken out the server within a few ... (comp.os.os2.networking.misc)
