Map network drive error

  • Thread starter Thread starter Steve
  • Start date Start date
S

Steve

When I attempt to map a network drive from Win2K (the
network drive is on a Win98 machine) I get the following
error message: "there are currently no logon servers
available". I have been doing this for two years now
without any problems.

The only changes I've made to either machine is that I
applied 5 security patches to my Win2K machine on October
20th (KB824141, KB823182, KB826232,KB825119, KB828035).

I have always been able to ping the IP address and the
computer name. All machines can access the internet.

To resolve this issue, I've done the following, one-at-a-
time and retested between actions:
* changed router ports
* updated router firmware
* "un-shared" a folder, "re-shared" it
* created new folders to share
* deleted NIC driver, re-installed from original media
* tried the same from a completely different Win2K laptop

No luck. Any suggestions ?

Thanks,
Steve
 
Thanks Michael,

I thought you were on to something when I read the article
you referenced. However, I had already set-up sharing as
suggested. That got me to thinking though. I changed my
Win98 network setting to share nothing, rebooted, set it
to share, then rebooted again. At first I could finally
map a drive, but after doing some work-related work, I
couldn't. I'm thinking it's the NIC card or perhaps the
Win98 OS that's hosed. I'm going to try replacing the NIC
card, and then if that doesn't work, upgrade Win98 to XP.
I know I'm grasping at straws, but a Linksys NIC card is
only $9.99 after rebate and I've been meaning to upgrade
to XP anyway.

Thanks
 
Steve,
I have to say I am doubtful about it being the NIC card.
If it were I would expect the card to be giving you some
other evidence that it was going bad. But as you say it
is an easy/cheap thing to try.

I had one of these tough problems recently. Word 2000
would sometimes hang when trying to access a file off the
network. I tried everything. Finally I told the client
that we needed to try loading Windows XP on the machine.
That fixed the problem. I wonder if that is where you are
going to end up?
Michael
 
Back
Top