![]() ![]() ![]() (all still working on AMD64 as I type this). I can see the WAN link light and various data flashes but the box says no! The WAN connection is PPPoE and I told it that while I had communication via the LAN at address 192.168.1.2 I also provided the username and password for the ISP. The usual process of starting without WAN or LAN and providing a WAN connection for an auto detect does not work. Probably someone with more knowledge of the tools it offers could make progress in finding out why it is unwilling to respond to the LAN. It has never wavered in its duty to be there. Similarly it does not respond with WEBConfig when asked to with a browser.Īll the while the console is up. When I run a LAN IP scan it is not there from which I conclude it is staying shtum even though it is on the subnet. The SG1100 will not ping from the LAN at 192.168.1.1 It will ping other members of the LAN using its own ping tool. I got that going so that I could learn the ropes before the SG1100 turned up. It is a problem that when given the real seat at 192.168.1.1 I have to disconnect my working installation of an AMD64 which has worked sweetly for about 6 weeks. This done it has refused to communicate over the LAN which it just did when addressed as 192.168.1.2 This worked so I set about giving it minimal configuring to have a go in the real seat at 192.168.1.1 I set it up as 192.168.1.2 so that I could communicate with it on the LAN web interface. Progress you might think with the replacement. The one I sent back had a dud console socket. I got a new SG-1100 from the UK distributor and it does, without fail communicate on it's console port. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |