Discussion Locked

Win 2000 and 95 Clients

0 helpful
170 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I have a small network with a Win 2000 Server and mostly Win 2000 Workstations, but there are a couple of Win 95 Clients also. The problem is the Win 95 clients can see and access everyone including themselves but none of the 2000 machines includingthe server can access the Win 95 Clients.
All you get is this message -
//computername is not accessible
The account is not authorized to log in from this station. -

I can ping the 95 machines from any station by name or IP address.
Please help. I know this must be something simple but I can't find it.
Thanks. TheTravman..................

170 replies

by austinadkins

Along the same lines, I am setting up a server, I have installed DNS and WINS, and my clients wont log in, but they show up on the server's Neighborhood Network. Still racking my brain.

by mvermaat

Try using the "File and Print Sharing voor Microsoft Networks" service on the clients.
If that's not working either go to the client's pc and make sure that the name of the workgroup is the same as the domain name.
Succes !
Let me know if it works.

by thetravman

Thanks for the reply but I've got File and Printer sharing enabled and the name of the workgroup is the same as the name of the domain.
That's why I'm pulling my hair out on this one.

by rschmid1

Ensure that the 2k svr has net bios protocol and clients as well... try that and see if it works.. sometimes the tcpip protocol does not allow the clients to login on for the first time using ip.. Netbios should do the trick...
If it works email me@ rschmid@alside.com

by themacd

If you are unable to see Win95 clients I have found that if you enable your Routing and Remote Access service that seems to solve the problem

by chrismccoy

I apologize for not reading the entire thread, but on the Windows 2000 Server CD you will find the Win 9x Client for Windows 2000. You need to install this on every windows 9x machine that will participate in your windows 2000 network. Hope this helps.
Chris McCoy
MCSE, A+

by thetravman

Thanks but that hasn't worked either.
I've tried sharing both ways and neither works. I don't think it's a sharing problem,
but then again I don't know what the problem is.
Let me know if you think of something else.

by gicu artistu'

You said that you could ping it. Did you tried to use net use L: \\\share. If this doesn't work maybe you have Win95 OSR2 with the "wierd" FAT32. Go back to normal FAT and it should work. If it still doesn't work you have something with the browser master on your network (try to disable it from Win95 in the File and print sharing properties).

If it does work then you should check your Wins server.

Luck.

by thetravman

How do you do that?
I installed the DSClient from the Windows 2000 Server CD-Rom. It installed fine but I could never find anything about how to run it.
I didn't know if just installing it was all you had to do or if there was more. There's very little documentation on it.

by airmen80

Sure
Before installing DSC on a computer running win95 you must install IE 4.01 or later and enable the active desktop.

Then in the clients\win9x folder on 200 server or advanced server, run dsclient.exe command. from the workstation.

setup runs and copies everything over. Finish and restart.

by tomkelly99

can you tell me what the access control setting is at [controlpannel-network-access control] should be set to userlevel with the name of your server that is doing the control for your network, dont you have to also add the name of the 95 pc's to the nt-server

by bogdan

- login using username/password of a CERTAIN member of domain
- create computer accounts for W95 machines on the domain's PDC
- another good practice may be reinstalling the TCP/IP protocol on W95 machines and re-check NIC's settings

by mcauchon

if your user exist on the server and you c'ant login try double click on client for microsoft network and check logon to windowsnt domain and enter the workgroup name reply if its working please!!

by thetravman

My workgroup name is the same as the domain
name. The 95 client finds the domain just fine and it can see and access everyone. It's the 2000 clients that can't access the win 95 client.
Thanks for the input though.
Any more ideas?

by kim2786

how about checking 95 clients protocol , make sure that they are the same as 2000 clients. Use TCP/IP do not mix with any other protocal.

by thetravman

Already using TCP/IP and Netbios with print and file sharing turned on and binding to Client for Microsoft Networks.
I'm using it configured this way on the 95 client and TCP/IP and Netbios on the server and 2000 machines.
Thanks anyway though.
Any more ideas?

by mwca

having Win2K and Win95 communicate is mainly based on username and password.

I have a small office setup with a couple Win2k machines and a couple Win95 machines. To get them communicating all PCs had to be on the same subnet and in the same workgroup.

Finally, since your network settings sound correct, setup a user account on a Win2K machine and on a Win95 machine with the same username and password.

It wasn't until I had set this up that I access shared files.

If this works, you may have to setup accounts for all your Win95 users on each Win2K machine.

Good Luck!
Mark.

by airmen80

I just thought of a couple other things to try. Is netbios installed? or installing a WINS server might help. When the 95 clients log on they will enter themselves into the WINS server and their names can be resolved. As you prob know w2k is alldns based and now that i think about it from your description starting the wins service might be the best bet.

by thetravman

I've installed WINS on the 2000 server but it doesn't see anything. I also can list the clients in MMC - DNS but when I use NSLOOKUP to see if the DNS Server is working it says it doesn't see a default DNS Server.
This was installed by the Setup when the Server was setup so what could be wrong with it. This could be the problem in the first place. Could be why WINS sees nothing too.
What's goin' on?

by airmen80

I would try WINS first.
Go to the TCP/IP config on the workstations. Enable WINS resolution and punch in the WINS server IP.

if no go
try loading the NetBEUI protocol on W2KServer. Make sure NetBios is enabled.

by austinadkins

Had the same problem. I was running WINS and DNS for my 95 clients so, I uninstalled WINS, and disabled it on my clients. Setup DNS for the clients and ran that service on the SVR and it worked, dont know if that'll helped and now that I did I have less of an understanding of it but it works.

by nicks

I may be off track here, but it's worth a shot. Check your DNS settings on the clients to make sure they have the correct host name and domain. (or in DHCP on the server if applicable). I'm thinking that if 2000 is moving away from WINS towards dns,the 95 clients will need to register correctly with the dns server.

by jacki

If your 95 clients are not on the same subnet as your WINS Server- you may want to install a WINS Proxy on the segment where the WIn 95 clients are located.

by thetravman

They're on the same subnet and it's all ran by DHCP and Active Directory. All the IP addresses are obtained automatically from the server. I can ping the names and addresses from anywhere and get a good response.
I've also enabled WINS and DNS is showing running correctly with NSLookup.
I'm stumped.

by supreme21

I don't know i fthis wil help or not but try this:

Disable the "Digitally sign server-side communication when possible" setting in the Securdc4.inf file. (You have to go into domain Policy then go into security policy an disable Digitally sign server-side communication and client.)

Save the Securdc4.inf file as another .inf file (for example, as Securup4.inf).

Load the new settings into the registry by using the following command:
"c:\winnt\system32\secedit.exe /configure /cfg c:\winnt\security\templates\securup4.inf /db c:\winnt\security\database\secedit.sdb /log c:\temp\secedit.log"
NOTE: This is a single command. It has been wrapped for readability purposes.

If thsi doesn't work do you have netbios over tcp/ip on theserver enabled?

by thetravman

Yes. It's name is in the Active Directory.
It realizes it's part of the domain because it logs me on with my domain name and password but it seems the Server isn't allowing the other computers into it.
Thanks.

by kalpesh_it

First of all i should know that is wins service is installed on ur server & if not u should do it or else update the lmhosts file on win2000 clients machine.

by thetravman

It's installed. I'm not sure if it's working correctly. Is there a command to check this out from the server.
I don't see anything in the MMC-Wins Console.
THanks.

by thetravman

Both Netbios over tcp/ip and netbui have been enabled from the start except when I disabled them to try without them. I've also enabled WINS and then disabled it again when it done no good.
I'm going crazy!!!!!!!!!!

by brogers

I just installed a network at home to get myself familiar with the Win2000 Server (we aren't running it at work and I'd like to have some experience with it before we install it in a true "work evironment").

My problem is that my Win98 machine cannot log onto the network. Workgroup = Domain name. All network configurations appear correct (Server is 10.0.1.1 and Win98 PC is 10.0.1.2, Server domain is "Israel", PC workgroup is "Israel", link lights on the network are nice and green, I can ping the IP addresses and get responses--but anytime I click on "network neighborhood" on the Win98 PC, I get an error--anytime I force a login (it won't login when it boots, I have to tell it to log-off the user) using the Administrator sign on and password, I am told there are "no domain controllers".

I have experience setting up users on Win NT (in fact, I'm a Network Administrator at the office), so this is really irking me that things are significantly different with W2K.

Any suggestions?

Benjamin

by marshall

make sure that you have the server options and scope configured. go to administrative tools and click on configure this server then networking and then DHCP, I have forgotten to configure the options and took a while to figure it out.

by brogers

I have DHCP running--but I bypassed it with the Win98 PC and manually configured the IP address as 10.0.1.2.

I have the Scope of DHCP set to 10.0.1.0 -- 10 - 250 and using a subnet of 255.0.0.0.

I have named the Scope "Judah".

Benjamin

by rareamer

I just upgraded our server to W2k and some of my 98 clients are running fine with the exception of one 98 and one 95 client. I can't find diddley on this subject at Microsoft's knoewledge base. What's strange also is that the 98 that won't log on can actually accesss our financial program that resides on the server. I've also noticed that pinging from ther server to workstations comes back with request timed out, but when I ping from my workstation I get every station that's connected. Kudos tothe first person who figures this all out!

by brogers

The Win 98 PC in question is a 1 GHz Athlon with a built in RealTek ethernet card on the motherboard. I tried to determine if it was a NIC/driver problem--but the only other NIC I had with me was another RealTek.

Another interesting side issue: When the Win 98 PC first powers up, you can watch the link lights on the hub as it communicates with the server--they are both flashing on and off in rapid succession. Then, just before you'd expect to see a log-on window, the Win 98 PC resets.

This is frustrating me to no end...

Benjamin

by marshall

On the 95 machine check to make sure that the c (or d whichever you want shared) is shared.

by thetravman

I've had them shared both ways but it doesn't even make it that far. It says I can't log in to it from the station I'm at.
Once again let me say that no suggestion or question is dumb. The only way to solve this is to get every possible angle on itand then kick it in the butt.
Thanks for trying.

by jeckhout

If it says can not log on from the station your at maybe there is a setting in a security policy somewhere dissallowing this type of connction.

Since all the workstations can login to the domain and all the hosts can see each other. It seems your DHCP and DNS are all configured properly.

I'd guess you need to focus on different policies (in the active directoy and on the 95 workstation) until you find the problem. I have not run into this problem so I can not be more specific. I'm just taking a guess based on the error message you are getting when you try and log in.

I'd also double check the 95 Active directory client.

Just my 2 cents... hope it helps.

by Former member

In Win2000 Server CD is folder Client. instal this programm On win 95 computer and join Client to Domain

Pleas mail me if you still have a problem.
Martins

by thetravman

The 95 Client has never had a problem joining the domain. In the network Neighborhood it is listed under the domain and when you log onto it you have to use your domain username and password, but no one can access it. It seems to be a name resolution problem but I can ping it by name or IP address.
Thanks anyway.

by dhxinc

I had a problem like this with Win 98 and
Win 95 client (long time ago).
Start, Settings, Control panel, Network, Identification tab, not sure which one,
"Computer name", or "Workgroup" on Win 95 client contained "Special Characters" (-_.,)
I changed it to A-Z 0-9 only, that fixed the problem.

Hovsep Movsessian
dhxinc@earthlink.net

by thetravman

My domain name is a simple Three letter word and the computer name is a four letter word. I haven't used any special characters in any of the computer names.
Thanks anyway.

by 007jam

I routinely access 9x clients from w2k svr and pro. You don't hane a name resolution problem if you can ping host/netbios name and ip address successfully. Try ensuring that netbeui and file and printer sharing for microsoft networks are installed at every 9x client and that all w2k clients are also configured for netbeui. Bear in mind the additional traffic this will cause as shares generate braodcasts. I hope this helps.

by c_alberts

Well, I have a similar structure, Win2K server, three Win2k pro stations. The majority of the other stations run 95/98.

I have had no problems accessing any of the workstations. I think the difference is that
All the workstations are running as a workgroup. Maybe that could help you.

by thetravman

Are all of your workstations in a workgroup or just the 95/98 stations?
If all are then how do you set up the 2000 stations to run in a workgroup from active directory?
I've never found any mention of setting up a workgroup in 2000.
Thanks.

by rogi

Firstly enable the guest account on the 2000 boxes. That way pass through wont be used. If your'e wanting more security create a user account for each of the Win95 users on each of the 2000 PC's. Remember the exact Username and Password must be usedfor pass through to work. So this can be a major mission if a Win95 user changes his own password and then tries to access the 2000 Box again. Much simpler - enable the Guest Account...

by rogi

Previous answer assuming their is no AD or Domain and you are in a workgroup enviro.

by thetravman

Guest account already enabled with standard user access and I have active directory.
No workgroups.
Thanks anyway.

by nichomach

If you can ping by hostname or IP from all your 2K and 95 machines, hostname resolution is working fine, so if it ain't broke don't fix it. Likewise, mucking about with installing NetBEUI won't help.
The error is being blunt. It's telling you that it's a security issue, not name resolution. Is your sharing on the 95 based PCs share or user based?
If share based, try switching to user-based, and telling them to get the account list from your domain.

by gardbc

If you have set the permissions to full, then did you assign a password to the account?
Win2k doesn't seem to like a "user" to have access without a password.
I have seen this happen a couple of times. Since you can ping the PC in question, I would think it is a permission issue.
Just a thought....

by thetravman

When this started I had the drives on the 95 machines user-based. The 95 machines even saw the active directory user names and let me choose who to give access to. I tried giving full access to everyone (even the world) but they still refused accessto them.
Thanks and I'll try the Microsoft Article you listed below.

by arg cio

do you have profiles setup on the Windows 9x PC's? check user profiles.. log in to the Win9x machines locally with the same user id and password.. then try..

If you have network profiles.. check to make sure all settings in these are correct.
Good luck, and happy hunting..

by dale

Our network is peer to peer and we assign ip addresses but once had a problem where you could ping the computer but it would not connect. Finally found two occurrences of tcp/ip running. Used ipconfig from the dos prompt to see them. Deleted bothand reinstalled the tcp/ip and it worked.

Good Luck

by rachaelpearl

I have had similar issues on a doman with 98 95 workstations. it would ask for a password to get acess to the shared drives or folders on the server or 2k systems. i had to create a user account on the windows 2k systems EXACTLY the same(user name and password) as the user logs on to the 98-95 systems. has to be exactly the same created a user acounts on the win 2k system.
Good luck let me know if this helped

by spacesam

Enable DNS on your server if it's not enabled, then try specifying the IP address, DNS and subnet IP.
Make sure all clients are in the same subnet.

by spacesam

one thing more.., is short, but it can work. Make sure you have the correct host name (try using the computer name), and the domain name.

by dbade

Since I don't have any Win95 machines in my office anymore, I really can't help to much. It does appear to be a permission problem though. Have you checked the network protocol binding against the network card on the WIN95 machine ? Check them all and make shure nothing is out of sink!

If you continue to have problems, do what you should have done earlier - UPGRADE and get away from Winows 95 -

Good Luck!

by thetravman

We would get rid of 95 but the piece of software we run will only run in 95 and no longer is supported for upgrades from the company that made it.
I think you're right about the permissions though. I just can't find where it's going wrong.
Thanks.

by dan

First, I assume what you mean by "see and access" is through network neighborhood. Also, that your working in a Workgroup with all clients in the same workgroup. Obviously, your network connectivity is good because you can ping, so? browsing must be what we?re talking about. Browsing is accomplished by the browser services of a WINx machine. Browsing is assisted through the WINS but WINS is not required. Browsing has nothing to do with DNS (in a mixed enviornment) or DHCP (as long as your static IP is ok and since you can ping, you should be ok) so let?s not consider these a problem.
Second, WINS will help if your clients are on different subnets and speed up the name resolution. If you have a WINS server setup, make sure all your clients have their TCP/IP properties set for the WINS server so they will register with the WINS server when they boot. You can also use an LMHOSTS file if you?re familiar on how to use this. Again, just a tool, not a requirement.
Since the second paragraph is just a tool, let?s look at the requirements.
-WIN9x must have file and/or printer sharing enabled. You said you already did this.
-NetBIOS over TCP/IP must be enabled on the W2K machines.
-WIN9x share permission should be per shareto make troubleshooting easier.
-WIN95 network protocols must have the binding order with TCP/IP at the top.
-WIN9x must be logged in as listed in Start/LogIN/OUT.
These are the most common problems. Once you are sure you have these configured correctly, you should be able to determine your problem from here.

by thetravman

Thanks for the info. I'll look at the 95 machine again but I think everything is already set as you suggest or has been during one test or the other.

by lpc

try this one,Check the permission control in Windows 2000 server if the following accounts in your server is in the right ones.
User Manager for domains...YOu said that only
win 95 cannot access the win 2000 servers,,

tnx

by gklassen

I have had a similar problem although with Samba. I found that creating an LMHOSTS file in the Windows directory and rebooting the PC cleared up most of my problems. I don't have an explanation and it is a pain to install a LMHOSTS file on each client but for me this worked.

by harm.groenendijk

I don't know if it is of any help, i have the problem the other way around, can't browse form win9x to win2k. Since you're using win9x clients in your network changes are high that they run on 10Mb NIC's. Win2k with new hardware wil run with there NIC's on 100Mb. Set them fixed to 10Mb and see if they can connect. Other tip is try to connect from the old command prompt using the NETUSE command (NETUSE /? shows complete options).

by thetravman

Thanks for the suggestion. I tried it but the speed did no good and when I tried the net use command I got the exact same message I get in network neighborhood.
"The account is not authorized to log in from this station."
Any more ideas, please let me know.

by k.yoda3

Hi,
Not sure if this applies but I had a problem with Win98 and W2K, found one solution in a manual for a NIC, install Microsoft's ipx/spx compatible protocol. When I did that then everyone was able to see each other.
Hope it helps....

by thetravman

I had ipx/spx installed when this all started but disabled them thinking that they might be the problem. No such luck. So far I've had ipx/spx, Netbeui, Netbios over ipx/spx, Netbios over tcp/ip and probably every other combination there is.
I've thought about standing on my head and chanting as a last resort.
Thanks for the reply though.

by paul moorhouse

Cannot Connect to Password-Protected Share on Windows 95/98 Computer

The information in this article applies to:

Microsoft Windows 2000 Advanced Server
Microsoft Windows 2000 Datacenter Server
Microsoft Windows 2000 Professional
Microsoft Windows 2000 Server
Microsoft Windows NT Server versions 3.1, 3.5, 3.51, 4.0
Microsoft Windows NT Workstation versions 3.1, 3.5, 3.51, 4.0
Microsoft Windows 95
Microsoft Windows 98

SYMPTOMS
When you try to connect to a share on a computer running Windows 95 or Windows 98 from a Windows NT-based or Windows 2000-based computer that is either in a workgroup or not in the same domain, you may prompted for your user name and password. If the Windows 95/98-based computer is using share-level security with a password-protected share, it does not recognize your credentials.

RESOLUTION
To gain access to the share, type Windows 95/98 computer name\administrator as the user account and the password for the share when you are prompted for your credentials. Substitute the computer name of the Windows 95/98-based computer for Windows 95/98 computer name.

MORE INFORMATION
In Windows 95/98, you can specify share-level or user-level security for protecting shared resources on the computer. Share-level security requires file and printer sharing services.

Share-level security protects shared network resources on the computer with individually assigned passwords. For example, you can assign a password to a folder or a locally attached printer. If other users want to gain access to the shared resource, they must use the appropriate password. If you do not assign a password to a shared resource, every user with access to the network can gain access to the resource.

User-level security protects shared network resources by requiring that a security provider authenticate a user's request to gain access to resources. The security provider

by thetravman

It never even allows me to get that far. It says I don't have access to the computer. It won't even let me see the shares, much less try to access them.
Thanks anyway. I had read that article too.

by blkjoe_1999

It may be that a remote control software will help you to access the machine and you will not have to worry about some out of the ordinary setting. I use PC-Duo at my helpdesk.

by waynecsmith

Check the network services (file, print, directory) and where the authentication of the 95 boxes takes place...

by azam.quadri

I think the Win95 clients at the time of joining win2k domain should have the workgroup name same as the domain name so that they are listed in the browse list.

by azam.quadri

I think the Win95 clients at the time of joining win2k domain should have the workgroup name same as the domain name so that they are listed in the browse list.

by wmastokes

We had the same problem at our site. The Win95 machines could see everything but the Win2000's couldn't (through Network Neighborhood). What I did was have the Win2000 pc's do a Start/Search/Files or Folders and choose "Computers", then plug in the IP address of the Win95 PC's and it would find them. You can make a link to them and share files if the Win95 PC's have any shared folders set up.

You might try this and see if it works for you. Good Luck....

Wm A. (Tony) Stokes
1/31/2001wmastokes@hotmail.com

by thetravman

O.K. This still hasn't totally solved the problem but I was able to see and gain access to the shares.
This must mean it's a name resolution issue.
Am I right?
If anybody reads this reply let me know.

by stephen.land

An earlier reply seemed to indicate that you were having a problem with connectivity to the Win95 PC. If you can connect to the Win95 PC by typing "\\PCName\SharedFolder" in the Start-->Run box, then the issue is network browsing. The MS TCP/IP stack is (and always has been) notorious for incomplete displays of network resources. One of the problems is that the Browse Master PC updates relatively infrequently. A workaround is to temporarily map a shared folder(s)on the Win9x PC to a drive letter on the Win2k PC. Afterward you can disconnect the drive. If it has been mapped long enough for the Browse Master PC to update its resource table, then the Win9x PC shared resources should be visible in Network Neighborhood.

by thetravman

I've tried both in the what seems like millions of tests I've run, but it never even makes it to the point of letting me see the shares in the network neighborhood. It won't let me have access to the computer itself. I'm going crazy......

by amartin

Have you enabled File and Print sharing on the Win 95 boxes? By default it is not and though you can see the '95 boxes on the network you will not be able to access them.

Also you may want to switch the Win95 boxes to User-level security and have the W2K Server be the security provider. This will allow you to assign access to shares to users or groups on the W2K Server machine. If the server is a domain controller then you would be able to assign permissions based on domain user accounts or groups.

by stait

Yes you are correct it's a resolution problem.

I have struck something similar once before and it drove me insane for about a week.

Hopefully this may help, check for an LMHOST file, if you are running one check the entries very thoughly.

If I remember rightly (anyone feel free to correct me) the network browser server will check for entries in the LMHOSTS file before it uses WINS but if you just ping the hostname it will resolve from WINS before LMHOSTS (strange but true. So if you LMHOSTS contains an in correct ip address for the client or if you are using DHCP and the workstation has pick up a different ip than is in the LMHOSTS you would get the symptoms that you are describing.
Anyway let me know how you go.

Cheers

by Former member

I was just doing some research about Win2k and I ran across a possible solution. Try checking your WINS setting.
Right click My Network Places\Properties
Right click Local Area Connection\Properties
Select Internet Protocol (TCP\IP)
PropertiesAdvanced
WINS
At the bottom of the window will be three options for NetBIOS over TCP/IP.
Win2K has a default WINS setting of "Enable NetBios over TCP/IP". If your box has a fixed IP or your network uses DNS only then you could disable NetBIOS over TCP/IP. If you use a DHCP server then select "Use NetBIOS setting from the DHCP server".

by lanman52

Cause:
Some non-Microsoft SMB servers only support unencrypted (plain text) password exchanges during authentication.

The SMB client redirector in Windows NT 4.0 Service Pack 3 and later including Win2K handles unencrypted passwords differentlythan previous versions of Windows NT. Beginning with Windows NT 4.0 Service Pack 3, the SMB redirector does not send an unencrypted password during authentication to an SMB server unless you add a specific registry entry.

In previous versions, the client would automatically negotiate downward to unencrypted (plain text) authentication if requested from the server.

Resolution:
to enable unencrypted (plain text) passwords for the SMB client on Windows NT 4.0 Service Pack 3 and newer systems, modify the registry in the following way:

Run Registry Editor (Regedt32.exe).

From the HKEY_LOCAL_MACHINE subtree, go to the following key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Rdr\Parameters
On the Edit menu, click Add Value.

Add the following:

Value Name: EnablePlainTextPassword
Data Type: REG_DWORD
Data: 1
Click OK and then quit Registry Editor.

Shut down and restart Windows 2K.

Give this a try and let me know how itworks. I know it is not exactly what you mean but it might just work.

Lanman52@hotmail.com

by stevelotho

Hi,
I think your problem is with the naming of the 95. If you have used this name before Win2000 retains the name somehow and will not release it.

If you change the name of your 95 to something else it should be able to log on to the network and see all the nodes in your network.

I had the same problem about a week ago.

Steve

by jabettasso

I don't know if this has been brought up yet, but if the high security policy template has been applied then win2000 pc's will only be able to communicate with each other. Apply the basic workstation policy to fix communication to 9x clients .

by pammc

1) make sure File and Print sharing is turned on on the Win95 clients
2) make sure you don't 'esc' or bypass the network login (not the domain login but the 'Windows' login) on the Win95 clients
Aside from that....I'd double check to make sure the Win95 machines have all the correct network settings (especially DNS and WINS), although it sounds like the problem is more related to access (thus my first two suggestions).

by unmelt

I'm not sure if the last poster's solution actually helps, as I don't have the problem configuration running on my network. But it makes sense. While TCP/IP is the optimal protocol for communication cross-platform over the network, NetBEUI does a much better job with MS to MS connections within the same subnet on a network.

Just wanted to point out that it was NetBEUI he meant to say.

by ahmedhuda71

on windows95 machine did you share the folder which you want to access from win2K machine. You can share by right clicking on folder(or drive) and select sharing option.

by techiwoman

I had a similiar problem with one of my
clients and discovered it was his firewall.
I could ping the machines, but could not
access them.
I also got a similar message. Best of luck.
Techiwoman