W98 cant access w2k machine

[introuble]

AAARRRRGGGGG!!!!!

I cant access any 2k machines on my network from w98. I get an error message that says \\name is not accessable. This device does not exist on the network. Now this 2k machine is on my desk right next to a 98 laptop that I'm working on. I can access the 2k machine from a 95 machine. On both 9x machines, the 2k machine appears in net hood, but when I click on it on the 98 machine, I get the error.

I can ping the 2k machine from the 98 machine and visa versa so the physical connection is there.

This used to work. Something, somewhere on the network changed; but I haven't made any INTENTIONAL changes....:)

Any ideas are greatly appreciated espcially since my backup machine is 98 and cant see the 2k :(

Thanks in advance
Steve

[YeOldeStonecat]

Make sure the logon is Client for Microsoft Networks on your Win9X's Network Properties.

NetBEUI installed on all machines? Or TCP/IP alone? Is TCP/IP manually assigned, or pull DHCP from a router or something?

[introuble]

Yup, I'm using Client for Microsoft Networks as the login on 98.

Yup, NetBEUI is installed on both machines (98 and 2k).

Im dolling out IP addresses via DHCP on another computer (not one of the two in question here.)

[cyberskye]

Which protocol is bound to fileNprint sharing? If netbeui, are the workgroups the same. If tcp/ip, do you have an account on the w98 box that has access to anything on the W2K box?

Skye

[introuble]

I dont see how to check the protocol bound to filenprint sharing. In 2k, there are no options for that and on the 98 machine, I dont see anywhere that lists the bound protocols for that.

Additional info....95 machine can fully access all shares on 98 and visa versa. Other than not being able to get to 2k box, the 98 box is working fine. It can get to all other machines on the network.

[cyberskye]

That's not the problem (since you can access shares on 98 from 95). FYI - you want to check the tcp/ip protocols properties to set your bindings.

Is the user you are logging into the w98 box a valid user on the W2K machine?

[introuble]

Hmmm valid user......

I have the guest acct enabled on the 2k machine...wouldn't that allow anyone access? Remember, I'm not getting an access denied message, the error is telling me that the 2k box is not available....am I putting too much faith in the error message? Is not avaiable different than not having access?

I'm logged in as myself on both 95, and 98. 95 can get to the 2k box, 98 cant so I dont think its a user issue. The 2k box is in the middle of the laptop on my left running 98 and another desktop on the right running 95. I'm almost positive this worked at one time, because I've only recently started to get errors from the backup software (running on a 98 machine) telling me the 2k box isn't accessable.

[hoov]

Cyber is correct. You need to have an account on the Win2K box for the username that you are logging in with on your 98 Machine. Also permissions for that user need to be given for each resource that you want shared on the 2K box.

[Kip Patterson]

See the Microsoft KB. There's an article or two on the subject.

[YeOldeStonecat]

What they're talking about is NT based computers (which Win2K and XP both are, Windows NT) need a user account for the computers that need to share it. For example, on the Win2K box, you probably log on as Administrator with some password. If you setup auto-logon when you first set it up, you still did so. On the Win9X boxes, you log onto the network with some username and password.

What you need to do, is on the Win2K box, add a user account that you will log onto the Win9X box with...say for the sake of arguement....username will be computer2, and the password will be password. One of the places to manage your users is to right click my computer, select manage...which opens up the management console. You'll see users....create a new one.

Now share out any printer/folders that you need to get access to on the Win9X box. Next...on the Win9X box, log off...log on...and use computer2 and password and confirm password one more time for Windows...which creates your .pwl file. Now you should be all set.

[introuble]

WAHOOO!!!! It worked!!

I created a new user on the 2k machine to match the username and password on the 98 box and now I can access the share from the 98 machine.

Thanks for all the help!

Steve

[The Dude]

Originally posted by introuble
I dont see how to check the protocol bound to filenprint sharing. In 2k, there are no options for that and on the 98 machine, I dont see anywhere that lists the bound protocols for that.

Additional info....95 machine can fully access all shares on 98 and visa versa. Other than not being able to get to 2k box, the 98 box is working fine. It can get to all other machines on the network.

In 2k open the "Network and Dial-up Connections" window and click the advanced "tool-bar", then advanced settings. In the lower pan remove the checkmarks next to both the TCP/IP entries, leaving only Netbeui checked under "Client for Microsoft Networks" and "File and Print Sharing".

Don't remember how to do it in 98. I think you just right click on the File and print Sharing and select properties. Then uncheck TCP/IP.

[charlyh]

Hi.
Question along these same lines...
THere seems to be some contraversy on whether to use tcp/ip vs. netbui for file/print sharing. I have a simple peer to peer winME and win2k and a dsl connection thru a router. I would appreciate you opinions on the best way to go.

Thanks
charly

[The Dude]

Originally posted by charlyh
Hi.
Question along these same lines...
THere seems to be some contraversy on whether to use tcp/ip vs. netbui for file/print sharing. I have a simple peer to peer winME and win2k and a dsl connection thru a router. I would appreciate you opinions on the best way to go.

Thanks
charly
I also have a simple network, one 2k PC and one win 98 PC connected to a cable modem through a router.
I bind File And Print Sharing to Netbeui because it is not a INTERNET protocol. It can't go to the wan side of your router, only the LAN side. It gives you extra protection from hackers because they can't access your shares with TCP/IP.

You can use TCP/IP just make sure you restrict access to the shares. Only allow access to the local accounts on your PC's. I used Netbeui because I felt it added extra security.

[koldchillah]

The Dude's right charlye. Also Netbeui is faster on the LAN side..

[charlyh]

THanks for clearing that up!
I added netbeui to both boxes and unchecked file/print from tcp/ip. It's all working fine now.

[introuble]

Oh, my joy was short lived....

I posted that all was well after creating the user acct on the 2k machine.....and it was; until the other day.

My tape backup is 9x and the log told me it couldn't access the 2k machine. Thats how I knew there was a problem in the first place. So after I got it working with the user acct, the back up was sucessful. 2 days later, the backup failed because it couldn't get to the 2k machine - again. Now the particular 2k machine is used by someone who is on vacation, so nothing there changed and the tape backup machine is dedicated and off in a corner somewhere, so nothing changed there.

So what could have changed? AAARRRRGGGG

Background....None of the computers on my network (about 23 of 'em) are running server software. (NT workstation, 2k Pro, 9x). Everyone is in one workgroup. The two machines in question have tcp/ip and netebui installed.

Thanks,
Steve

[cyberskye]

Are the shares on the backup client mapped back to the tape machine (and set to mount at boot)? Without doing so I don't think there would be a connection by default.

When you say you got it working with the user account do you mean that you had to supply username/password to access the W2K box?