Welcome Serena Central users! CLICK HERE
The migration of the Serena Central community is currently underway. Be sure to read THIS MESSAGE to get your new login set up to access your account.
scum1 Absent Member.
Absent Member.
1483 views

Server Status Unavailable

hey all,

going nuts here...

have just built a new ZAM v7.5 server for our enterprise environment.
when i watch the ZAM Management Console on the Primary server, the new
server's "Server Status" shows as unavaiable, (both under Collection and
Task)
when i stop the services on the new server, and restart them, the ZAM
management Console shows both the Collection and Task servers as "started"
for ~2 seconds, then return to the unavailable status.

any ideas on what may be going on???

cheers
--
------------------
Leon Hewitt
l.hewitt@@curtin.edu.au
0 Likes
2 Replies
Highlighted
scum1 Absent Member.
Absent Member.

Re: Server Status Unavailable

Ok all, problem sorted....
kinda...

having no luck with my secondary zam server, i started to make the server as
similar to our ZAM Primary server.

being slack and cheap i decided to build the 2nd server on windows XP, with
the novell client and ZDM Agent installed.

first up i decided to uninstall the novell client, (keeping the ZDM Agent
for remote control purposes)...

once rebooted, the 2nd servers Task and Collections Services stayed up.
not 100% sure why, but possibly something to do with filestore rights or
something...

this maybe useless to most, but though i would post it in case someone else
had the bright idea of ding what i did, 😉

background info:
Primary ZAM server's FILESTORE is located on a seperate Netware File Server,
(running CIFS)
local ZAM admin accounts are created on the 2nd Servers which match those of
eDir accounts.
eDir accounts have full rights to the FILESTORE
local ZAM Admin accounts are used to launch the Task and Collection
services.
possibly problem with the Novell client being installed, could be the
machine trying to authenticate to the FILESTORE via a Novell connection,
rather than using the a Microsoft connection to the CIFS.

just a thought.


Leon Hewitt wrote:

> hey all,
>
> going nuts here...
>
> have just built a new ZAM v7.5 server for our enterprise environment.
> when i watch the ZAM Management Console on the Primary server, the new
> server's "Server Status" shows as unavaiable, (both under Collection and
> Task)
> when i stop the services on the new server, and restart them, the ZAM
> management Console shows both the Collection and Task servers as "started"
> for ~2 seconds, then return to the unavailable status.
>
> any ideas on what may be going on???
>
> cheers


--
------------------
Leon Hewitt
l.hewitt@@curtin.edu.au
0 Likes
jaredljennings Absent Member.
Absent Member.

Re: Server Status Unavailable

Leon Hewitt,

>possibly problem with the Novell client being installed, could be the
>machine trying to authenticate to the FILESTORE via a Novell connection,
>rather than using the a Microsoft connection to the CIFS.


Have you tried taking a packet trace?

--
Jared Jennings - Data Technique, Inc.
Novell Support Forums Sysop
My Blog and Wiki with Tips, Tricks, and Tutorials
http://jaredjennings.org
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.