Video Screencast Help

Server loses fix IP after SEP-Update

Created: 09 Apr 2013 • Updated: 09 Apr 2013 | 3 comments
Sepp105's picture

Hello

We have an issue when updating the SEP-Client on servers. After the Update, we do the mandatory reboot and everything seems to work fine. But after another reboot (which may happen a few months later) the server loses his fixed IP-Address by creating a new network interface and switchting it to DHCP... We have been struggling with this for a few weeks now.

Situation:

- Only happens on Windows Server 2003

- Happens on both 32 & 64 bit OS

- Virtualised in VMWare

- Happens with the built-in autoupdate of SEPM, as well as manual executing of the installpakage

- There are no open RDP-sessions, no open Shared Files-sessions and no other logged in users during update

- Updating from 11.0.X to 12.1.1000

I was able to reproduce this error:

Network connection before update:

lan1.PNG

After the completion of the Update, a reboot is requested:

reboot.PNG

After the reboot is done, SEP is green and looks fine, but the Network connection already changed. Notice that now it's called "Local Area Connection 2". The IP in cmd is still correct though:

network_disabled.PNG

infact_dhcp.PNG

ip.PNG

Next I reboot again and the server loses it's fix IP. I get the following messages when trying to set the fix IP-address again:

apipa_address.PNG

error1.PNG

and

error2.PNG

After this the server is back online, but this is kind of ugly.

Any information about why this happens is greatly appreciated.

Best Regards

Operating Systems:

Comments 3 CommentsJump to latest comment

Brɨan's picture

Do you have NTP installed?

Please click the "Mark as solution" link at bottom left on the post that best answers your question. This will benefit admins looking for a solution to the same problem.

Sepp105's picture

Yes, it was installed before the update, but my 12.1.1 pakage contained AntiVirus-only. So it's uninstalling NTP with the update.

Before the update:

sepversion.PNG

Brɨan's picture

Seems to be a know issue per the same thread here:

https://www-secure.symantec.com/connect/forums/upg...

I would suggest opening a case.

Please click the "Mark as solution" link at bottom left on the post that best answers your question. This will benefit admins looking for a solution to the same problem.