Unable to connect Windows 95 machine to a share drive on Windows X

G

Guest

Hello All,

I am trying to connect a Windows 95 machine to a share drive residing on
Windows XP machine. The Windows XP machine is in a DOMAIN. Windows 95 machine
is not in the domain. Also, the Windows 95 machine doesn't use Logon window
at all. It just starts up without any Logon window.

When I try to connect the Windows 95 machine using Explorer's Tools-Map
Network Drive, I am unable to connect to the share drive using the UNC
notation as
\\128.195.16.23\D, where D is tha share drive name on Windows XP
Professional machine and it's IP address is 128.195.16.23.

I can ping from Windows 95 to Windows XP Professional without any problem.

Can anyone help me out with any information?

Waiting to hear from you soon.
Thank you.
regards
Partha
 
C

Chuck

Hello All,

I am trying to connect a Windows 95 machine to a share drive residing on
Windows XP machine. The Windows XP machine is in a DOMAIN. Windows 95 machine
is not in the domain. Also, the Windows 95 machine doesn't use Logon window
at all. It just starts up without any Logon window.

When I try to connect the Windows 95 machine using Explorer's Tools-Map
Network Drive, I am unable to connect to the share drive using the UNC
notation as
\\128.195.16.23\D, where D is tha share drive name on Windows XP
Professional machine and it's IP address is 128.195.16.23.

I can ping from Windows 95 to Windows XP Professional without any problem.

Can anyone help me out with any information?

Waiting to hear from you soon.
Thank you.
regards
Partha

Partha,

Enable Windows Logon, reversing the instructions in this article:
http://support.microsoft.com/?kbid=152104

Setup a local account on the Windows XP computer, with a non-blank password.

When you logon to the Windows 95 computer, use the account / password setup on
the Windows XP computer.

--
Cheers,
Chuck
Paranoia comes from experience - and is not necessarily a bad thing.
My email is AT DOT
actual address pchuck sonic net.
 
G

Guest

Hello Chuck,

Thank you for your reply.

Is there any other way without enabling Windows Logon feature of Windows 95
I can do the same?

Like while performing the network map to the shared drive of Windows XP I
provide the USER NAME/PASSWORD.

Waiting to hear from you or anyone else in the group soon.
Thank you.
Regards
Partha
 
G

GTS

Pashan,

1. You have to use the network logon in Windows 95. Specifically the
Microsoft network client has to be selected as the primary logon in the
network configuration. Otherwise File and Printer sharing will not be
enabled. You can use TweakUI to automate the login if you like.

2. Since the XP box is on a domain, it is not using simple file sharing and
must include a user matching the Win 95 box.

3. It is a limitation of Win 9X that the user name used to connect to a
share is the 9X net user name. This cannot be avoided (unlike in XP where a
username can be included as a parameter in a net use command).

4. In addition to the network issues above, the security settings on the
share must permit the access. (e.g. if set to only members of domain, for
example, you would have a problem. It will need to include local users, or
your username specifically.)

I hope this helps.
 
S

Steve Winograd [MVP]

Pashan,

1. You have to use the network logon in Windows 95. Specifically the
Microsoft network client has to be selected as the primary logon in the
network configuration. Otherwise File and Printer sharing will not be
enabled. You can use TweakUI to automate the login if you like.

All peer-to-peer networking functions are available in Windows 95
using either of the choices for primary network login: Windows Logon
or Client for Microsoft Networks.

Client for Microsoft Networks must be in the list of installed network
components, but it doesn't have to be the primary network logon.
Windows Logon is fine.
2. Since the XP box is on a domain, it is not using simple file sharing and
must include a user matching the Win 95 box.

3. It is a limitation of Win 9X that the user name used to connect to a
share is the 9X net user name. This cannot be avoided (unlike in XP where a
username can be included as a parameter in a net use command).

4. In addition to the network issues above, the security settings on the
share must permit the access. (e.g. if set to only members of domain, for
example, you would have a problem. It will need to include local users, or
your username specifically.)

I hope this helps.

I agree with #2-4, and I'm sure that they'll help.
--
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
 
G

GTS

Thanks for the clarification re. point 2.
--

Steve Winograd said:
All peer-to-peer networking functions are available in Windows 95
using either of the choices for primary network login: Windows Logon
or Client for Microsoft Networks.

Client for Microsoft Networks must be in the list of installed network
components, but it doesn't have to be the primary network logon.
Windows Logon is fine.


I agree with #2-4, and I'm sure that they'll help.
--
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
 
G

GTS

Correction - re. Point 1.

--

Steve Winograd said:
All peer-to-peer networking functions are available in Windows 95
using either of the choices for primary network login: Windows Logon
or Client for Microsoft Networks.

Client for Microsoft Networks must be in the list of installed network
components, but it doesn't have to be the primary network logon.
Windows Logon is fine.


I agree with #2-4, and I'm sure that they'll help.
--
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
 
G

Guest

Hello Steve and GTS,

I tried to do whatever you people have referred. But to no avail.

I found one more article
http://support.microsoft.com/kb/q258717/

There it is mentioned that Windows95 and WIndows2000/XP machine must be in
the same WorkGroup in order to use Peer-to-Peer networking.

At the beginning of my mail chain I have mentioned that my XP Pro is in the
DOMAIN.
I have created a local user account on the XP machine.
Then from another Windows 2000 machine which is also in the same domain I can
use the command

NET USE E: \\XP-IP-Address\SHARENAME /USER:XP-MACHINE-NAME\LOCAL_USER

to connect after satisfying the local user password prompt answer.

Also note that if I give the above command without the XP-MACHINE-NAME\
parameter then also it fails to connect after validating the password from
2000 machine to XP machine share drive connection.

From Windows 95 when I try to do
NET USE E: \\XP-IP-Address\SHARENAME

I get the following :

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.

Any way to verify or analyze with some tool why it does fail with Windows 95.
Remember again that my XP and 2000 machines are in a domain.
Windows 95 machine is not in a domain and hence I am using the IP Address.

Also, I have created a share drive on Windows 95 machine and I can comfortably
connect to it from both of my DOMAIN connected XP and 2000 machines.

Ping works from every machine to the other. Hence, network connectivity is
not an issue.

Because from 2000 machine to XP the following command fails [no machine name]:
NET USE E: \\XP-IP-Address\SHARENAME /USER:LOCAL_USER_NAME
whereas
NET USE E: \\XP-IP-Address\SHARENAME /USER:XP-MACHINE-NAME\LOCAL_USER
passes,
so, my doubt is about the specific machine name part when Windows 95 tries
to connect to XP. There is no parameter like USER in Windows 95 NET USE
command, which you have already mentioned. It uses the login user name. But
what happens to the machine_name part of the command for XP to understand.
Because from my experfiment it proves that NET USE command does require the
machine name for the USER part of the parameter.

Any help is appreciated.
Please help.

Thank you.
Regards
Partha
 
G

GTS

Is NetBIOS enabled on the XP box?
--

Pashan said:
Hello Steve and GTS,

I tried to do whatever you people have referred. But to no avail.

I found one more article
http://support.microsoft.com/kb/q258717/

There it is mentioned that Windows95 and WIndows2000/XP machine must be in
the same WorkGroup in order to use Peer-to-Peer networking.

At the beginning of my mail chain I have mentioned that my XP Pro is in
the
DOMAIN.
I have created a local user account on the XP machine.
Then from another Windows 2000 machine which is also in the same domain I
can
use the command

NET USE E: \\XP-IP-Address\SHARENAME /USER:XP-MACHINE-NAME\LOCAL_USER

to connect after satisfying the local user password prompt answer.

Also note that if I give the above command without the XP-MACHINE-NAME\
parameter then also it fails to connect after validating the password from
2000 machine to XP machine share drive connection.

From Windows 95 when I try to do
NET USE E: \\XP-IP-Address\SHARENAME

I get the following :

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.

Any way to verify or analyze with some tool why it does fail with Windows
95.
Remember again that my XP and 2000 machines are in a domain.
Windows 95 machine is not in a domain and hence I am using the IP Address.

Also, I have created a share drive on Windows 95 machine and I can
comfortably
connect to it from both of my DOMAIN connected XP and 2000 machines.

Ping works from every machine to the other. Hence, network connectivity is
not an issue.

Because from 2000 machine to XP the following command fails [no machine
name]:
NET USE E: \\XP-IP-Address\SHARENAME /USER:LOCAL_USER_NAME
whereas
NET USE E: \\XP-IP-Address\SHARENAME /USER:XP-MACHINE-NAME\LOCAL_USER
passes,
so, my doubt is about the specific machine name part when Windows 95 tries
to connect to XP. There is no parameter like USER in Windows 95 NET USE
command, which you have already mentioned. It uses the login user name.
But
what happens to the machine_name part of the command for XP to understand.
Because from my experfiment it proves that NET USE command does require
the
machine name for the USER part of the parameter.

Any help is appreciated.
Please help.

Thank you.
Regards
Partha


GTS said:
Correction - re. Point 1.
 
S

Steve Winograd [MVP]

Hello Steve and GTS,

I tried to do whatever you people have referred. But to no avail.

I found one more article
http://support.microsoft.com/kb/q258717/

There it is mentioned that Windows95 and WIndows2000/XP machine must be in
the same WorkGroup in order to use Peer-to-Peer networking.

That's wrong. Windows networking supports multiple workgroups, and a
computer in any workgroup can access a computer in any other
workgroup. Using the same workgroup makes networking a little easier,
but it isn't necessary.

To access another computer, regardless of what workgroup either
computer is in, type the other computer's name in the Start | Run box
in this format:

\\computer

There are other errors in that article, too. For example, it says:

Note that peer-to-peer workgroup computers typically use NetBEUI
for local LAN communication
[remainder snipped]
--
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
 
G

Guest

Hello GTS,

NetBIOS setting is set to DEFAULT on XP Box as I have seen on the WINS
tabbed page of the Advanced setting of the TCP/IP Properties -- which means
if the DHCP server doesn't provide the NetBIOS setting automatically then
it is enabled.

Now how do we determine whether NetBIOS is enabled on the XP Box by some tool?
Waiting to hear from you soon.

Thank you.
regards
Partha
GTS said:
Is NetBIOS enabled on the XP box?
--

Pashan said:
Hello Steve and GTS,

I tried to do whatever you people have referred. But to no avail.

I found one more article
http://support.microsoft.com/kb/q258717/

There it is mentioned that Windows95 and WIndows2000/XP machine must be in
the same WorkGroup in order to use Peer-to-Peer networking.

At the beginning of my mail chain I have mentioned that my XP Pro is in
the
DOMAIN.
I have created a local user account on the XP machine.
Then from another Windows 2000 machine which is also in the same domain I
can
use the command

NET USE E: \\XP-IP-Address\SHARENAME /USER:XP-MACHINE-NAME\LOCAL_USER

to connect after satisfying the local user password prompt answer.

Also note that if I give the above command without the XP-MACHINE-NAME\
parameter then also it fails to connect after validating the password from
2000 machine to XP machine share drive connection.

From Windows 95 when I try to do
NET USE E: \\XP-IP-Address\SHARENAME

I get the following :

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.

Any way to verify or analyze with some tool why it does fail with Windows
95.
Remember again that my XP and 2000 machines are in a domain.
Windows 95 machine is not in a domain and hence I am using the IP Address.

Also, I have created a share drive on Windows 95 machine and I can
comfortably
connect to it from both of my DOMAIN connected XP and 2000 machines.

Ping works from every machine to the other. Hence, network connectivity is
not an issue.

Because from 2000 machine to XP the following command fails [no machine
name]:
NET USE E: \\XP-IP-Address\SHARENAME /USER:LOCAL_USER_NAME
whereas
NET USE E: \\XP-IP-Address\SHARENAME /USER:XP-MACHINE-NAME\LOCAL_USER
passes,
so, my doubt is about the specific machine name part when Windows 95 tries
to connect to XP. There is no parameter like USER in Windows 95 NET USE
command, which you have already mentioned. It uses the login user name.
But
what happens to the machine_name part of the command for XP to understand.
Because from my experfiment it proves that NET USE command does require
the
machine name for the USER part of the parameter.

Any help is appreciated.
Please help.

Thank you.
Regards
Partha


GTS said:
Correction - re. Point 1.

--

Pashan,

1. You have to use the network logon in Windows 95. Specifically the
Microsoft network client has to be selected as the primary logon in the
network configuration. Otherwise File and Printer sharing will not be
enabled. You can use TweakUI to automate the login if you like.

All peer-to-peer networking functions are available in Windows 95
using either of the choices for primary network login: Windows Logon
or Client for Microsoft Networks.

Client for Microsoft Networks must be in the list of installed network
components, but it doesn't have to be the primary network logon.
Windows Logon is fine.

2. Since the XP box is on a domain, it is not using simple file
sharing
and
must include a user matching the Win 95 box.

3. It is a limitation of Win 9X that the user name used to connect to
a
share is the 9X net user name. This cannot be avoided (unlike in XP
where
a
username can be included as a parameter in a net use command).

4. In addition to the network issues above, the security settings on
the
share must permit the access. (e.g. if set to only members of domain,
for
example, you would have a problem. It will need to include local
users,
or
your username specifically.)

I hope this helps.

I agree with #2-4, and I'm sure that they'll help.
--
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
 
S

Steve Winograd [MVP]

Hello GTS,

NetBIOS setting is set to DEFAULT on XP Box as I have seen on the WINS
tabbed page of the Advanced setting of the TCP/IP Properties -- which means
if the DHCP server doesn't provide the NetBIOS setting automatically then
it is enabled.

Now how do we determine whether NetBIOS is enabled on the XP Box by some tool?
Waiting to hear from you soon.

Thank you.
regards
Partha

Set NetBIOS to ENABLED, not to DEFAULT. Some DHCP servers, especially
in home broadband routers, provide the wrong setting, which results in
NetBIOS being disabled.
--
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
 
G

GTS

Like Steve said, set NetBIOS to enabled rather than default. I think
there's a good chance that will resolve your problem. Please let us know
the result.
 
G

Guest

Hello GTS and Steve,

Thank you for all the information. It worked at last.
Regards
Partha
 
G

Guest

Hello GTS and Steve,

I am able to connect [share drive] between Windows 95 and Windows XP Pro
successfully in both directions.

The only problem I have is that Windows 95 doesn't have any parameter for
USER NAME within it's NET USE command. Hence, it uses the Login User Name
while connecting to Windows XP Pro machine.

I want to use Automatic Login feature of Windows 95 using Registry Hacks as
described in
http://support.microsoft.com/kb/q152104

It works for bypassing Logon Prompt only. It doesn't work for really LOGIN
as NET USE command fails after that.

Because after that if I use NET USE command, then Windows 95 mentions that I
must logon and then only I can use NET USE.

Can anyone help me how to LOGIN automatically within Windows 95 so that I
can use NET USE
command from Windows 95?

Waiting to hear from you.
Thank you.
regards
Partha
 
G

GTS

I would roll back that registry change and try using TweakUI's autologon
feature. I know it works the way you want with Windows 98 and suspect it
will with 95 also.
http://www.microsoft.com/ntworkstation/downloads/PowerToys/Networking/NTTweakUI.asp
--

Pashan said:
Hello GTS and Steve,

I am able to connect [share drive] between Windows 95 and Windows XP Pro
successfully in both directions.

The only problem I have is that Windows 95 doesn't have any parameter for
USER NAME within it's NET USE command. Hence, it uses the Login User Name
while connecting to Windows XP Pro machine.

I want to use Automatic Login feature of Windows 95 using Registry Hacks
as
described in
http://support.microsoft.com/kb/q152104

It works for bypassing Logon Prompt only. It doesn't work for really LOGIN
as NET USE command fails after that.

Because after that if I use NET USE command, then Windows 95 mentions that
I
must logon and then only I can use NET USE.

Can anyone help me how to LOGIN automatically within Windows 95 so that I
can use NET USE
command from Windows 95?

Waiting to hear from you.
Thank you.
regards
Partha


GTS said:
You're welcome. Glad to hear it.
 
G

Guest

Hello GTS,

It worked as exepected. Thank you for that TWEAKUI tool.

But now I have a different issue.

I have two Windows 95 machines. One version is
4.01.0.971 B
and the other version is
4.00.950 B

According to
http://support.microsoft.com/default.aspx?scid=kb;en-us;158238
article
4.00.950 B is
OEM Version.

This machine [4.00.950 B] is working perfectly with the NET USE command as
well as AUTOMATIC LOGIN using TWEAKUI tools.

The other version of Windows 95 [4.01.0.971 B], which I don't have any
documentation on Microsoft Web Site, is not working for the NET USE command.
It's giving Error 53 message [as mentioned in the previous mail] when I try
to connect to Windows XP machine's share drive.
But Windows XP machine can connect to the share folder on this Windows 95
[4.01.0.971 B] machine without any problem.

I have made the TCP/IP properties of both the Windows 95 machines same
w.r.t. all the GUI available parameters.

Any clue how to connect this Windows 95 [4.01.0.971 B] machine to Windows XP.

Remember again, Windows 95 [4.00.950 B] machine is working both ways [i.e.
between Windows XP and itself].

As mentioned before, I am using Windows Logon on both the Windows 95 machine.
Windows XP machine is on a DOMAIN.

I have the only problem for connecting this Windows 95 [4.01.0.971 B]
machine to Windows XP.
Please help with any information about this version of Windows.

I don't want to change this Windows 95 [4.01.0.971 B] machine as this is a
preconfigured embedded machine with lot of hardware in a rack for simulation.
This is working fine except for the share drive connection from this machine.
But if I share from this machine, then I can connect to it from Windows XP.

Waiting to hear from you soon.
Thank you.
regards
Pashan

GTS said:
I would roll back that registry change and try using TweakUI's autologon
feature. I know it works the way you want with Windows 98 and suspect it
will with 95 also.
http://www.microsoft.com/ntworkstation/downloads/PowerToys/Networking/NTTweakUI.asp
--

Pashan said:
Hello GTS and Steve,

I am able to connect [share drive] between Windows 95 and Windows XP Pro
successfully in both directions.

The only problem I have is that Windows 95 doesn't have any parameter for
USER NAME within it's NET USE command. Hence, it uses the Login User Name
while connecting to Windows XP Pro machine.

I want to use Automatic Login feature of Windows 95 using Registry Hacks
as
described in
http://support.microsoft.com/kb/q152104

It works for bypassing Logon Prompt only. It doesn't work for really LOGIN
as NET USE command fails after that.

Because after that if I use NET USE command, then Windows 95 mentions that
I
must logon and then only I can use NET USE.

Can anyone help me how to LOGIN automatically within Windows 95 so that I
can use NET USE
command from Windows 95?

Waiting to hear from you.
Thank you.
regards
Partha


GTS said:
You're welcome. Glad to hear it.
--

Hello GTS and Steve,

Thank you for all the information. It worked at last.
Regards
Partha

:

Like Steve said, set NetBIOS to enabled rather than default. I think
there's a good chance that will resolve your problem. Please let us
know
the result.
--

Hello GTS,

NetBIOS setting is set to DEFAULT on XP Box as I have seen on the
WINS
tabbed page of the Advanced setting of the TCP/IP Properties --
which
means
if the DHCP server doesn't provide the NetBIOS setting
automatically
then
it is enabled.

Now how do we determine whether NetBIOS is enabled on the XP Box by
some
tool?
Waiting to hear from you soon.

Thank you.
regards
Partha
:
 
G

GTS

I don't know about that specific version number. Error 53 indicates a name
resolution issue or connectivity issue, the former in your case since you
can map the other way. You might see if you can connect to (initially if
you can ping) the XP box by IP. I rarely see Win 95 anymore and generally
wouldn't recommend using it, though I understand your issue re. an embedded
box. A few other ideas come to mind - There was a significant service pack
for Win 95 that affected various network issues. I'm not sure if it was
before or after your releases. You might look at
http://support.microsoft.com/kb/143003/EN-US/
which has some related component version info. Also, you might double check
that you have a correct matching user on the XP box. Sometimes spaces or
lower case letters in Win 9X net names can also cause problems mapping to
XP.
--

Pashan said:
Hello GTS,

It worked as exepected. Thank you for that TWEAKUI tool.

But now I have a different issue.

I have two Windows 95 machines. One version is
4.01.0.971 B
and the other version is
4.00.950 B

According to
http://support.microsoft.com/default.aspx?scid=kb;en-us;158238
article
4.00.950 B is
OEM Version.

This machine [4.00.950 B] is working perfectly with the NET USE command as
well as AUTOMATIC LOGIN using TWEAKUI tools.

The other version of Windows 95 [4.01.0.971 B], which I don't have any
documentation on Microsoft Web Site, is not working for the NET USE
command.
It's giving Error 53 message [as mentioned in the previous mail] when I
try
to connect to Windows XP machine's share drive.
But Windows XP machine can connect to the share folder on this Windows 95
[4.01.0.971 B] machine without any problem.

I have made the TCP/IP properties of both the Windows 95 machines same
w.r.t. all the GUI available parameters.

Any clue how to connect this Windows 95 [4.01.0.971 B] machine to Windows
XP.

Remember again, Windows 95 [4.00.950 B] machine is working both ways [i.e.
between Windows XP and itself].

As mentioned before, I am using Windows Logon on both the Windows 95
machine.
Windows XP machine is on a DOMAIN.

I have the only problem for connecting this Windows 95 [4.01.0.971 B]
machine to Windows XP.
Please help with any information about this version of Windows.

I don't want to change this Windows 95 [4.01.0.971 B] machine as this is a
preconfigured embedded machine with lot of hardware in a rack for
simulation.
This is working fine except for the share drive connection from this
machine.
But if I share from this machine, then I can connect to it from Windows
XP.

Waiting to hear from you soon.
Thank you.
regards
Pashan

GTS said:
I would roll back that registry change and try using TweakUI's autologon
feature. I know it works the way you want with Windows 98 and suspect it
<SNIP>
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top