post the logs, somebody will help you out..

Hi Raul,

What about DNS - specifically reverse DNS?  Can the server resolve the dynamic client names - and how quickly?  Thanks!

You can look for the DNS Address provided in a DHCP lease and the DNS Server Address that you configure in a Static IP address.

Make sure that they are the same.

Cheers,
Aniket

Hi,

Douglas I checked again and the DNS and reverse DNS works fine. I can resolve the client hostname from the server and the server name from the client. This takes place instantly.
Aniket the DNS server addresses configured on the client are the same in static and dynamic mode.

This are the lines where the logging stops when the IP is configured in dynamic mode:
09/09 16:16:50 [3716] <SendRegistrationRequest:>http://servername:8014 [encrypted data]
09/09 16:16:50 [3716] <SendRegistrationRequest:>SMS return=200
09/09 16:16:50 [3716] <ParseHTTPStatusCode:>200=>200 OK
09/09 16:16:50 [3716] <SendRegistrationRequest:>Content Lenght => 350
09/09 16:16:50 [3716] HTTP returns status code=200
09/09 16:16:50 [3716] <SendRegistrationRequest:>RECEIVE STAGE COMPLETED
09/09 16:16:50 [3716] <SendRegistrationRequest:>COMPLETED, returned 0

When configured in static mode the logging goes on:
09/09 16:21:05 [3960] <SendRegistrationRequest:>http://servername:8014 [encrypted data]
09/09 16:21:05 [3960] <SendRegistrationRequest:>SMS return=200
09/09 16:21:05 [3960] <ParseHTTPStatusCode:>200=>200 OK
09/09 16:21:05 [3960] <SendRegistrationRequest:>Content Lenght => 350
09/09 16:21:05 [3960] HTTP returns status code=200
09/09 16:21:05 [3960] <SendRegistrationRequest:>RECEIVE STAGE COMPLETED
09/09 16:21:05 [3960] <SendRegistrationRequest:>COMPLETED, returned 0
09/09 16:21:05 [3960] HEARTBEAT: Check Point 5.1
09/09 16:21:05 [3960] <ScheduleNextUpdate>Manually assigned heartbeat=3 seconds
09/09 16:21:05 [3960] <PostEvent>going to post event=EVENT_SERVER_ONLINE
09/09 16:21:05 [3960] <PostEvent>done post event=EVENT_SERVER_ONLINE, return=0
09/09 16:21:05 [3960] HEARTBEAT: Check Point 8
09/09 16:21:05 [3960] <PostEvent>going to post event=EVENT_SERVER_DISCONNECTED
09/09 16:21:05 [3960] <PostEvent>done post event=EVENT_SERVER_DISCONNECTED, return=0
09/09 16:21:05 [3960] <RegHeartbeatProc>====== Registration Procedure stops at 16:21:05 ======
09/09 16:21:05 [3960] HEARTBEAT: Check Point 10
09/09 16:21:06 [3960] HEARTBEAT: Check Point Complete
09/09 16:21:06 [3960] <RegHeartbeatProc>Done, Heartbeat=3seconds
09/09 16:21:06 [3960] <CheckHeartbeatTimer>====== Heartbeat loop stops at 16:21:06 ======
09/09 16:21:10 [3960] <CheckHeartbeatTimer>====== Heartbeat loop starts at 16:21:10 ======
09/09 16:21:10 [3960] <GetOnlineNicInfo>:Netport Count=1

Hope this helps

Regards,
Raul

Check this out

https://www-secure.symantec.com/connect/articles/troubleshooting-client-commuincation

have your try to replace the sylink.xml,

it seems the client si connecting to server
09/09 16:16:50 [3716] <SendRegistrationRequest:>SMS return=200
09/09 16:16:50 [3716] <ParseHTTPStatusCode:>200=>200 OK

since you said that  If I change the IP address from dynamic to static the client can reach the management server.

verify if the DHCP IP details are on similar to the static one. Check IP config while in DHCP and in static. Apart from IP , the others should be same. subnet, gateway, DNS etc.

Replacing the sylink.xml doesn't do it. I've checked the IP configuration in static and dynamic mode and it matches. I also checked the link posted by Prachand and none of those solutions worked. It stops right before checkpoint 5.1

Hi,
I have the same problem; sylink monitor log stops right before checkpoint 5.1; if i switch the clients to static ip addresses everything works fine. On DHCP there are no communication issues with different applications other than the symantec client showing as being unmanaged. Any ideeas?