Analysis Server Problem - "Assessing Analysis Server status"

We are experiencing a problem running 3.5.2 with the server failing to connect to the analysis server running on a separate (windows) machine.

The warning message: "Assessing Analysis Server status..." is reported in the Start Center landing screen.

The analysis server has been restarted.  There are no apparent problems reported in the logs: Analysisserver.log and Launcher.log.  See below for details of these files.

The Test feature inside the 'Manage dynaTrace Servers - Services - 'dynaTrace Analysis Server' tab reports "Error: Failed to test connection for accessing dynaTrace Analysis Server." after pausing for several minutes.

A telnet connection from the server machine to the analysis server machine confirms that port 7788 is listening. 

Any help would be greatly appreciated.

Thanks,

Simon

Analysisserver.log
2012-02-27 16:20:48 INFO [HttpActivator] Webservice Bundle started
2012-02-27 16:20:48 INFO [OOPAnalyzer] -----------------------------------------------------------------------------
2012-02-27 16:20:48 INFO [OOPAnalyzer]  dynaTrace Analysis Server Copyright (C) 2004-2011 dynaTrace software GmbH
2012-02-27 16:20:48 INFO [OOPAnalyzer] -----------------------------------------------------------------------------
2012-02-27 16:20:48 INFO [OOPAnalyzer]  Version 3.5.2.2393  built Wed Apr 27 21:05:01 EST 2011
2012-02-27 16:20:48 INFO [OOPAnalyzer] 
2012-02-27 16:20:48 INFO [OOPAnalyzer] Platform: Windows 2003 5.2, x86
2012-02-27 16:20:48 INFO [OOPAnalyzer] vm: Java HotSpot(TM) Server VM 1.6.0_21, Sun Microsystems Inc., mixed mode
2012-02-27 16:20:48 INFO [OOPAnalyzer] Configuration summary:
2012-02-27 16:20:48 INFO [OOPAnalyzer]   Session directory: C:\Program Files\dynaTrace\dynaTrace 3.5.2\server\sessions\stored
2012-02-27 16:20:48 INFO [OOPAnalyzer]   Config directory: C:\Program Files\dynaTrace\dynaTrace 3.5.2\server\conf
2012-02-27 16:20:48 INFO [OOPAnalyzer]   Log directory: C:\Program Files\dynaTrace\dynaTrace 3.5.2\log\analysisserver
2012-02-27 16:20:48 INFO [OOPAnalyzer]   Listen address: <All local>
2012-02-27 16:20:48 INFO [OOPAnalyzer]   Listen port: 7788
2012-02-27 16:20:49 INFO [OOPAnalyzer] memory: 761MB heap, 128MB perm
2012-02-27 16:20:49 INFO [OOPAnalyzer] Starting dynaTrace Analysis Server...
2012-02-27 16:20:49 INFO [ShutdownPipe] found named pipe for shutdown - listening
2012-02-27 16:20:50 INFO [NexusServiceComponent] Master/Detail dashlet interaction service (Nexus) started
2012-02-27 16:20:56 INFO [FileBasedSessionManager] Initializing stored session manager...
2012-02-27 16:21:00 INFO [WatchDog] WatchDog "Snoopy" has been started
2012-02-27 16:21:00 INFO [OOPAnalyzer] dynaTrace Analysis Server successfully started
2012-02-27 16:21:45 INFO [WatchDog] Connected to native watchdog on [localhost:50000]

Launcher.log

2012-02-27 16:19:23 info    [native] -----------------------------------------------------------------------------
2012-02-27 16:19:23 info    [native]  dynaTrace Analysis Server, Copyright (C) 2004-2010, dynaTrace software GmbH
2012-02-27 16:19:23 info    [native] -----------------------------------------------------------------------------
2012-02-27 16:19:23 info    [native] Native Launcher version: 3.5.2.2393 - built 2011-04-27 07:43:06 +0200
2012-02-27 16:19:23 info    [native] Starting service "dynaTrace Analysis Server 3.5.2"...
2012-02-27 16:19:33 info    [native] Launcher configuration summary for dynaTrace Analysis Server:
2012-02-27 16:19:33 info    [native]   Launcher: C:\Program Files\dynaTrace\dynaTrace 3.5.2\dtanalysisserver.exe
2012-02-27 16:19:33 info    [native]   Java VM:  C:\Program Files\dynaTrace\dynaTrace 3.5.2\jre\bin\java.exe
2012-02-27 16:19:33 info    [native]   Java version: 1.6.0_21 32-Bit
2012-02-27 16:19:33 info    [native]   Working directory:  C:\Program Files\dynaTrace\dynaTrace 3.5.2\server
2012-02-27 16:19:33 info    [native]   Configuration file: C:\Program Files\dynaTrace\dynaTrace 3.5.2\dtanalysisserver.ini
2012-02-27 16:19:33 info    [native]   Native watchdog timeout: 180 sec (timeout for graceful shutdown: 300 sec)
2012-02-27 16:19:36 info    [native] Process created successfully, pid: 1384
2012-02-27 16:19:36 info    [native] Ping outdated, resetting timout limits
2012-02-27 16:20:13 info    [java  ]