N
Nia
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
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