Windows 2000 Server with a win 98 Network 1

[Guest_imported]

Being a newbie to this particular forum I hate to re ask a question you may feel has been answered but I am running into problems fairly similar to Spiceman Above. I am trialling Windows 2000 server for a small win 98 network. I am trying to do this using our local workgroup which allows me to see the server and indeed access outside comps from the server but whenever I try to access folders on the server I get a password required prompt for the /IPC$ folder. As you may have assumed I am not a network person, merely a web devver trying to get the office going. If anyone could help me in this VERY frustrating issue it would be most appreciated.

 

[SirLee]

I think you have to enable the guest account for shares to work.

 

[Guest_imported]

Hey buddy,
What your recieving is an administrative prompt as I understand it.

You will need to set up users on the WIN2k machine for all users who login to the WIN 98 machines. When they login to the win98 machines they will have access directly and uninhibitted to the WIN2k server.


for example


WIN98 machine 1 - user -> Joe
WIN98 machine 2 - user -> Nancy

WIN2K server - users group -> Joe and Nancy.

Go to the control panel and adminitrative components and click the users folder on the left pane and then right click in the right pane and choose new user and create the user accounts. By default all accounts will be set as basic users. Passwords don't have to match accross the network unless you otherwise specify.

Hope this helps.

 

[ShaithisDanoveur]

Correct. You are receiving this prompt because there is a username/password mismatch.

Nitch is correct - solving the problem requires that you set up usernames and passwords for the people who will be logging in.

You can also, if you'd like, change to a domain model, and have the Windows 98 boxes authenticate their shares from the windows 2000 server password database. This increases security considerably, centralizes user administration, allows for tracking of bad password attempts, etc. Also makes it so your users change 1 password, 1 time, that's it. No more passwords older than your credit card debt.

It also allows you to get rid of the insecure password cache files on those win98 boxes that any monkey with a copy of L0phtcrack could rip apart in a matter of seconds. And since all those boxes would have all users passwords...yup, that person would have everyone's password.

Of course, my favorites when I do security audits generally come from exec officers, who have a penchant for using either just a carriage return, or "12345" and "123456". The last batch I did a demo for spit coffee across the room when their "secure passwords" were nailed in about .08 seconds.