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.

This is page 2 of the discussion. Read the opening post

170 replies

by reddn

I have had the same problem. I am sorry to say but i have only read the first 21 threads of this board and some people dont know what they are talking about(and dont know how to read past threads). With that out of the way what I am going to say isn't going to help you. But I have a home network with about 3 clients, 1 server running Windows 2k Adv Server. My first installation of it, it would not let me access my Windows ME client. But as yall have said the ME client can access everythingelse. My windows server was giving the exact same error message, and I gave the logon name to that computer(the ME client) Full administrator access, nothing. I just got tired and used Netmeeting to get files from it. After finished my MCSE testsI thought it would be good to reinstall windows, to re-recongize my self with all of the options. After installation I got all of my clients back up and running the Win ME client could be access from the server. I really don't know what I did. But I tired everything. But like i said in the beginning, this won't help you because your company probably can't afford there server being down for reinstallation of the OS.

Tommy Sweeney
MSCE, A+
reddn@crosswinds.net

by ampl

Make sure that the latest service pack is installed on the Windows computers (both server and clients).

I have seen a similar issue before with NT and 3.11... I'd make sure that the NIC drivers are also up to date - primarily, make sure that the Win 2000 machines are using drivers designed for Windows 2000 and not 9x. You may also want to update the drivers for the NICs on the 9x clients also, just to be safe.

Another thing, manually add the names into the clients hosts and lmhost files for the servers. I have seen this issue with certain Samba share issues connecting to Linux systems.

See if you can find the server directly with Find -> Computer or by the IP address.

I'd have to research it a bit more, but I believe thatit could also be an encryption issue with the Domain name/passwords... Are any of the Win 2000 Servers acting as a PDC? If so, use the event viewer to make sure that the 95 machine is signing onto the domain correctly. I have encountered an issue where a few 95 machines weren't correctly talking with an NT PDC... in my case, it turned out to be an incompatible set of NICs.

by thetravman

I installed Wins and tried it but it never seemed to see anything. How do you setup a scope?
By the way one of the posts to my question finally got me access to the computer. I had to do a search for a computer and use the IP address as the keyword.
This leads me to believe it's a name resolution problem whereas before I was thinking it was a security or permissions issue.
Any thoughts?

by thetravman

I can't really take the server down just like you said but I received an interesting post. He suggested doing a search for computers but to use the IP address of the win95 client. Lo and Behold it let me right in.
I mapped the shares to My Computer on the stations we will more than likely need to access it from. I know this don't solve the original problem of what's actually goin' on but it got me access to the computer until I can figure it out.
Any ideas?

by thetravman

All of those are already done.
I got a post that didn't solve the problem but it helped me to gain access.
See the post from wmastokes@hotmail.com
Thanks for the ideas.

by thetravman

I don't have a firewall but thanks anyway.
See post by wmastokes@hotmail.com for something that has me heading in the right direction. His suggestion worked as far as getting access but doesn't quite solve the problem.

by larry rutherford

I didn't read all of these posts as I don't have 99 years left in my life. I did read the titles and noticed no one brought up Active Directory as the issue. I recently read an article about AD and problems implementing it unless all servers and clients on the network are W2K. Maybe that is your problem. Try disabling AD. If you have already tried this, my apologies. Good Luck

by rbilyk

Don't have a w2k server but had something similar with NT. Depending on which win95 you are running, check the version and datestamp of vserver.vxd. OSR1 and OSR2 have different versions of this file.
OSR1 should be version 4.00.954 dated 4/24/97 108,288 bytes and OSR2 should be version 4.00.1112 dated 7/24/97 112,904 bytes.

Got this from an old MS support article, ID Q169841.

May not be this specifically, but have a feeling that the win95 machines are where you should be looking.

Good luck.
roman@bilyk.com

by gomes

Make sure your Win2k servers and clients are configured to support SMBs using NetBIOS over TCP/IP. Win95/NT4 etc all use NetBIOS over TCP/IP to communicate.

Ivan Gomes.

by gomes

Make sure your Win2k servers and clients are configured to support SMBs using NetBIOS over TCP/IP. Win95/NT4 etc all use NetBIOS over TCP/IP to communicate.

Ivan Gomes.

by robert defazio

Depending on the number of workstations you are supporting, why not consider upgrading them to Windows 98/ME? Microsoft is dropping its support for Windows 95 (for good reason), so why should you continue to be a missionary furthering the cause of an OS that is about to become extinct in the eyes of the company that created it?

Windows 98/ME does not have these problems. If you insist on using Windows 95, identify all Windows 95 workstations where the problem does NOT exist. Determine theversion of Windows 95 running on those workstations, and make sure that all other workstations are using that same version. Also, be sure to apply all the applicable service packs for that version. (See below)

Finally, make sure that the sameprotocols are installed on all machines. If you are relying on the use of NetBEUI, make sure you have a WINS server set up on the network. If you are using TCP/IP, make sure everyone is on the same subnet, and make sure everyone has the same Winsock and vredir.vxd versions.

As a starting point, I would direct you to http://msdn.microsoft.com. Click the search tab, and enter Q132736 in the box. It will bring up a document that is a jumping off point for Windows 95 network issues. Then, go to http://www.microsoft.com/downloads and get all the downloads for your OS. There are 240 possible downloads, so be prepared to do some work in sifting out the ones you need from the ones you don?t. Moreover, when you download, be sure the download applies to your version of Windows 95.

The key is standardization of hardware/software configurations. I'm just a company president, but I know enough that no one wants to start out to be wrong. If it is at all possible, upgrade. If you can?t, you will have to support a system that was written when Active Directory Services had not yet even been conceived.

by thetravman

We have to use the 95 machines because the program we use won't run on anything else (tested on winMe and Win2000).
We plan on getting away from this program in a few months but can't at the moment.
Incidentally, I had the same network issue with WinMe as I'm having with 95 so it's not really a 95 problem. Just can't find where the problem is.
Thanks for the input though.

by jmc4

I'm not positive as I've not been on a 95 machine in a while. But, in addition to the domain that you can add to a 95 wkstn, there is ALSO another option that allows you to set a Windows 95 group membership whereby machines outside the group cannotsee in. This is set up somewhere in the client network properties. Sorry I can't be more specific but again, it's been a while for me on 95.

Jon

by clacy

I have had a similar problem at my company.

I ended up adding user accounts to the win2000 server for the win92 clients and it seemed to fix the problem.

by geosean

The MS KBase describes a couple of different situations that sound VERY much like this.
Go hit http://search.support.microsoft.com and then request the following articles:

Domain Browsing with TCP/IP and LMHOSTS Files Article ID: Q150800

"Access Denied" Accessing Windows 95 Share from Windows NT 4.0 Article ID: Q169841

Good luck...

by thetravman

Wow. It's getting time consuming reading all of the posts and trying all of these things but eventually somebody's gonna get it.
Thanks for the suggestion.

by ezmoney

trav, similar problem here 98 machines lease address from dhcp, but then will not logon nor can you ping anything. Solution was to set dhcp lease to 0 days and force all machines to renew lease. The mess just keeps piling up when you mix w2k with legacy systems.
I have one subnet using w2k for nat / and nt4 bdc that some 98 machines wont browse but others work fine with the same setting (go figure). I think it's a personal plot by the big G man to drive us all a little crazy. And it's working to.

by thetravman

What's weird is I can ping by name and address and it finds the computer.
I can browse in network neighborhood and it sees the computer.
I can try to access it from the network neighborhood or net use and get the same access denied error.
Thanks for the suggestions.

by thetravman

If you're talking about tracert then I did that. When I did it by name it gave me the IP address instantly. When I gave it the IP address it returned the name instantly.
Same thing that ping does because it's not routing through anything. Least I don't think it is. Should it be?
Thanks.

by kelly.ecklund

Have you installed DS client. Directory Service Client software for Windows 9x.
You'll find this add-on in any of the Windows 2000 server installation CD-ROMs in the \Clients\Win9x folder. Double-click on the DSCLIENT.EXE file to start the setup program. It's a fairly quick and simple setup program, guided by a wizard. Once you have the Directory Service Client installed, your domain logon is validated through Kerberos authentication. You can also search the AD for published printers.

by swetbak

Try installing WinSock 2.0 Installer for Win95. Q184242 on Microsoft.
Good luck.

by danayen

first w2k has change TCP/IP stack and is causing problem with network connections even in win98 I need to know your verison of 95 and TCP/IP version as well as winsock.dll
Dan A. Ayen The KIndness Company L.L.C.
danayen@voyager.net I will do my best to help
Dan A. Ayen

by johnnyextreme

Check your computer policy / security options for LAN Manager Authentication Level on the Win2K server or the individual 2000 machines. Win95 and pre-sp3 NT clients cannot authenticate using NTLM or NTLMv2, so this option should be set to "Send LM & NTLM responses"

by danayen

Did not work computer would see any workgroup no mater what the name so that and some virsion of 98 first edition were the same 98SE amd w2k won't that why I ask for version I have A 95 MACHINE LEFT OVER SO i WILL HOOK IT UP TO MY NETWORK AND PUT INW2K ON ANOTHER MACHINE AND SEE IF i GET THE SAME THING WISH ME LUCK
Dan A. Ayen

by cail

Make sure they all have the same workgroup name and have enable file sharing if files need to be access. Also make sure the Netbui protocol is installed

by dbade

If you have an extra PC around, try it anyway. I have been told that before and only on a very rare occasion was the company correct. Unless it is very picky about video drivers, it will probabley work. I had only win95 and Dos programs running under NT4 Workstation. It just took a little fiddling around.

Good luck anyway.

by lkrause

I remember back in the day of hybrid networks, we had 2 dell laptops that would see NT mahcines but not vice-versa, i think all it took was this:
goto network properties then
edit the microsoft network client
then make sure that browse master isdisabled because this caused conflict on our NT domain with the polling the 95 machines acted like browse master when a PDC should win all polls, so try this and it may need to learn the network, but be sure all 95 machines have this changed. Let meknow what happens
-lucas krause

by jagcon

What version of 95 are you running ? If not release b it might be centered around incompatable fat systems? Just a thought

Jag
jagcon@earthlink.net

by chaosad

question ?
how are your hard disks formated and under what fat table are they formated for ?
have you tried reformating the 95 clients
using large disk support !
if you find your solution to this problem please let me know !

by thetravman

I can get into the computer by going to
Start/Search for computers and entering the IP address instead of the name of the computer. This hasn't solved the problem as far as browsing but I know I can get into the 95 machines and read from the drives.
Thanks anyway.

by blue_ice_4u

The lkast time i worked on a win2000 server and had win95 client workstation, the only way i was able to get the win95 to be seen was to place the win95 machines on first, and then the rest of the network and then it was able to see them. for some reason win2000 will look at win2000 workstations only, but if you place the win95 online first then it should work..

by shirley28

It seems to me that Win95 is upward compatiable and that is why it can recognize the W2KSVR. I also believe that the software W2KSVR is not downward compatiable and it will not recognize previous versions. I hope this helps somewhat!!

by tatsnice

When you have dhcp running on your server combined with a scope.

On the win98 machine have it log into the same domain as the server.
Do not assign an address .. Set to get automatically from dhcp server.

Your scope will assign an address that is not being used according to the scope setting you have on the server.

If you want your 98 machines files or printers to be visible make sure file and printer sharing is enabled.

To make the computer totally visible to the network , sharea folder assign a password with the appropriate rights. Whether it be read or write access.

On the server create a username with the same password as the shared folder on the 98 machine.

use that username to see if it is working.

by gonzg

I believe the problem might be with the user accounts you are logging on to the W95 STATIONS. For example, user A1 within the usermanager probably has rights to log on to probably that computer and no other. You probably need to either unrestrictthat user within user manager or key in the computer name of the Window 2000 machines

by paddle

On the 95 machines, do you have Browse Master disabled? I've had a similar problem on an NT network when that feature is enabled. Apparently the NT server and the 95 workstation fight over who is the Browse Master and the 95 machines give up.

Ihaven't read all the responses so you may have already tried this.

HTH

by nicholas mackintosh

We have the simaler problem,we battle to access our Win98 workstations from our 2K servers.The servers can see the client but often when connecting over the network they browse for a few minutes before you can connect to the workstation.I have foundthat typing in the path to that workstation and the shared folder makes it a lot faster.

by earthquake

When you setup the W2K server, did you set Active Directory to Mixed mode, or native? Documentation states that an NT 4.0 server cannot participate in Native Active Directory, only mixed mode. So my assumption would be that neither would win9x OS's.The entire issue seems to me to involve the master browser/browser - not compatible - thus no older style browser would not work! By the way, if you set native mode, you cannot reverse it. Let me know how it goes, that is if you have time?

by stuckinthemiddleagain

I have found that clients that get stuck in the file-sharing game, always lack one or two settings in the tcp/ip stack bound to the network adapter. Make sure you have a host and domain entry even if they are nonsense. As long as you have that, and the ip address entered for your server that has a running Wins database, it should work.
I also remembering having to run some dippy win95 patch for tcp/ip at one time or another.
You will also want to try the following fom the client to the server:
At the dosprompt type:
route add X.X.X.X (client's ip) X.X.X.X (server)

-Then ping the server. Sometimes the routing table can get screwed up.

I think the host and domain entries are the key.

Good luck,
Earl

by talden

I know this may seem obvious, but have you checked your settings in Client for Microsoft Networks to make sure that SAP (Service Advertising Protocol) is Enabled on your 95 clients? If not, they will be able to see all of the other machines, but only the 95 machines might be able to see the other 95 machines. Sound familiar?

by velasco53

Are you using same format? such is FAT win95/98 and W2k FAT or Win95 with FAT and W2k with NTFS. If you are using diferent formats that might be the main reason.

second you have to use same communication protocols.

remember compatibility of formats is only valid among clients.
servers can be either NTFS OR FAT.
FAT MACHINES CAN NOT ACCESS NTFS, BUT NTFS CAN ACCESS FAT.

by thetravman

As suggested in an earlier post I can go to
Start/Search for Computers and enter the IP address of the 95 machines and read from them just fine so I know I can read the files on the offending machines. I just can't browse network neighborhood and get access to them.
Thanks anyway.

by hakkinen

I had the same problem with my network.
I have installed Linux Red Hat on the server
and all the computers are fine now, no matter what version of Windows I use !
Linux Red Hat is distributed for free !

by lanman52

I agree. This posting shouldn't be here. If we are going to fill the postings with useless suggestions then why bother. The whole argument that Linix is a more stable, faster enviroment is crap. Mabey you switched to Linix so no one at your work cantell you don't know what you are doing.

by chaosad

Throwing the thing about linux in here has nothing to do with the issue at hand ! My self am interested in the travmans problem and would like to LEARN FROM IT AND ABOUT IT NOT CHANGE SEATS ON THE TITANIC ! SO PLEASE GET FOCUSED AND HELP THE COMMUNITY OUT !

by jcgarciaplua

You are right, the Linux is free and very good, but you change your network, that required capacited the human resources and others costs.

by thetravman

We already tried to get the program to run on Win Me and Win 2000 with no success. Tried everything in the settings to get it to run but no go.
It's setting up some kind of funky screen when it goes into the main part of the program and this is where it always messes up.
It also uses a dongle which doesn't like anything but 95.
Thanks anyway.

by thetravman

No it's not obvious since I don't even remember seeing it before, so I'll look for it.
Thanks.

by claymuir

I am sorry I can't give you the correct answer right now but I know what is wrong. The new Active directory has to be installed so that it has a "tree" for the old systems. I have a sybex book that explains the problem and how to resovle it. My suggestion is this - either get that book or try MS technet. The problem is documented in both.

by gicu artistu'

W2k & W95
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 berx

Of course I agree, there is NO PLACE for that comment in this discussion!!

by rschmid1

Sorry I did mean Netbeui!!

Dyslexic fingers I guess!!!

Thanks for the clarification

by brogers

Okay. Here's what I did:

I downgraded the server using the "dcpromo" command and then reinstalled Active Directory. (I wanted a fresh start.) Once it was finished, I added the Windows 98 machine ("Melchizidek"). Within that same "Computers" folder, I added the user "Benjamin". After the user was added, I went in and edited the profile for "Benjamin" indicating the base logon was "\\Melchizidek\Benjamin".

Then I reset the Windows 98 computer, and logged Benjamin into the network--and it worked like a charm!

However, my other machine still refuses to connect to the server/network at all. I removed its NIC from Network Properties and reinstalled/reconfigured and it still didn't connect (although the symptom of double booting is gone, now--though I have to wonder if it was trying to network boot...).

I suspect there is a problem with the driver, installation or even physically ailing with the NIC. However, it's built into the motherboard and will be a pain to deal with if that's the case.

But, I thought you should all know how I was able to get the Win98 machine to see the network/logon to the Windows 2000 Server.

Thank you for all your help! Now that one of them is working, it's just a matter of time/trial-and-error/sweat to get the 2nd machine up and running...

...and then it's time for running network Half-Life!

Benjamin

by wegerc

First and foremost.. You dont have to add the computer to ADS..
Obviously, you have ADS installed if it was mentioned.. am I correct? if so, check the Client for Microsoft Networking properties and make sure the domain name is there.. then on the last tab, of the network properties (forgot the name of the tab, security or something), and check off the user permissions and select NT Domain.. My wording may not be exactly accurate as far as what the screen may actually say, im at an NT workstation right now.
This will enable the domain permissions to the computer and it will join the domain. 95/98 clients dont need to be added to the domain.
Hope this helps.
Chris Weger
MCSE, CCA

by johnnyextreme

When you attempt to connect to a share on a Windows 95 based computer from a Windows NT 4.0 workstation or server or Windows 2000, the connection attempt may not succeed and you may receive an Access Denied error message if the following conditions exist:
1. Windows 95 peer server has user-level security enabled (instead of share-level security), and the security provider is a Windows NT domain. 2. You are attempting to connect using a UNC name ( \\ servername\sharename ) instead of mapping adrive letter to the share. 3. The Windows NT 4.0 workstation or server has Service Pack 2 or Service Pack 3 installed. This behavior can also occur with Windows 98-based computers connecting to Windows 95 based computers, and from Win95 with the DFSclient installed talking to Win95. This problem is caused by an interoperability problem between Windows NT 4.0 SP2 or SP3 and Windows 95. Windows NT 4.0 with SP2 or SP3 makes a connection using a null user name, which Windows 95 acting as a server does not handle correctly. You can resolve by using drive letter mapping or update the problem executable on Win95 peer server. For Win95 and OSR1 acting as server by updating VSERVER.VXD with : VSERVER.VXD version 4.00.954 dated 4/24/97 108,288 bytes. For Win95 OSR2 and OSR 2.x, you need: VSERVER.VXD version 4.00.1112 dated 7/24/97 112,904 bytes

by cactus pete

I was doing some other research and came accross this:

Win95 and OSR1 acting as server by updating VSERVER.VXD with :

VSERVER.VXD version 4.00.954 dated 4/24/97 108,288 bytes

For Win95 OSR2 and OSR 2.x, you need:

VSERVER.VXD version 4.00.1112 dated 7/24/97 112,904 bytes

by mmarcus

Microsoft has several Knowledgebase entries that appear related. My company is currently using static IP and DHCP is not the problem. It does appear to be a security issue and Microsoft is aware.

See:
Q278558
Q138365
Q2772594

The answer for these is to call Microsoft for support (cannot find download for the Vredir.vxd files (Win98, Win98SE, WinME).

So far the PCs these are occuring on appear to be OEM versions of Windows. Note that this is not occuring with the Windows 2K Pro Clients.

This discussion is closed to new replies.