SEP connection client to server

[Joseph Stefanelli]

Hello.  I am migrating from SEPM to SEPM. Same versions on both machines.  I feel like I am close.

I am going the route of changing hostname and IP so I am currently not performing any disaster recovery procedures.  Simply testing migration of a few clients from oldserver to new server.  

I setup a policy with priorities of the new server and old server as a backup priority.  Everything is configured properly on the new server
Firewalls allow incoming and outbound connections for the sep webserver and manager software.  I am getting a weird error in the logfile when i establish a connection from the client in the troubleshooting section

06/02 17:30:35 [8680:4692] <CHttpRequest::HttpExtensionProc> [internal ip] Returning 400 Bad Request, No length parameter for the encoding URL!
In addition to this log there is a lot of random characters(ÇOµc›Òm...)

I am not sure what is happening here and why I am getting these errors.

Any assistance?

[Moin Sobhan]

Hi Joseph,

SEP 14 is such a buggy version. Tried the same and it didn't work. However testing I did that was from moving clients from SEPM12 to SEPM14 management console by modifying Management Server List. You may need to check "Reconnection Preference". Returning 400 Bad Request - basically saying Apache is rejecting the connection.

[Joseph Stefanelli]

Ill try that.  I am using 14.2, any idea if this is fixed on 14.3?  I was able to move one computer by manually using the sylinkdrop.  That is obviously going to be difficult with a large amount of computers.  Where are the reconnection preferences?

[Joseph Stefanelli]

No dice on resolving the issue.  The only process that works is on individual computers by using sylinkdrop utility and using the new server.  Other than that, using the server management list and updating the policy it fails to connect to the new server.   Gives that http 400 error. I went to reconnection preferences and made the changes as well. also uninstalled and reinstalled the client after redeploying the software.  I am out of ideas Even network Monitor shows the same information but no reason as to why

[DAVID MATTHEWSON]

We've just done this - 14.0 to 14.3 and moved name & IP. We made anew server management list with both servers and Ips listed, let it all run for a few days to allow clients to 'catch up' and then removed the old VM management server. Several days later it seems ok. ISTR SEPP uses FQDNs at the client level to find the server and only if the DNS lookup fails does it revert to IP..

[Joseph Stefanelli]

I upgraded to 14.3 sepm to see if same problem occurs and still get the HTTP 400 Errors.  Any other guidance you can recommend?

[John Owens]

400 Bad Request can be a KCS value mismatch.  Compare your Sylink.xml from the client (open in Notepad) and look for kcs value.  Compare that with the KCS value in your SEPMs conf.properties file.  If they do not match that will be your issue.  You will need to drop Sylinks onto these clients.

------------------------------
John Owens
Principal Product Support
Symantec
United States
------------------------------