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

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

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
  • AFAIK you can't login to the console until you finished the setup wizard only available as a browser application. You should connect Port1 (LAN) to a switch and use another computer to go throught the wizard. I think setup runs a DHCP server and your machine should get 172.16.16.17 if connected properly (at least mine did). Afterwards you need to set a static IP because DHCP setup is not part of setup/activation/registeration process. If you can't get the connection working try setting up a static IP e.g. 172.16.16.17 or something similar.

    And if your are using Chrome or Safari be sure to enter https:// in browser because it will go with HTTP if you will just enter the IP and port.
  • I ended up doing something along those lines... in vSphere I had to make a new switch; essentially deprovision it from the Lab Network (our network auto provisions based on a bunch of conditions). Set it up as sort of a dumb stand alone. Make a whole new VM Desktop - attach it to the new switch - IP it (didn't know about the DHCP on that interface). Go through the web setup. Drop back in to console as soon as the activation portion was done & log in. Reconfigure the interface to DHCP [vmware reservations], reboot - test connectivity from the "real" network. Destroy the VDI & vSwitch, then move forward with configuration.

    Essentially - build a whole new network in order to make it work. All from not being able to just push "y" on the EULA in the console. Even the whole activation portion is something I feel could've been accomplished in a couple of Y/N prompts and a prompt for your key...
  • I agree that it should be possible to activate the device / appliance using vga or serial console but it is not just for now. I always have Ubuntu ISO nearby for that purpose ;-)
Reply Children
No Data