Windows Forum

Ask something
Discussion Locked

ADMIN CHALLENGE?

0 helpful
9 replies

by xyzxyz1

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Need someone's [fresh] direction, PLEASE!! ...ASAP!

NETWORK: 1 WIN2000 Advanced Server; multiple combo's of WIN98, WIN2000 PC Workstations.

Installed a new WIN2000 [PRO] PC to run SQL & other Network services for us; ease the burden of our nowover-burdened ADVANCED SERVER, which we're going to eventually de-commission to put antother in its palce as soon as time/budget allow.
PC seems to run lke a champ (!.7Ghz Intel, 384MB RAM, 60GB, etc.), no problems to note otherwise, except...

NO ONE ON NETOWRK CAN GET TO ITS SERVICES - like HD, Printer, etc. That is, you can see them present in Explorer, but says "don't have permission to.." when you clik-on. Does that even to the WIN2000 Advanced Server.

The PC "itself" can see everything, get to everything fine, even Internet, but seeing "in" on it, the other Workstations can get to it.

CONFIG: This WIN2000 Pro PC is following the STANDARD setup for ALL OTHER WORKSTATIONS with TCP/IP, NetBeui, etc. services running.

From any Workstation: you can ping the problem PC; just can't get to any of its Services!!

We've tried everything we know with rights issues, over-prescirbing rights to be safe, etc. 1 Tech. here suggests it might be the brand NIC, another says something else, blah, blah, blah...; ALL seem to agree tom some extent that its a rights issue with it somehow, not a hardware issue. I personally don't know what to think any more!!! and I've been doing this work 16 YEARS!! Ready to scream, is what I'm ready to do!!

ANY HELP/SUGGESTIONS WITH THIS QUIRKY PC? ANY PRE-EXISTING ARTICLES U MIGHT HAVE TO "CHECKLIST" THE PROBLEM DOWN TO AN "INEVITABLE"?

THANKS IF U CAN HELP!

GUY!

9 replies

by joseph moore

Well, let's start with the easy question.
Did you add this new Win2K Server to the existing Windows domain, or is it a member of its own Workgroup? Or its own Domain?
What is your domain setup?

by rabbit_runner

It could be that the WIN2K PRO computer was put into a workgroup with the same name as the domain. This will allow the system to see and access the network. However, other systems, users, etc, are not able to access the Win2k Pro system because they do not have a LOCAL account on the computer.

In your question, you did not mention if you have Active Directory installed on your Advanced server. If you are in a workgroup setting, or the new system does not have a domain account, this will also bring about the permission's problems that you are experiencing.

Please note, that I am attempting to answer your question from the information you have given. If it is not correct, then please disregard.

Best of luck.

by timwalsh

More questions (in addition to those in Answer 1):

What other "network services" are you trying to run on this Win2K Pro computer?

You mention SQL. What version of SQL are you running? If you are running MS SQL Server, in any version other than Personal, it must be installed on a Win2K Server.

If you can ping the PC in question, and the PC can ping other PCs, then chances are very good that it isn't a NIC problem.

by jon pratt

This problem is almost certainly an issue with permissions. With windows 2000 you have three possible sources for network permissions - GP, ACLs, Domain/Workgroup authentication. If you're on a workgroup then that's your problem :|. If you're on a domain then your problem might lie in GP. Use the resource kit tool - gpresult.exe - to enumerate the policies being applied to the problem machine (There is a GP that restricts access from the network found at: Computer Configuration\Windows Settings\Security Settings\Local Policies\User Rights\"Access this computer from the network") The only remaining possibility for a permissions problem is ACLs and I would definitely expect someone who has worked in networking for 16 years to be able to pulverize any file/share ACL problem that confronted them. Hope this helps. Good Luck!

This discussion is closed to new replies.