Win 95 will not connect share drive

I have a freshly formatted Windows 2000 Server with SP4 and all available
updates. Trying to connect all the CNC lathes to them, which are 95% Windows
95, and the remaining are Win2K Pro. Works fine from the Win2K Pro boxes, but
when I try to map the share
net use x: \\servername\share
I get the following error from the Win95 boxes.
"Error 53: The computer name specified in the network path cannot be located.
Make sure you are specifying the computer name correctly, or try again later
when the remote computer is available."
The Server is not a PDC, only in the same workgroup as all the PCs. I can
access the shares/etc. fine, so all usename/passwords are correct.
The server has a static IP and all workstations can ping it using the host
name. WINS, etc. are all running.
I even installed dsclient hoping that would help, but nothing has worked.
Does anybody have any ideas? It's nearly impossible to take down these
machine for anything more than a reboot, so all the trial and error things
are becoming an issue.

Pegasus
Thu Dec 13 08:51:59 PST 2007


"dwhagerman" <dwhagerman@news.postalias> wrote in message
news:2455A9C7-023A-4974-8AF0-CAEF5C466BA8@microsoft.com...
>I have a freshly formatted Windows 2000 Server with SP4 and all available
> updates. Trying to connect all the CNC lathes to them, which are 95%
> Windows
> 95, and the remaining are Win2K Pro. Works fine from the Win2K Pro boxes,
> but
> when I try to map the share
> net use x: \\servername\share
> I get the following error from the Win95 boxes.
> "Error 53: The computer name specified in the network path cannot be
> located.
> Make sure you are specifying the computer name correctly, or try again
> later
> when the remote computer is available."
> The Server is not a PDC, only in the same workgroup as all the PCs. I can
> access the shares/etc. fine, so all usename/passwords are correct.
> The server has a static IP and all workstations can ping it using the host
> name. WINS, etc. are all running.
> I even installed dsclient hoping that would help, but nothing has worked.
> Does anybody have any ideas? It's nearly impossible to take down these
> machine for anything more than a reboot, so all the trial and error things
> are becoming an issue.

I would grab an old PC or laptop and load Win95 on it in order
to have a proper testing platform. Use a spare hard disk so that
you don't lose the original OS.

I would then go through the usual motions when configuring
network connectivity, e.g.
- Check the network speed (10 MBits/s)
- Check the IP details
- Do some ping tests
- Make sure that the server name and the share name are
less than 8 chars long
- Check the Event Viewer on the server
- Turn off the server's firewall

3c273
Thu Dec 13 09:11:15 PST 2007

Have you tried mapping with the ip address "net use x:
\\192.168.0.1\sharename"?
Louis

"dwhagerman" <dwhagerman@news.postalias> wrote in message
news:2455A9C7-023A-4974-8AF0-CAEF5C466BA8@microsoft.com...
> I have a freshly formatted Windows 2000 Server with SP4 and all available
> updates. Trying to connect all the CNC lathes to them, which are 95%
Windows
> 95, and the remaining are Win2K Pro. Works fine from the Win2K Pro boxes,
but
> when I try to map the share
> net use x: \\servername\share
> I get the following error from the Win95 boxes.
> "Error 53: The computer name specified in the network path cannot be
located.
> Make sure you are specifying the computer name correctly, or try again
later
> when the remote computer is available."
> The Server is not a PDC, only in the same workgroup as all the PCs. I can
> access the shares/etc. fine, so all usename/passwords are correct.
> The server has a static IP and all workstations can ping it using the host
> name. WINS, etc. are all running.
> I even installed dsclient hoping that would help, but nothing has worked.
> Does anybody have any ideas? It's nearly impossible to take down these
> machine for anything more than a reboot, so all the trial and error things
> are becoming an issue.

Pegasus
Thu Dec 13 11:08:12 PST 2007

AFAIR, mapping with IP addresses is not available
for Win9x machines.

"3c273" <nospam@nospam.com> wrote in message
news:fjrp3i03k0@enews1.newsguy.com...
> Have you tried mapping with the ip address "net use x:
> \\192.168.0.1\sharename"?
> Louis
>

3c273
Thu Dec 13 13:14:43 PST 2007

Didn't even think of that. It's been a while.
Louis

"Pegasus (MVP)" <I.can@fly.com> wrote in message
news:u0LUCubPIHA.4272@TK2MSFTNGP06.phx.gbl...
> AFAIR, mapping with IP addresses is not available
> for Win9x machines.
>
> "3c273" <nospam@nospam.com> wrote in message
> news:fjrp3i03k0@enews1.newsguy.com...
> > Have you tried mapping with the ip address "net use x:
> > \\192.168.0.1\sharename"?
> > Louis
> >
>

Steve
Thu Dec 13 13:52:46 PST 2007

On Thu, 13 Dec 2007 20:08:12 +0100, "Pegasus \(MVP\)" <I.can@fly.com>
wrote:

>AFAIR, mapping with IP addresses is not available
>for Win9x machines.
>
>"3c273" <nospam@nospam.com> wrote in message
>news:fjrp3i03k0@enews1.newsguy.com...
>> Have you tried mapping with the ip address "net use x:
>> \\192.168.0.1\sharename"?
>> Louis

I don't have Windows 95 to test with, but I just tried it on Windows
98, and Windows 98 CAN map a network drive using IP addresses.
--
Best Wishes,
Steve Winograd, MS-MVP (Windows Networking)

Please post any reply as a follow-up message in the news group
for everyone to see. I'm sorry, but I don't answer questions
addressed directly to me in E-mail or news groups.

Microsoft Most Valuable Professional Program
http://mvp.support.microsoft.com

Pegasus
Thu Dec 13 14:48:31 PST 2007


"Steve Winograd" <bc070521m@comcast.net> wrote in message
news:4n93m31d88m84dl8jovf9vn3cel68912lk@4ax.com...
> On Thu, 13 Dec 2007 20:08:12 +0100, "Pegasus \(MVP\)" <I.can@fly.com>
> wrote:
>
>>AFAIR, mapping with IP addresses is not available
>>for Win9x machines.
>>
>>"3c273" <nospam@nospam.com> wrote in message
>>news:fjrp3i03k0@enews1.newsguy.com...
>>> Have you tried mapping with the ip address "net use x:
>>> \\192.168.0.1\sharename"?
>>> Louis
>
> I don't have Windows 95 to test with, but I just tried it on Windows
> 98, and Windows 98 CAN map a network drive using IP addresses.
> --
> Best Wishes,
> Steve Winograd, MS-MVP (Windows Networking)
>

You made me curious, so I dug deep in by box of obsolete
disk images. One of them was Win98, and yes, you're
right, it can do it. Perhaps I was thinking of DOS but I am
disinclined to spend the time to set up a disk with DOS
networking . . .

dwhagerman
Fri Dec 14 03:26:03 PST 2007



"Pegasus (MVP)" wrote:

>
> "dwhagerman" <dwhagerman@news.postalias> wrote in message
> news:2455A9C7-023A-4974-8AF0-CAEF5C466BA8@microsoft.com...
> >I have a freshly formatted Windows 2000 Server with SP4 and all available
> > updates. Trying to connect all the CNC lathes to them, which are 95%
> > Windows
> > 95, and the remaining are Win2K Pro. Works fine from the Win2K Pro boxes,
> > but
> > when I try to map the share
> > net use x: \\servername\share
> > I get the following error from the Win95 boxes.
> > "Error 53: The computer name specified in the network path cannot be
> > located.
> > Make sure you are specifying the computer name correctly, or try again
> > later
> > when the remote computer is available."
> > The Server is not a PDC, only in the same workgroup as all the PCs. I can
> > access the shares/etc. fine, so all usename/passwords are correct.
> > The server has a static IP and all workstations can ping it using the host
> > name. WINS, etc. are all running.
> > I even installed dsclient hoping that would help, but nothing has worked.
> > Does anybody have any ideas? It's nearly impossible to take down these
> > machine for anything more than a reboot, so all the trial and error things
> > are becoming an issue.
>
> I would grab an old PC or laptop and load Win95 on it in order
> to have a proper testing platform. Use a spare hard disk so that
> you don't lose the original OS.
>
> I would then go through the usual motions when configuring
> network connectivity, e.g.
> - Check the network speed (10 MBits/s)
> - Check the IP details
> - Do some ping tests
> - Make sure that the server name and the share name are
> less than 8 chars long
> - Check the Event Viewer on the server
> - Turn off the server's firewall
>
>
>
As for that list, network has been checked, IP's have all been double/triple
checked, server(s) all ping fine through IP or name. No events are being
logged, and the server has no firewall.
Now, IIRC, even Windows 3.1 would recognize share names up to 12 characters
in length?
At this point, setting up a test box would be great, but I'm out of ideas to
try.
Oh, and yes, I did try mapping through the server IP and sharename with the
same result. Yea it's been quite a while for me as well doing much (if
anything) with a Win 95 box!

Bob
Fri Dec 14 05:23:51 PST 2007



dwhagerman wrote:
>
> "Pegasus (MVP)" wrote:
>
>
>>"dwhagerman" <dwhagerman@news.postalias> wrote in message
>>news:2455A9C7-023A-4974-8AF0-CAEF5C466BA8@microsoft.com...
>>
>>>I have a freshly formatted Windows 2000 Server with SP4 and all available
>>>updates. Trying to connect all the CNC lathes to them, which are 95%
>>>Windows
>>>95, and the remaining are Win2K Pro. Works fine from the Win2K Pro boxes,
>>>but
>>>when I try to map the share
>>>net use x: \\servername\share
>>>I get the following error from the Win95 boxes.
>>>"Error 53: The computer name specified in the network path cannot be
>>>located.
>>>Make sure you are specifying the computer name correctly, or try again
>>>later
>>>when the remote computer is available."
>>>The Server is not a PDC, only in the same workgroup as all the PCs. I can
>>>access the shares/etc. fine, so all usename/passwords are correct.
>>>The server has a static IP and all workstations can ping it using the host
>>>name. WINS, etc. are all running.
>>>I even installed dsclient hoping that would help, but nothing has worked.
>>>Does anybody have any ideas? It's nearly impossible to take down these
>>>machine for anything more than a reboot, so all the trial and error things
>>>are becoming an issue.
>>
>>I would grab an old PC or laptop and load Win95 on it in order
>>to have a proper testing platform. Use a spare hard disk so that
>>you don't lose the original OS.
>>
>>I would then go through the usual motions when configuring
>>network connectivity, e.g.
>>- Check the network speed (10 MBits/s)
>>- Check the IP details
>>- Do some ping tests
>>- Make sure that the server name and the share name are
>> less than 8 chars long
>>- Check the Event Viewer on the server
>>- Turn off the server's firewall
>>
>>
>>
>
> As for that list, network has been checked, IP's have all been double/triple
> checked, server(s) all ping fine through IP or name. No events are being
> logged, and the server has no firewall.
> Now, IIRC, even Windows 3.1 would recognize share names up to 12 characters
> in length?
> At this point, setting up a test box would be great, but I'm out of ideas to
> try.
> Oh, and yes, I did try mapping through the server IP and sharename with the
> same result. Yea it's been quite a while for me as well doing much (if
> anything) with a Win 95 box!

Maybe something in this list?
http://www.myitforum.com/articles/5/view.asp?id=960