Guest User!

You are not Sophos Staff.

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

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.
  • Hi, Matthew and welcome to the UTM Community!

    If you're looking at the console, you should see the linux login just below the IP you should be trying to reach. Try plugging into the other NICs - any luck?

    Cheers - Bob
     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
  • Your UTM and PC appear to be in different subnets: put them in the same subnet (192.168.2.0/24) by changing the PC to 192.168.2.10.

    The console can probably be logged into, pre-wizard, with root and no password (just hit enter when prompted) - I have not tested this with recent versions.
  • sorry - I had a type in the original post. My PC IP address is 192.168.2.10 subnet 255.255.255.0. The UTM admin ip is 192.168.2.100:4444.

    The console screen does not have the IP address listed. Just the standard linux login prompt. Root with empty password does not work.
  • "The console screen does not have the IP address listed." - That sounds like a failed install, Matthew.

    Cheers - Bob
     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
  • 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.

  • 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)?

    Managing several Sophos UTMs and Sophos XGs both at work and at some home locations, dedicated to continuously improve IT-security and feeling well helping others with their IT-security challenges.

    Sometimes I post some useful tips on my blog, see blog.pijnappels.eu/category/sophos/ for Sophos related posts.

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

  • 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.
  • 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
     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
  • 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.