Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 4 replies
  • Subscribers 0 subscribers
  • Views 8399 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Virtual Email - Cant set static ip

SGICT

Hi,

Has anyone else experienced issues with their email appliance not being able to set a static IP since last night's update to 3.7.2.1?

At the moment we've set it to DHCP and reserved the IP in the pool so it obtains the correct IP for the time being. Quite weird though.

I've had to log a call with Sophos on this one but interested if anyone else has come across this

:26747


This thread was automatically locked due to age.
  • 0

    Development department of Sophos have seen this issue with 3.7.2.1 and Hyper-V. Sadly, not being a supported system means it wont get fixed by the looks of it.

    :26749
  • 0

    Hi SGICT,

    I noticed in one of your earlier posts you mentioned HyperV - Is this on a HyperV system?

    Unfortunately we've had an issue reported where new functionality in the network scripts doesn't work with HyperV network adapters. Sorry this wasn't picked up in testing because we don't test/support HyperV (or those adapters).

    The workaround would be to use a dynamic IP.

    Although it's not supported, Sophos support could also apply a temporary fix if we can arrange a remote session to the Hyper V box.  However, I'd strongly suggest to switch to VMware or a hardware appliance.

    If you have any questions (or I've misunderstood) then please do let me know.

    -Tom.

    :26751
  • 0

    Ah - you beat me to the post!  Sorry about the confusion

    Like I said we could get the static IP back for business critical issues - but this workaround could be reverted by future updates.

    I can't promise at this time if we will actually be able to permanently fix this.

    Sorry again for any inconvenience.

    :26753
  • 0

    Thanks TomA for your replies.

    I don't feel there's a need for us to have the fix applied as a DHCP server is resolving the issue.

    The only thing I would highlight is for businesses that use the virtual appliance on Hyper-V in a DMZ would be stuck as more than likely a DHCP server wouldn't be available.

    It does make us wary that Hyper-V isn't supported and a minor update can bring the system to its knees. We do have Exsi on standby but its not in production and nor do we want it to be - we prefer M$ solution to virtualisation so trying to hold out until Sophos will provide support on Hyper-V platform.

    :26775
Unfiltered HTML