Hi,

Compare q no f=d output of the node with the current ip address of that
node. Some of the registered ip's of that node might have not been updated.

Having dhcp enabled on your backup clients and having them switch ips
constantly will cause issues for tsm server to tsm client communications
even when running in polling mode.
Op 1 jun. 2015 22:27 schreef "Zoltan Forray" <zforray AT vcu DOT edu>:

> We are migrating our TSM infrastructure to DHCP assignments for the client
> nodes/servers.  Up until no everything seems to have worked OK.
>
> Now we moved a bunch of CIFS backups to DHCP and having problems logging in
> to an administrator ID via the WEB client on the box.
>
> Every attempt to login produces "invalid password" for the administrator,
> no matter how many times we reset the password. Logging in as this same
> admin ID via a different interface work with no problem.  The admin ID has
> full privileges.
>
> The config is this.  The connection from this node server to the TSM server
> is DHCP / 172 range.  The webport connection to the box is a fixed private
> 192.168 address. The client is 7.1.2.0
>
> Any thoughts?
>
> --
> *Zoltan Forray*
> TSM Software & Hardware Administrator
> Xymon Monitor Administrator
> Virginia Commonwealth University
> UCC/Office of Technology Services
> www.ucc.vcu.edu
> zforray AT vcu DOT edu - 804-828-4807
> Don't be a phishing victim - VCU and other reputable organizations will
> never use email to request that you reply with your password, social
> security number or confidential personal information. For more details
> visit http://infosecurity.vcu.edu/phishing.html
>