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

Still can't access default IP!

Hello, I am still unable to connect to the default address with the home version of XG Firewall. I have tried everything under the book and this is just a nightmare! It appears that the DHCP server during initial setup isn't working and my network (even IP scanners) can't find any live address of 172.16.16.16, it appears not to be broadcasting anything! If I hardline into the server that is running XG and set a static IP what am I supposed to do with Gateway and DNS? Also during first boot there were error messages containing to page cache, I dont know if thats a problem but I am sure having hell with this small mistake Sophos made...

This thread was automatically locked due to age.

Parents

0 Mike B over 9 years ago

What I did was open the command prompt from windows and run
ping 172.16.16.16 -t

I left this up and running.

I then set up the ip setting for my NIC to be 172.16.16.1 with a mask of 255.255.255.0. I left the DNS and gateway blank because they were not needed.

I then connected to each port and monitored my command prompt for a response. I have four NICs in my appliance and didn't know which one would be the one programmed for the IP. This allowed me to find it.

Mike
Cancel
Vote Up 0 Vote Down

Cancel
0 ChristopherGault over 9 years ago in reply to Mike B

I kept on getting error "Destination host unreachable"
Cancel
Vote Up 0 Vote Down

Cancel
0 Mike B over 9 years ago in reply to ChristopherGault

I don't know. What NIC is in the R310?

I looked at the SPECS and don't see any reason it would be having an issue. Throw a linux version like Ubuntu on it and see if all the NICS come up. That will let you know if you have a hardware problem. You don't need to install Ubuntu. Just run it from a USB drive. I use RUFUS to make my bootable USBs. It is handy to have one around anyways.

-Mike
Cancel
Vote Up 0 Vote Down

Cancel
0 ChristopherGault over 9 years ago in reply to Mike B

I was running Windows Server 2012 R2 on it yesterday and both ports were available...
Cancel
Vote Up 0 Vote Down

Cancel
0 Mike B over 9 years ago in reply to Mike B

Are you connecting through a switch or directly to the R310?
Cancel
Vote Up 0 Vote Down

Cancel
0 ChristopherGault over 9 years ago in reply to Mike B

Directly into the R310
Cancel
Vote Up 0 Vote Down

Cancel
0 Mike B over 9 years ago in reply to ChristopherGault

Does your nics support MDIX auto? Pretty much, do you know if you need a cross-over cable or not? Can you through a switch between them and use two straight-thru cables to be sure. Or boot from linux so you can see ping between the two hosts and ensure NICS are all working with the drivers in a general linux kernel.
Cancel
Vote Up 0 Vote Down

Cancel
0 ChristopherGault over 9 years ago in reply to Mike B

Cross-over cable?
Cancel
Vote Up 0 Vote Down

Cancel

Reply

0 ChristopherGault over 9 years ago in reply to Mike B

Cross-over cable?
Cancel
Vote Up 0 Vote Down

Cancel

Children

0 Mike B over 9 years ago in reply to ChristopherGault

Like devices (computers) need to have the transmit and receive pins switched. Current hardware senses they are like devices and changes the transmit and receive pins. There is still a chance the NICs you have don't sense this and it will require a cross-over cable. Easiest way is to boot into a known good and ping between the two devices. Or throw a dumb switch in between them. I would still boot into Linux to verify connectivity between the R310 and laptop.
Cancel
Vote Up 0 Vote Down

Cancel
0 ChristopherGault over 9 years ago in reply to Mike B

Ok, also I have a GS108 unmanaged switch...
Cancel
Vote Up 0 Vote Down

Cancel
0 Mike B over 9 years ago in reply to ChristopherGault

Put that between the two devices. That will take away any issue with the cross-over cable.
Cancel
Vote Up 0 Vote Down

Cancel
0 ChristopherGault over 9 years ago in reply to Mike B

Ok, give me a min.
Cancel
Vote Up 0 Vote Down

Cancel
0 ChristopherGault over 9 years ago in reply to Mike B

Nope, didn't work... still unreachable!
Cancel
Vote Up 0 Vote Down

Cancel
0 Mike B over 9 years ago in reply to ChristopherGault

You can ping another device on the switch?
Cancel
Vote Up 0 Vote Down

Cancel
0 Mike B over 9 years ago in reply to Mike B

Can you do an IPCONFIG /all from your cmd prompt and copy the output here.
Cancel
Vote Up 0 Vote Down

Cancel
0 ChristopherGault over 9 years ago in reply to Mike B

Yes
Cancel
Vote Up 0 Vote Down

Cancel
0 ChristopherGault over 9 years ago in reply to Mike B

Here it is:
Windows IP Configuration

Host Name . . . . . . . . . . . . : Christopher-PC
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Wireless LAN adapter Wi-Fi:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Broadcom 802.11ac Network Adapter
Physical Address. . . . . . . . . : 40-E2-30-98-71-96
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Wireless LAN adapter Local Area Connection* 2:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft Wi-Fi Direct Virtual Adapter
Physical Address. . . . . . . . . : 42-E2-30-98-71-96
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Wireless LAN adapter Local Area Connection* 4:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft Hosted Network Virtual Adapter
Physical Address. . . . . . . . . : 40-E2-30-98-71-96
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Ethernet adapter Ethernet:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) Ethernet Connection (2) I218-V
Physical Address. . . . . . . . . : 08-62-66-C7-E1-5B
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::809d:b132:d7bf:d84f%11(Preferred)
IPv4 Address. . . . . . . . . . . : 172.16.16.1(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
DHCPv6 IAID . . . . . . . . . . . : 151544422
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1C-FA-3B-7F-08-62-66-C7-E1-5B
DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter VirtualBox Host-Only Network:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : VirtualBox Host-Only Ethernet Adapter
Physical Address. . . . . . . . . : 0A-00-27-00-00-00
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::bcb0:ec01:4be0:46da%6(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.56.1(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
DHCPv6 IAID . . . . . . . . . . . : 503971879
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1C-FA-3B-7F-08-62-66-C7-E1-5B
DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter Bluetooth Network Connection:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Bluetooth Device (Personal Area Network)
Physical Address. . . . . . . . . : 40-E2-30-92-E2-C7
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Teredo Tunneling Pseudo-Interface:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter isatap.{6EC61585-1BBA-40DF-93DF-23AE596A2CE6}:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter isatap.{4D77A6DA-8449-403D-8BB3-5B2F5F809594}:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter #3
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Cancel
Vote Up 0 Vote Down

Cancel
0 Mike B over 9 years ago in reply to ChristopherGault

See nothing wrong with that.
Cancel
Vote Up 0 Vote Down

Cancel