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

WAN port not connecting

I am setting up an XG 115 but I can't get Port 2 to connect with my ISP through my cable modem.

The initial set up (before introducing the XG 115) is that I have a Virgin Media (UK ISP) 'Superhub' operating as a modem.  I then have a Netgear router connected to the modem and from the router to multiple switches.  This set up works fine.  The intention is to replace the Netgear router with the XG 115 but when I plug the XG 115 into the modem (port 2 of the XG set to DHCP) it doesn't get an IP address.

The LAN side is working fine.  I have completed the set up and can connect to the console.  From there I can configure port 2 but nothing I have tried causes the connection to come up.

If I re-introduce the Netgear router and simply connect the XG 115 to one of the LAN ports on the router, all is good.  The XG 115 connects and I can access the internet from a laptop connected to the XG.

There are no unusual settings on the Netgear router that allows it to connect successfully with the modem (which by the way, although branded as a Virgin super hub is also a Netgear device).  The settings are simply to get the IP address and DNS from the ISP.

I have searched the forum but I seem to be alone in failing to have an XG device connect successfully with an ISP.

Any thoughts would be gratefully received.



This thread was automatically locked due to age.
Parents
  • Hi Philip,  You are not alone, I am having exactly the same problem with an XG115W.  I have many XG appliances deployed with ADSL/VDSL and Cable services using DHCP, Static and PPPoE connections.  At this site I have a Point-to-Point Wireless connection.  The XG will not connect to the gear.  I put in a cheap Asus router and it connected with no issues.  If I set the XG up to DHCP (currently static with the supplied ISP IP info - which works on the Asus and a laptop BTW, no MAC changes needed) it will get an IP from the Asus on the LAN port.  We had a support call and had one 115W returned on an RMA, but when I took it back to the office, it worked fine.  The new device was configured fully at the office and when brought to the site, it will not connect to the PTP connection any more. I am currently on hold - over 30 minutes - for support to ask more about this.   I will reference your post and the answer that worked for you.  We are attempting this change.  Thanks for posting!

  • I still have an open case.  Their top level support engineer could not get the Sophos to connect directly to the Wireless modem.  We put a switch between the modem and the Sophos XG and it connected.  Seems to me that the XG does not support automatic MDI/MDI-X and perhaps the wireless modem does not as well.  This means that only a crossover cable would work to connect the two.  Obviously the laptops we tested and the cheap Asus router support automatic MDI/MDI-X.  I am interested in knowing if this is the same for all XG devices or only the 115W.  I will update when there is a solution from Sophos support just in case others are having the same frustration.

Reply
  • I still have an open case.  Their top level support engineer could not get the Sophos to connect directly to the Wireless modem.  We put a switch between the modem and the Sophos XG and it connected.  Seems to me that the XG does not support automatic MDI/MDI-X and perhaps the wireless modem does not as well.  This means that only a crossover cable would work to connect the two.  Obviously the laptops we tested and the cheap Asus router support automatic MDI/MDI-X.  I am interested in knowing if this is the same for all XG devices or only the 115W.  I will update when there is a solution from Sophos support just in case others are having the same frustration.

Children
No Data