Networking NT4 to Win95

Patrick

I've got a few NT4 pcs ona network and I'm trying to add a win95 machine. (TCP/IP). The NT4 machines see a computer in network neighbour hood which an unknown name. The win95 machine can see the NT4 machines and get files marked as sharing off them but the NT machines can't access the win95 machine.

Anyone know what's up?

seamus

They will have trouble communicating because NT and Win9x use different file systems. NT uses NTFS and Win9x uses FAT32. Most Individual files are usually interchangeable but, the Folders and things can cause hassle. As for the the win95 machine being unknown, I think it's only a matter of giving it a network name, and IP( if you're not using DHCP) Check out the TCP/IP Properties from your network icon in the control panel(on the win95), and you should be able to configure everything in there. Not all reliable info from me though

---

When I was young, I dreamed of being a Fireman. Then I learned that they put out the fires.

[This message has been edited by seamus (edited 23-08-2001).]

phaxx

The bit about the filesystems there, seamus, that's wrong. My linux box runs samba, and any of my windows machines (9x, nt, whatever) can access files on it, so the filesystem doesn't matter.

Yup, give it a name. Other than that I dunno. if one can see the other, the reverse should be true...

It could be something to do with the passwords... I believe 95 uses plain text smb passwords, and anything later uses encrypted? Not sure on that point, but it seems the most likely cause.

Patrick

I've already given the win95 machine a name and ip.
Anyone every get it working without install a patch or whatever?

Gavin

Aye, 95 and NT will work together fine.

When you say an unknown name.. what exactly do you mean ?

I presume you can ping it etc, if it's showing up in network neighbourhood. Try accessing it via it's ip ie, \\192.168.100.20 or whatever.

Sometimes tcp/ip and microsoft client can get screwed in a win95 install. Maybe try reinstall them. Is file and printer sharing enabled on the 95 box ?

( i assume you haven't given it an dns name as a pose to a network client name ? )

As for the files part, aye that's incorrect. The base file system is irrelevant, as the actual files are shared via a common smb protocol as phaxx says.

Gav

_CreeD_

Make sure the computer/share names are no longer than 11 characters (Win9x and NT networking is based on dated Lan-Manager technology and still have some dodgy 8.3 limitations floating around in there)
Make sure each is a member of the same workgroup.
Reinstall File&Printer sharing on the 9x machine.
Edit your LMHOSTS.SAM file on each machine to have the name and IP of each other machine (Unless you're using a WINS/DNS server in there somewhere).
Double click the FILE & PRINTER SHARING service (ie. the listing in the main white box, not the large button below) and change the BrowseMaster options, try disabled first.

Xterminator

Going back to what creed is saying, make sure file and print sharing have been added. If os remove and add again.

I assume you are using a workgroup, not a domain? Ensure the name of the 95pc is correct, in network neighbourhood properties, and that the workgroup name is correct. Go into properties for microsoft client, and check the settings are correct here too.

Also create a share resource on the win95 machine.

If all else fails, add netbeui to the machines too.

x

---

"Man, you go through life, you try to be nice to people, you struggle against the urge to punch ‘em in the face, and for what?! For some pimply little puke to treat you like dirt unless you're on a team. Well I'm better than dirt ... well most kinds of dirt. I mean, not that fancy, store-bought dirt. That stuff’s loaded with nutrients. I …I can't compete with that stuff."
-Moe Szyslak

[This message has been edited by Xterminator (edited 24-08-2001).]

[This message has been edited by Xterminator (edited 24-08-2001).]

WhiteWashMan

try connecting using the run command.
win9x sometimes doesnt like showing up in network neighbourhood for some reason.
anyone know why?

Patrick

I tried accessing it via ip but it says it doesn't exist even tho the 95 machine can see the rest. I've reinstalled everything in the network icon the 95 machine about 3 times. The NT machines have netbeui in there as well and an ip address so I did the same for the 95 machine but still the same result. The 95 machine is called 'accounts' and I *also* gave it a dns name of 'accounts' since that's the way the others are setup. I did not setup the rest of the network, I'm just adding the 95 to it.
The NT machine can ping the 95 one. At home I have NT5(win2k) and 98se networked, no probs, I can always see the other pc in the network neighboorhood.
If I have no other option I might upgrade the 95 machine to 98se and see if it makes a difference..

[This message has been edited by Patrick (edited 24-08-2001).]

[This message has been edited by Patrick (edited 24-08-2001).]

The Cigarette Smoking Man

You'll have to log on to the Win95 PC with a user name and password from your NT machines using the Client for Microsoft Networks. Have a look at this:

http://www.helmig.com/j_helmig/w2kwin9x.htm

It's 2000 and 95 but it's similar for NT4.

_CreeD_

Far from an expert on DNS as I am, surely DNS names (aswell as the computername, sorry but that bit about 'same as the others' has me wondering) have to be unique?

You still haven't mentioned if you disabled Browsemaster or what share names you have setup on the 95 machine.

[This message has been edited by _CreeD_ (edited 25-08-2001).]

Hobbes

If you can see it by IP and not machine name, add the name to your LMHOSTS file and try again. You should at the very least be able to ping the machine.

Also Win9x doesn't like Domains (at least I've had problems with it), so add it to a workgroup with the same name as the domain.

Try WWMans idea of typing in the Run command box "\\machine\share" to see if that connects.

Make sure you have a guest login setup, file/print sharing set up and switched on.

Seamus is right, FAT32 may cause problems as well.

The way I got around this problem was I set up a generic share area for everyone on an NT server. If they wanted to share something out they dumped it there rather then on thier machine.

Patrick

Have already done that. The win95 machine can access files from the NT machine but the NT one can't see the 95 machine

Gavin

<font face="Verdana, Arial" size="2">Originally posted by Hobbes:

Seamus is right, FAT32 may cause problems as well.
</font>

How ? I could understand NTFS posing problems with underlying permissions perhaps, but fat32 ?

Gav

Patrick

<font face="Verdana, Arial" size="2">aswell as the computername, sorry but that bit about 'same as the others' has me wondering) have to be unique?</font>

The name is unique.

<font face="Verdana, Arial" size="2">You still haven't mentioned if you disabled Browsemaster or what share names you have setup on the 95 machine.</font>

I'm not familier with browsemaster settings but I'll try disabling it as said.
I have "C" setup as a share on the 95 machine.

<font face="Verdana, Arial" size="2">If you can see it by IP and not machine name, add the name to your LMHOSTS file and try again. You should at the very least be able to ping the machine.
Also Win9x doesn't like Domains (at least I've had problems with it), so add it to a workgroup with the same name as the domain.</font>

Yes I can ping it and I don't use domains. All pcs are in a workgroup called "WORKGROUP". I'll try adding the box to my LMHOSTS file.

<font face="Verdana, Arial" size="2">Try WWMans idea of typing in the Run command box "\\machine\share" to see if that connects</font>

tried that.. "\\10.6.36.72\c" but it said the machine doesn't exit even though it can ping it


[This message has been edited by Patrick (edited 27-08-2001).]

WhiteWashMan

hmmm, sounds as if you may have a problem with your wins (or is it dns, i can never remember)
which ever resolves your ip addresses to computer names. has something to do twith the master browser if i remember correctly.
which is absolutely no help to you at all, but there you go.
of course, you would only have one of thoise if you were in a domain, so i have no iddea what your problem is.
did you try from a run box
\\computername\c
?

Gavin

<font face="Verdana, Arial" size="2">Originally posted by WhiteWashMan:
hmmm, sounds as if you may have a problem with your wins (or is it dns, i can never remember)
which ever resolves your ip addresses to computer names. has something to do twith the master browser if i remember correctly.
which is absolutely no help to you at all, but there you go.
of course, you would only have one of thoise if you were in a domain, so i have no iddea what your problem is.
did you try from a run box
\\computername\c
?</font>

Nah, you can use Wins outside of domains too, but there aint much point using it unless you have a big lan or have a wan/vpn.

Is NetBios over tcp/ip enabled on 95 machine ? Just throwing out anything here. I'd go for a complete reinstall of networking on the 95 machine though. Remove net card, all drivers, reboot and reinstall from the cd, not from windows\system32.

But as above, I don't have a clue what the problem is.

Gav

<edit>

Sorry, I just saw that you have reinstalled already a few times. Just to make sure that the files are coming from the CD, not what is already on the computer.

Also, perhaps try to stick the accounts machine into a new workgroup and see if that show up in network neighbourhood, when the NT machines are browsing.

</edit>



[This message has been edited by Verb (edited 28-08-2001).]

WhiteWashMan

i presume you are logging in with client for microsoft networks.
although to be honest whenever ive been using win95 to connect to anNT domain i havent really had to do much.
just put in same workgroup, make sure tcp/ip and netbios is installed. ipx if using netware. and make sure your share is for everyone. apart from that, there must be some major balls up somewhere
apart from that just make sure you get an ip address automatically and that you are using dhcp (i preume you are using dhcp?)
you lost me ?!
as verb said, uninstall you netwok card and reboot and er...i dont know!