Mapping causing startup problems

  • Thread starter Thread starter Tewfik Lobbos
  • Start date Start date
T

Tewfik Lobbos

Two computers in my home network, connected by a crossover cable:
Comp2000 under win2000pro sp4 and Comp98 under win98se.
Sharing is ok (both ways), except for startup difficulties in Comp2000
only, due to the mapping of drives:

1) When Comp98 is OFF and Comp2000 is started:
the boot process cannot complete unless I am there, because a window
pops up: "An error occurred while reconnecting to \\Comp98\c...", and I
have to click "OK".
(If I start Comp98 after that, I can see the c: drive of Comp98 in
Comp2000's MyNetwork, but the mapping isn't active. I have to disconnect
the drive and then map it again. In contrast with (2) below, the mapping
is immediate)

2) When Comp98 is ON and Comp2000 is started:
the operation of "Restoring \\Comp98\c" is longer then the rest of the
boot process: 55 secs vs 45 secs (~1:40 in all).

No difficulties in Comp98, where I enabled the Quick Logon feature.
And the problem is protocol independent: until this morning, I was using
tcp/ip. I then switched to netbeui: no change in respect with what I
said.

Most important for me is solving (1): I want Comp2000 to start
unattended, even when Comp98 is off. Booting speed, although
exasperating, is less important. Any thought ?
 
Number 2 is solved (the duration of the startup process).
Somehow, tcp/ip got checked in the list of components of my
Local Area Connection, in Comp2000. I unchecked it again,
and now Comp2000 boots up in 45 seconds, when Comp98 is on.

Please someone help me with number 1.
 
Number 1 is solved.


Tewfik said:
Number 2 is solved (the duration of the startup process).
Somehow, tcp/ip got checked in the list of components of my
Local Area Connection, in Comp2000. I unchecked it again,
and now Comp2000 boots up in 45 seconds, when Comp98 is on.

Please someone help me with number 1.
Click to expand...
 
Back
Top