Guest User!

You are not Sophos Staff.

Thread Info
  • State Verified Answer
  • Locked Locked
  • Replies 11 replies
  • Subscribers 7 subscribers
  • Views 14059 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

UTM 9.351 install question

MatthewFord

After installing UTM 9.351 software on a compatible PC and rebooting, should I be presented with the Linux console login screen or something else?  The installation appears to have been successful, but I am unable to browse or ping the Webadmin at the configured address of 192.168.2.100:4444 from a PC that is directly connected to the correct admin NIC and configured with a static IP of 192.168.1.10 and subnet 255.255.255.0 (no gateway defined).  Any thoughts?

I have been unable to locate a default password for the Linux console - I was thinking that if I could login and check ifconfig to verify it may help point me to the problem.



This thread was automatically locked due to age.
Parents Reply Children
  • 0 in reply to BAlfson

    To reiterate, this is 9.351, in case it is different from previous versions.  And I used the "asg-9.351-3.1.iso" image.

    The installation screen did indicate that it finished successfully and provided IP address.

    Then, after reboot, the only failure was on the AD server, which I don't have:

    It did appear to wait for network configuration for a while, but, after the second "waiting for network configuration" message, it quickly flipped to the Ubuntu console screen:

     I have reinstalled 10+ times with same result, selecting both 64-bit and 32-bit kernels and always selecting the full install (not basic) with all additional tools with the same result upon reboot.

    Thanks for your help.

  • 0 in reply to MatthewFord
    You did use https://192.168.2.100:4444 (and not http) did you?
    Did you also connect the client to the correct interface (you should have at least 2)?
  • 0 in reply to apijnappels

    Correct - HTTPS. And yes, I connected the client to the NIC (1 of 4) that was identified as "link" during the installation process (ETH1)

  • 0 in reply to MatthewFord
    The installer screen looks like the UTM installer.

    The boot screen and login screen do not look like Sophos UTM. A proper UTM banner does not mention Ubuntu. (Was the previous OS on that system/drive Ubuntu LTS?) It may be necessary to use a third party tool to wipe the drive.

    Run through the installer in a virtual machine to, hopefully, see correct behavior in first boot and beyond.
  • 0 in reply to MatthewFord
    I've never seen an Ubuntu login on any UTM. The underlying Linux is SUSE. Try another hard drive or delete all of the partitions on this one. Any luck there?

    Cheers - Bob
  • 0 in reply to teched
    OK, I found the problem. It was the old ID10T error. You know, the problem between the seat and the keyboard? Your comment made me realize that I had a second drive plugged in that had Ubuntu Server installed on it. Once I disconnected that drive, I booted into UTM and was able to connect my client without problem. Thanks for the assist.