xp clients keep loosing network and map drive and they have to reboot

[msnews.microsoft.com]

I have windows 2000 server with xp clients.

All of a sudden, xp clients keep loosing map drives and they have to reboot.

Any suggestion ?

Thanks

 

[Malke]

I have windows 2000 server with xp clients.

All of a sudden, xp clients keep loosing map drives and they have to
reboot.

Any suggestion ?

Thanks

The key phrase here is "all of a sudden". What changed between the time
things worked and the time they didn't?

Malke

 

[Guest]

Malke

thats the issue nothing has changed. its doing something by its self.

 

[Guest]

I think the problem is something to do with the DNS but not sure. the dns is
managed by a third party system and I dont this things resolve correctly
throught out the network.

 

[Malke]

I think the problem is something to do with the DNS but not sure. the
dns is managed by a third party system and I dont this things resolve
correctly throught out the network.

I'm sorry, Marcel but I have no idea what the above means. I do think we
might have a bit of a language issue here in that it seems that English
is not your first language. It is difficult discussing technical things
when there is a language barrier. Perhaps it would be better if you
posted in a newsgroup specifically for your language. If it is French
(my guess), then look for groups in the list at the following site that
have *.fr in them:

http://aumha.org/nntp.htm

Otherwise, have your IT Dept. take a look or call a local professional.

Good luck,

Malke

 

[Walterius]

look for groups in the list at the following site that have *.fr in them:

http://aumha.org/nntp.htm

There ain't none. I searched.

 

[Ron Ruble]

I have windows 2000 server with xp clients.

All of a sudden, xp clients keep loosing map drives and they have to reboot.

Any suggestion ?

Thanks

As indicated by others, something surely changed.
Since it's several machines, I would also guess the
DNS server settings are the reason.

That said, the simplest workaround is to create batch
files that map and unmap drives.

The command to unmap a drive is:

NET USE * /DELETE

The command to map a drive is:

NET USE Z: \\server\share /persistent:no

Replacing the drive letter, server name, and share
name appropriately. Specifying /perstent:no tells
windows not to try to remember the drive mappings,
which your systems seem to have a problem with.


If people's drives become unmapped, they can restore
them by running the batch file. You probably also
want to tell them to unmap the drives in explorer
as well. Mapping this way (non-persistent) sometimes
fails if windows is trying to restore a persistent
share.

 

[Hank Arnold]

If I understand you correctly, it sounds like your systems are pointing to a
3rd party DNS server. This is not good. Your network has to have a DNS
server. It should point to the 3rd party DNS servers via "Forwarders" in the
DNS configuration. It should point to itself for DNS resolution. All
workstations must point to that internal DNS server *NOT* the external one
for name resolution.

 

[Hank Arnold]

This should only be considered a temporary fix until the "real" problem is
identified and resolved.

Also, if there are DNS issues, these commands may not work. One might have
to put in the command

NET USE * \\nnn.nnn.nnn.nnn\sharename

where "nnn.nnn.nnn.nnn" is the IP address of the server....