Got a strange problem with a Windows 2003 server and the latest client.

This Windows server was having VSS errors.  The admin went through the
VSSWriter/list processes and all seems to be good.

However, the client simply hang and wont do a thing.  This was a working
client and the user decide to upgrade to 6.2.1.

I have his rework his dsm.opt so it has the bare minimum - NODENAME,
TCPSERVERADDRESS, VERBOSE and DOMAIN.  Even added -systemstate to DOMAIN
thinking it might be having problems with that.

Running the CLI/dsmc produces nothing.  It starts and just sits there.   I
even tried introducing errors in the opt file and it would recognize them
and issue error messages and fail, so I know syntax checking is working.

Can successfully ping the TSM server via both IP and DNS name, so
connectivity isn't the problem - besides, it used to work and there are
existing backups.   But now, it never gets as far as trying to connect to
the TSM server.

Client has been uninstalled/deleted/reinstalled.  System has been
rebooted.

What can we do to further diagnose/resolve where the hang is?  Are there
processing/startup options/traceflags to show where it is and what it is
doing?
Zoltan Forray
TSM Software & Hardware Administrator
Virginia Commonwealth University
UCC/Office of Technology Services
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