| Title: | Server_works |
| Moderator: | PCBUOA::IS_SYSTEM |
| Created: | Fri Jun 30 1995 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 291 |
| Total number of notes: | 1063 |
Since I installed ServerWorks 2.0 and SWCC1.1b on my system,
Performance Monitor bails out with Computer Name not found on My Windows
NT 4.0 server. The missing name is the name of the system it self!
Performance Monitor still works with another Server here in my home
office and Performance Montior's Network browser sees the system SW is
installed on, but when I selct it from the browser I get Computer Name
not found! Same if I go to the other server and try to connect here.
Shares on this Network Name are working.
I have installed ServerWorks on my NTAS system as I do not have a
seperate workstation.
Is ther a particular problem associated with installing SW20 Management
on the same server that is being "managed".
This is just for exploring functionality...
FJP
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 230.1 | ServerWorks 2.2 not 2.0 | USPS::FPRUSS | Frank Pruss, 202-232-7347 | Wed Mar 19 1997 14:29 | 2 |
Sorry, make that ServerWorks 2.2
| |||||
| 230.2 | Domain Controller not up | PCBUOA::BRACKEN | Tue Mar 25 1997 08:08 | 23 | |
This is almost certainly *not* related to ServerWORKS. The fact that
he's not seeing any computers in the browse list can be from one of
several conditions:
not waiting long enough for the browser list to be created on his
NT
domain (the browse list can take a while to get created after a
machine
reboots)
the NT machine running ServerWORKS console has not been added to
the
browse list or has been explicitly deleted from the browse list
There could be other problems with the NT primary domain
controller.
If he's in a non-domain environment, we'd need more info to figure
out
what's happening. But I still think that it's not related to
SWORKS
2.2.
-George
| |||||
| 230.3 | Answer | USPS::FPRUSS | Frank Pruss, 202-232-7347 | Fri May 16 1997 20:24 | 7 |
It was a corrupt PERFC009.DAT. _NOT_ a Serverworks problem. The
source file for this was corrupt in the on-line kit I maintain to
support the frequent re-configs I usually do. Not sure how that
happened, but the "drive" is an NT Stripe set, and I've heard that
there can be bugs in that.
FJP
| |||||