Sign in with
Sign up | Sign in
Your question

Windows 2003 server & XP Pro Sync issues

Last response: in Windows XP
Share
Anonymous
January 26, 2005 1:09:35 PM

Archived from groups: microsoft.public.windowsxp.basics (More info?)

A couple of days ago we moved from a WIndows 2000 server to a Windows
2003 server and are experiencing connection problems from the
workstations when file synchronization for off line viewing is turned
on on the workstations.

When file sync is on navigating to [only] certain network resources
results in disconnection from the network.

Example:

Navigating to \\Itk-fp\work_groups\environment\biosafety\ on the server
works fine.

Navigating to \\Itk-fp\work_groups\environemnt\Climate Change\ on the
server results in a network disconnect.

At one point yesterday we sat down at a workstation and turned off file
sync, off line folder viewing, deleted all mapped drives and shortcuts
to files on the server, cleared out all the "network places", and
rebooted the machine with the idea in mind that if we "started fresh"
we might solve the problem - the problem persisted as soon as file sync
was turned back on.

The server name & IP on the Win2003 server are identical to the old
Win2000 server, as is the folder & directory structure which we copied
off the old server and on to the new.

Is there a possibilith that somewhere in the registry on the work
stations that some bit of "old" information is creating this problem?
If so, how would we get rid of it?

If we're going down the wrong road completely on this any pointers in a
more productive direction would be most appreciated as we have a number
of positions that travel fairly regularily (to places where even a
stable dial-up connection to the server that would allow use of the VPN
isn't really a viable option) and need access to their files.

Thanks
Anonymous
January 26, 2005 2:48:04 PM

Archived from groups: microsoft.public.windowsxp.basics (More info?)

You should probably take this microsoft.public.windows.server.networking

--
Colin Barnhorst [MVP Windows - Virtual Machine]
"Nia" <mmason@gmail.com> wrote in message
news:uk1eyI9AFHA.3016@tk2msftngp13.phx.gbl...
>A couple of days ago we moved from a WIndows 2000 server to a Windows
> 2003 server and are experiencing connection problems from the
> workstations when file synchronization for off line viewing is turned
> on on the workstations.
>
> When file sync is on navigating to [only] certain network resources
> results in disconnection from the network.
>
> Example:
>
> Navigating to \\Itk-fp\work_groups\environment\biosafety\ on the server
> works fine.
>
> Navigating to \\Itk-fp\work_groups\environemnt\Climate Change\ on the
> server results in a network disconnect.
>
> At one point yesterday we sat down at a workstation and turned off file
> sync, off line folder viewing, deleted all mapped drives and shortcuts
> to files on the server, cleared out all the "network places", and
> rebooted the machine with the idea in mind that if we "started fresh"
> we might solve the problem - the problem persisted as soon as file sync
> was turned back on.
>
> The server name & IP on the Win2003 server are identical to the old
> Win2000 server, as is the folder & directory structure which we copied
> off the old server and on to the new.
>
> Is there a possibilith that somewhere in the registry on the work
> stations that some bit of "old" information is creating this problem?
> If so, how would we get rid of it?
>
> If we're going down the wrong road completely on this any pointers in a
> more productive direction would be most appreciated as we have a number
> of positions that travel fairly regularily (to places where even a
> stable dial-up connection to the server that would allow use of the VPN
> isn't really a viable option) and need access to their files.
>
> Thanks
Anonymous
January 27, 2005 2:59:59 PM

Archived from groups: microsoft.public.windowsxp.basics (More info?)

"Nia" <mmason@gmail.com> wrote in message
news:uk1eyI9AFHA.3016@tk2msftngp13.phx.gbl...
>A couple of days ago we moved from a WIndows 2000 server to a Windows
> 2003 server and are experiencing connection problems from the
> workstations when file synchronization for off line viewing is turned
> on on the workstations.
>
> When file sync is on navigating to [only] certain network resources
> results in disconnection from the network.
>
> Example:
>
> Navigating to \\Itk-fp\work_groups\environment\biosafety\ on the server
> works fine.
>
> Navigating to \\Itk-fp\work_groups\environemnt\Climate Change\ on the
> server results in a network disconnect.
>
> At one point yesterday we sat down at a workstation and turned off file
> sync, off line folder viewing, deleted all mapped drives and shortcuts
> to files on the server, cleared out all the "network places", and
> rebooted the machine with the idea in mind that if we "started fresh"
> we might solve the problem - the problem persisted as soon as file sync
> was turned back on.
>
> The server name & IP on the Win2003 server are identical to the old
> Win2000 server, as is the folder & directory structure which we copied
> off the old server and on to the new.
>
> Is there a possibilith that somewhere in the registry on the work
> stations that some bit of "old" information is creating this problem?
> If so, how would we get rid of it?
>
> If we're going down the wrong road completely on this any pointers in a
> more productive direction would be most appreciated as we have a number
> of positions that travel fairly regularily (to places where even a
> stable dial-up connection to the server that would allow use of the VPN
> isn't really a viable option) and need access to their files.
>
> Thanks

Hi Nia,

I've seen a similar problem before and there it helped to turn off
SMB-signing.

The following link is turning it on for Windows 98, but if you do the
opposite you'll turn it off (obvious... *grin*). The registry entries are
the same:

http://support.microsoft.com/default.aspx?scid=kb;en-us;230545

In Xp it's also possible to do this over the policies, either local or AD...

Let me know if it worked or not...

Cheers,

Robert
!