Can't access shared folder under NT Server

[Rudee]

With help from fellow forum members here - especially celeritas (thanks man) - I managed to resolve a earlier problem this week with a different PC. Now we have another problem with another computer on the network. Sorry, company doesn't have a IT dept. 🙁



The problem...

Networked PC is running Win98. NT4 Server was just installed to "dual boot" with Win98. This PC is only a test PC, it is not meant to be used as a real server, but just to test software that the company designs for NT4 Server. NT4 Server is running as a "Stand alone" server. Not a PDC nor a BDC. frankly, it's not even going to be a real server. NT4 Server was just installed for testing software.

When I dual boot to Win98 and go to Network Neighborhood, I can see all the other PC's connected to the LAN. I can also access their shared resources and they can access mine. But when I dual boot switching to NT4 Server, things change a bit. I can access the other PC's via Network Neighborhood no problem, but when a user tries to access my machine the computer freezes for a few seconds then it responds with a message asking for a password to connect to my machine. The thing is, I don't have any passwords assigned. All passwords are blank and I'm running the default permissions.

Like I said, this dual boot with NT Server was set up for testing only, no scopes or permissions were assigned. Just defaults. I don't quite know how to let others access my machine like they can when I am in Win98. This is not going to be used as a real server, so I would like to know if anyone has any ideas how to easily resolve this without resorting to complicated permissions and group setups? It's kind of a pain in the butt having to logoff and log back into Win98 just to let others access my machine from the network.

Thanks in advance. 🙂

 

[mrbios]

Well, this may not help your situtation, but the same thing happened to me before. If I remember correctly, when they try to connect to the NT box, it asks for a password for "$IPC". Now, what the hell that is, I don't know, but in NT Workstation, it'll connect no problem. However, when I re-setup my NT4 Server as a PDC, and set the Domain it controlled to something other than the workgroup name, it would connect no problem. Now, whether changing to a PDC helped, or the changing of the Domain (or in your case, workgroup) helped, I'm not sure. The quickest way would try change the Workgroup it is in. If that works, good. If not, wait for a better NT guy to help you out.

Russell "Mr.Bios" Sampson

 

[jsm]

There is a really easy fix.

Enable guest account.

Enable full access on share level permissions.

Change the specific permissions on the NTFS permissions to whatever you desire for each specific folder, file, etc.

That should work.

 

[Cable God]

If you're running a NT Domain, with NTFS permissions on the shared space, in addition to assigning NTFS permissions, you need to assign LOCAL permissions under the security tab. I know it goes against the grain, but it had to be done here for users to access their personal folders stored on the server.