Guest User!

You are not Sophos Staff.

Thread Info
  • State Suggested Answer
  • +1 person also asked this people also asked this
  • Locked Locked
  • Replies 14 replies
  • Answers 1 answer
  • Subscribers 26 subscribers
  • Views 62867 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

SW-SFOS 15.01.0-376 Installed but on first boot it says to login and accept agreement but i cant get on it??

JohnKenny

I have just installed SW-SFOS 15.01.0-376 and it seemed to finish and rebooted, I was then asked to enter password I entered admin.  Then it said i needed to login and accept the licence agreement.  I assume thats on https://172.16.16.16:4444?  However I cannot access the page, should it show me the URL to goto on the machine itself?  How can i tell if the NIC is working?  It does ask for another password again but when i enter admin it doesnt do anything.

Can anyone help?

Thanks

KL



This thread was automatically locked due to age.
Parents
  • 0

    Hi John,
    I too have experienced the same issues you are suffering from. I installed the SW-SFOS_15.01.0-376.iso onto a UTM 120 and it got to the point where it asks to accept the EULA. At this point I can ping the IP 172.16.16.16 having received a dynamic IP of 172.16.16.17. I couldn't get to the default URL https://172.16.16.16:4444 which should then forward to 172.16.16.16:4444/.../login.jsp.

    At this point i ran a nmap -p 1-65535 -T4 -A -v 172.16.16.16 scan that produced the following results.
    22/tcp open ssh
    443/tcp closed https
    2712/tcp open aocp
    3128/tcp closed squid-http
    4444/tcp closed krb524
    8090/tcp closed unknown
    8094/tcp open ssl/unknown
    9922/tcp open ssl/unknown

    At this point i wondered what services would be up and running if I were to spin this up as a VM so using the same image I got to the point where it asks to accept the EULA and the default URL https://172.16.16.16:4444 forwarded to 172.16.16.16:4444/.../login.jsp.

    I then ran a nmap -p 1-65535 -T4 -A -v 172.16.16.16 scan again on the VM and produced the following results.
    22/tcp open ssh
    443/tcp open ssl/https
    2712/tcp open aocp
    3128/tcp open squid-http
    4444/tcp open ssl/krb524
    8090/tcp open unknown
    8094/tcp open ssl/unknown
    9922/tcp open ssl/unknown

    The install must be aware of the virtual NIC's or lack of in the first case and purposefully close the ports to which the services/daemons are running..

    Maybe the Sophos Team could comment further on this..?

Reply
  • 0

    Hi John,
    I too have experienced the same issues you are suffering from. I installed the SW-SFOS_15.01.0-376.iso onto a UTM 120 and it got to the point where it asks to accept the EULA. At this point I can ping the IP 172.16.16.16 having received a dynamic IP of 172.16.16.17. I couldn't get to the default URL https://172.16.16.16:4444 which should then forward to 172.16.16.16:4444/.../login.jsp.

    At this point i ran a nmap -p 1-65535 -T4 -A -v 172.16.16.16 scan that produced the following results.
    22/tcp open ssh
    443/tcp closed https
    2712/tcp open aocp
    3128/tcp closed squid-http
    4444/tcp closed krb524
    8090/tcp closed unknown
    8094/tcp open ssl/unknown
    9922/tcp open ssl/unknown

    At this point i wondered what services would be up and running if I were to spin this up as a VM so using the same image I got to the point where it asks to accept the EULA and the default URL https://172.16.16.16:4444 forwarded to 172.16.16.16:4444/.../login.jsp.

    I then ran a nmap -p 1-65535 -T4 -A -v 172.16.16.16 scan again on the VM and produced the following results.
    22/tcp open ssh
    443/tcp open ssl/https
    2712/tcp open aocp
    3128/tcp open squid-http
    4444/tcp open ssl/krb524
    8090/tcp open unknown
    8094/tcp open ssl/unknown
    9922/tcp open ssl/unknown

    The install must be aware of the virtual NIC's or lack of in the first case and purposefully close the ports to which the services/daemons are running..

    Maybe the Sophos Team could comment further on this..?

Children