Mapped Drives/Slow Network

We are currently in the middle of upgrading our windows 98 Machines with Dell XP pro machines, we have upgraded about 7 users so far and have ran into several problems. One of the problems I have noticed is that when I map a drive to a shared folder on NT and I restart the computer for some reason XP says it cannot connect the network drive and the drive has a red X through it, but if you click on the drive it opens fine and the X goes away this happens everytime you restart the machines. Second problem is network applications and shared folders, it seems that users have to wait from anywhere from 1-3 minutes before they are able to open a shared folder on the servers and before the (not responding) sign goes away.

Why is XP doing this? Windows 98 is still doing very well and does not have this problem. Is there a way to fix this?

Mannyg wrote:
> We are currently in the middle of upgrading our windows 98 Machines with Dell XP pro machines, we have upgraded about 7 users so far and have ran into several problems. One of the problems I have noticed is that when I map a drive to a shared folder on NT and I restart the computer for some reason XP says it cannot connect the network drive and the drive has a red X through it, but if you click on the drive it opens fine and the X goes away this happens everytime you restart the machines. Second problem is network applications and shared folders, it seems that users have to wait from anywhere from 1-3 minutes before they are able to open a shared folder on the servers and before the (not responding) sign goes away.
>
> Why is XP doing this? Windows 98 is still doing very well and does not have this problem. Is there a way to fix this?

To cure the drive mapping problem, try this: create a .BAT file
on the client PC(s), containing a NET USE command for each mapped
drive; then, create a link to that .BAT file in the Startup folder
to invoke the .BAT file when the client reboots.

You must tailor the NET USE commands to your network and your
tastes, but a sample would look like:

Net use P: \\PC-P\ShareP /persistent:yes
Net use Q: \\PC-Q\ShareQ /persistent:yes PasswordQ
Net use R: \\PC-R\ShareR$ /persistent:yes /user:Stupid PasswordStupid
Pause
Exit

The Pause command allows the user to see if the NET USE commands all
worked; network problems and host reboots sometimes prevent NET USE
from working. If the user is too naive to recover from such problems,
omit the Pause command.

{And, if your organization is PC, substitute PHB for Stupid. <g>}
--
Cheers, Bob

"Bob Willard" wrote:

> Mannyg wrote:
> > We are currently in the middle of upgrading our windows 98 Machines with Dell XP pro machines, we have upgraded about 7 users so far and have ran into several problems. One of the problems I have noticed is that when I map a drive to a shared folder on NT and I restart the computer for some reason XP says it cannot connect the network drive and the drive has a red X through it, but if you click on the drive it opens fine and the X goes away this happens everytime you restart the machines. Second problem is network applications and shared folders, it seems that users have to wait from anywhere from 1-3 minutes before they are able to open a shared folder on the servers and before the (not responding) sign goes away.
> >
> > Why is XP doing this? Windows 98 is still doing very well and does not have this problem. Is there a way to fix this?
>
> To cure the drive mapping problem, try this: create a .BAT file
> on the client PC(s), containing a NET USE command for each mapped
> drive; then, create a link to that .BAT file in the Startup folder
> to invoke the .BAT file when the client reboots.
>
> You must tailor the NET USE commands to your network and your
> tastes, but a sample would look like:
>
> Net use P: \\PC-P\ShareP /persistent:yes
> Net use Q: \\PC-Q\ShareQ /persistent:yes PasswordQ
> Net use R: \\PC-R\ShareR$ /persistent:yes /user:Stupid PasswordStupid
> Pause
> Exit
>
> The Pause command allows the user to see if the NET USE commands all
> worked; network problems and host reboots sometimes prevent NET USE
> from working. If the user is too naive to recover from such problems,
> omit the Pause command.
>
> {And, if your organization is PC, substitute PHB for Stupid. <g>}
> --
> Cheers, Bob
>
>
Bob,

Thank you I will try that, do you have any Idea why networking is slow to react when browsing folders on remote servers.

Mannyg wrote:
>
> "Bob Willard" wrote:
>
>
>>Mannyg wrote:
>>
>>>We are currently in the middle of upgrading our windows 98 Machines with Dell XP pro machines, we have upgraded about 7 users so far and have ran into several problems. One of the problems I have noticed is that when I map a drive to a shared folder on NT and I restart the computer for some reason XP says it cannot connect the network drive and the drive has a red X through it, but if you click on the drive it opens fine and the X goes away this happens everytime you restart the machines. Second problem is network applications and shared folders, it seems that users have to wait from anywhere from 1-3 minutes before they are able to open a shared folder on the servers and before the (not responding) sign goes away.
>>>
>>>Why is XP doing this? Windows 98 is still doing very well and does not have this problem. Is there a way to fix this?
>>
>>To cure the drive mapping problem, try this: create a .BAT file
>>on the client PC(s), containing a NET USE command for each mapped
>>drive; then, create a link to that .BAT file in the Startup folder
>>to invoke the .BAT file when the client reboots.
>>
>>You must tailor the NET USE commands to your network and your
>>tastes, but a sample would look like:
>>
>> Net use P: \\PC-P\ShareP /persistent:yes
>> Net use Q: \\PC-Q\ShareQ /persistent:yes PasswordQ
>> Net use R: \\PC-R\ShareR$ /persistent:yes /user:Stupid PasswordStupid
>> Pause
>> Exit
>>
>>The Pause command allows the user to see if the NET USE commands all
>>worked; network problems and host reboots sometimes prevent NET USE
>>from working. If the user is too naive to recover from such problems,
>>omit the Pause command.
>>
>> {And, if your organization is PC, substitute PHB for Stupid. <g>}
>>--
>>Cheers, Bob
>>
>>
>
> Bob,
>
> Thank you I will try that, do you have any Idea why networking is slow to react when browsing folders on remote servers.

No, but others (Steve W.?) may. You may want to try a new thread to
ask just about that; or, better yet, search this NG (via Google) as
that issue has been frequently discussed.
--
Cheers, Bob