AW: dsmcutil question
1999-02-17 10:35:07
Mark,
I think of two further possibilities:
Did you upgrade the ADSM client version? There is a problem that one DLL
is not removed from memory when stopping the scheduler service (since
V3PTF1). In this case you have to reboot the server to get dsmcutil working.
Also when upgrading the client, be sure to choose the same settings for "put
backup and adminclient into same directory?". If you choose to have two
directories you also have to create two option files.
Is there a firewall within your network? Even when the firewall is not
BETWEEN client and server, you can get quite funny effects. On one client we
had a default setting in the routing table that pointed to the firewall.
Pinging the server worked perfectly, the firewall rerouted the packets back
to the LAN. It even worked to use the dsm* tools right after pinging, as the
correct route to the server was cached for some minutes. A scheduled command
or an attempt without pinging the server first failed...
Good luck!
Regards,
Michael
|
<Prev in Thread] |
Current Thread |
[Next in Thread> |
- AW: dsmcutil question,
Michael Bartl <=
|
|
|