clients cannot access nt workstation 1

[paveway]

All the clients on my network (5 computers using TCP/IP workgroup settings) can see me NT machine but when they go to double click it in network neighbourhood, it waits for a while then it sometimes asks for a password or sometimes it just refuses the connection (cannot connect to \\mercury\ipc, something along those lines). I had NT running no problems about a year ago, now i forget how to set it up to work properly. I have an admin password set, but this does not seem to be the one that is asks for.<br>
Thanks for any help.

 

[Tool]

Users will not be able to access your NT system unless you add them with User Manager to your workstation. This is part of NT security. You'll find User Manager under Programs then Administrator's Tools.<br>
<br>
Hope this helps.

 

[mckarl]

Administritive tools common.<br>
then user manager. <br>
<br>
Here you may set the permissions user, administrator backup guy,, stuff like that. <br>
<br>
However, after you set up these (as Tool suggested) make sure that the OS's are the same, i know it sounds silly, but 95 os's can realy cause problems, not sure about the microsoft repair kits. (SP's)<br>
<br>
Karl.<br>
<br>

 

[paveway]

I have setup users and permissions etc but it still does not let me connect. The network is peer to peer with my machine the only NT one, the others all use Windows 98. They can all ping my machine etc, but when it comes down to actually connected via network neighbourhood when another user double clicks my computer icon it waits for a bit then it has a message on screen which says:<br>
"You must supply a password to make this connection:<br>
<br>
Resource: \\mercury\IPC$<br>
Password:<br>
<br>
(ok and cancel buttons)"<br>
<br>
I have tried setting up a password but it does not work, i have tried my sys admin password but it does not work.<br>
<br>
I used to run NT and with the other computers running Win95 it worked fine.

 

[mckarl]

ok, when you say Reasource: \\mercury\IPC$, i take it you are connecting through network neighborhood.<br>
<br>
the way it works is as follows. the 98 system connects to the NT system, and the NT system checks its database (SAM files) to check for the username mercury. <br>
<br>
If non are set up in the NT system, it will tell you... you cannot connect. if there is a connection available for that username, it will ask for you to supply a username.<br>
<br>
Now, the username you use to log into your userID on the 98 box, use it identicaly to log into the NT system.<br>
<br>
por example:<br>
<br>
<br>
log into the 98 box with username:bloggs01<br>
password:fred<br>
<br>
log then into the NT box using <br>
<br>
username:bloggs01<br>
password:fred<br>
<br>
<br>
i'm told that the userID on both machines have to be identical, as too do the passwords. I'm not too sure.<br>
<br>
--<br>
<br>
You must have the account of bloggs01 and password fred for this to work.<br>
(as shown in my previouse reply).<br>
<br>
Please reply, tell me if i have got the wrong idea.<br>
<br>
Karl.<br>

 

[databarn]

paveway, Karl,<br>
<br>
Working with NT is kinda new to me, but I though that IPC$ was a reserved system resource?? Not a service to which you could connect?? Correct me if that's wrong.

 

[paveway]

I have fixed the problem, when i added the other users with user manager i added the name of their computer, not their logon name, so now i have fixed it, and it works fine. BTW, databarn you are right in regards with the IPC$, any share name ending with a $ is inaccessible to any one remotely.

 

[Blotto99]

I believe the very last statement is incorrect. Any share name ending with a $ is NOT inaccessible to any one remotely. The $ makes the share hidden. If you know it exists, you can still connect to it.<br>
<br>
That is great way to share "confidential" material, that must be shared. No one, except for the people notified will even know the share exists and other users won't be tempted to try to hack into it.

 

[RoadRunner]

You guys are killing me <br>
<br>
By default, a Windows NT and 95 clients will browse a network resource [Using Network Neighborhood] only if the client belongs to the same workgroup or domain of the network host. The workgroup or domain name for the client computer should be the same as the workgroup or domain name of host to which it is connecting. <br>
<br>
The Windows NT workstation then needs to allow [grant share permissions] Windows 95 client users to access shared folders or such from the NT workstation. <br>
<br>
VISE VERSA within the Windows 95 clients they must check File and Print Shareing....<br>
<br>
You knew that..........right???

 

[networkcrash]

Hi. <br>
<br>
Do you have the Client for Microsoft Networking setup to logon to an NT Domain???<br>
<br>
This always makes life a little easier. LOL<br>

 

[RoadRunner]

One more note. Along with what Tool(MIS)said...<br>
<br>
The Username and Password of the Windows 95/98 clients<br>
must be added in the User Manager on the NT PC in order<br>
for the users to gain access to the NT Shares that are<br>
defined for that particular user account.