Important note about SSL VPN compatibility for 20.0 MR1 with EoL SFOS versions and UTM9 OS. Learn more in the release notes.

Thread Info
  • State Suggested Answer
  • Locked Locked
  • Replies 19 replies
  • Answers 1 answer
  • Subscribers 46 subscribers
  • Views 77082 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

172.16.16.16 not working

pmolan

Right now I have UTM9 on a dell 2950..  No issues.

I bought 2 Dell 1950 servers from craigslist mainly because they were cheap and I like to play with this stuff.  I installed Pfsense on one of them and I have basic WAN/LAN functionality.   I installed XG on the other but have no access  to https:://172.16.16.16:4444.  I set my laptop to 172.16.16.1, 255.255.255.0.  Thinking possibly there was something wrong with my craigslist find, I installed XG on the other server, overwriting the working pfsense.  Still no access to the web gui.

I tried both ports.

I tried the ping 172.16.16.16 -t trick

I tried booting up with WAN in one and Laptop in the other.

I waited 4 hours.

Not working

Nic card:

Broadcom Corporation NetXtreme II BCM5708 Gigabit Ethernet

This appears to be the same model Nic as the 2950 which is currently working with UTM9

Any thoughts?



This thread was automatically locked due to age.
  • 0
    I had the same issue with Broadcom NICs it would never work. I eventually installed an Intel quad port card, disabled the onboard NICs and it worked perfectly.
  • 0
    XG systems need to operate 2 lan card, so you try to connect the remaining port and perform the ping command to test, you should set the 255.255.0.0 subnet for your laptop.0919679920 Viet Nam
  • 0

    Hi, same problem here. - Installed latest sophos firewall on bare metal. My client system gets an ip from the sophos dhcp system and can ping 172.16.16.16, but i am not able to login to 172.16.16.16:4444 to accept EULA. :( - Rebooted the machine multiple times. NIC-Adapter is an Intel Pro 1000 GT.
    Looks like a common problem with the latest sophos release as i see other users which ran into the same problem. (i guess compatibility issues with some bare metal machines).

  • 0
    I did an experiment. I installedUTM9 on that server and still had no access to the management page. Pings did not respond either. Both eth0 and eth1 did not function as intended. I installed a second NIC, Intel this time, eth2 and eth3 and assigned the management to eth3. I got in on eth3 after install.
    I assigned lan addresses to eth0 and eth1 on the Broadcom Corporation NetXtreme II BCM5708 Gigabit Ethernet. It functions correctly.
    Maybe there is something broken in the install package? I know the Broadcom Corporation NetXtreme II BCM5708 Gigabit Ethernet works because I have used to for 2 years on my other 2950.
  • 0
    i have the same problem. Can you found the answer?
  • 0
    Independent of the support for the broadcom ethernet adapter: You set your laptop to 172.16.16.1, 255.255.255.0. That is the wrong subnet mask. You should set you laptop to 172.16.16.1, 255.255.0.0. (notice the zero instead of 255)
  • 0 in reply to JohanCamps
    wen i set the laptop to 172.16.16.1, 255.255.255.0 or 172.16.16.1, 255.255.0.0 , then i can ping to 172.16.16.16. I have no access to https:://172.16.16.16:4444.
  • 0
    I installed it on Bare Metal with Intel i210AT LAN controller which worked well.
    Those guys who are expiring problem, connecting via IP: Did you see any ARP Adresses (cmd > arp -a on Windows) on the Interface on your Laptop you conntected to the Firewall? If so, this would indicate a broken IP-config.

    What does the COM-CLI say? Do you see any interfaces there?

    Please send me Spam gueselkuebel@sg-utm.also-solutions.ch

  • 0 in reply to HuberChristian
    I am running into this same issue on a system that I just built. Installation went fine, and the CLI shows that 3 interfaces are found. I received a DHCP address of 172.16.16.17, and I can ping 172.16.16.16. However, when I try to browse to https://172.16.16.16:4444 nothing comes up. I have also tried two different NIC cards. One is based on the Realtek RTL8111 Chipset, while the other is based on the Intel i350 chipset.

    Here are the specs of the system:
    Rosewill Mini ITX Tower
    MSI AM1I AM1 2 x SATA 6Gb/s USB 3.0 HDMI Mini ITX AMD Motherboard
    Crucial 8GB Single DDR3 1600
    AMD Athlon 5350
    Kingspec 2.5" SATAIII

    I tried these two NIC cards:
    SYBA 2 Port Ethernet PCIe x 1 Card, Realtek RTL8111 Chipset
    HP Ethernet 1Gb 2-port 361T Adapter, Intel i350 Chipset

    I also tried disabling the onboard NIC just to take it out of the equation.

    When I run an "arp -a" from the command line I get the following:
    Interface: 172.16.16.17 --- 0x9
    Internet Address Physical Address Type
    172.16.16.16 5c-b9-01-8a-2b-60 dynamic
    172.16.16.255 ff-ff-ff-ff-ff-ff static
    224.0.0.22 01-00-5e-00-00-16 static
    224.0.0.252 01-00-5e-00-00-fc static
    255.255.255.255 ff-ff-ff-ff-ff-ff static
  • 0
    Hi,

    i found my problem. The Bios-Time is for the xg-os very importent. I must set the correct time, than ws the connect to 172.16.16.16 ok.
Unfiltered HTML