rcxyz Posted January 3, 2016 Posted January 3, 2016 (edited) I recently upgraded a router, which seems like it was a bad idea, because it has caused all sorts of headaches. My Admin Console can't find the controller. I can see the ISY994-EMS on my DCHP client list, but I can't figure out how to tell the Admin Console what to do next. Thanks in advance, and sorry for being such an idiot. Ruth BTW, when I type the IP address into my browser, it doesn't connect and the browser times out. Thanks again. Edited January 3, 2016 by rcxyz
stusviews Posted January 3, 2016 Posted January 3, 2016 Did you assign a port other than 80? What is the result if you ping the IP address?
rcxyz Posted January 3, 2016 Author Posted January 3, 2016 No, I don't think I assigned a port other than 80. If I ping it, the requests time out. The controller is working, and I can access it from the app on my phone.
rcxyz Posted January 3, 2016 Author Posted January 3, 2016 Here is an odd thing. The settings for my app, Mobilinc Pro, show the controller at 192.168.1.101, port 80. I can sync with the ISY from this app. On my husband's phone, the settings show the controller at 192.168.1.105, and it cannot sync. It times out and says: a connection failure occurred.
DennisC Posted January 3, 2016 Posted January 3, 2016 Here is an odd thing. The settings for my app, Mobilinc Pro, show the controller at 192.168.1.101, port 80. I can sync with the ISY from this app. On my husband's phone, the settings show the controller at 192.168.1.105, and it cannot sync. It times out and says: a connection failure occurred. You indicated you can't connect when you type the IP address in your browser, but don't indicate which IP address you tried. Have you tried the IP address from the working phone? Also, could you have issued a static IP address in the old router? Dennis
rcxyz Posted January 3, 2016 Author Posted January 3, 2016 I tried both of the addresses. 101 fails instantly with the message "connection is refused", and 105 takes longer to fail, but eventually times out. I have a wired router (TP-Link) in the garage that provides wired access to the house and the office. I have two wireless routers configured as access points that are connected to the router in the garage (one Asus and one TP-Link). The change that I made was to swap an old Cisco 2.4Ghz wireless router with a new TP-Link wireless router that supports both 5Ghz and 2.4Ghz. When I plug the old router back in and attach the hub, the blue and red error lights blink. The static IP address would be in the router, which hasn't changed. I don't have any entries in the Static Routing table. Ruth
paulbates Posted January 3, 2016 Posted January 3, 2016 (edited) I When I plug the old router back in and attach the hub, the blue and red error lights blink. Ruth this is probably due to multiple DHCP servers available at the LAN level. This is especially problematic if the DHCP servers are handing out Static DHCP addressed to specific mac addresses. Edit: if not, some DHCP clients may be holding on to addresses and the dhcp server didn't catch it. I would shut everything off, restart the device with the dhcp server, and then start up the devices in question, like the ISY. Paul Edited January 3, 2016 by paulbates
DennisC Posted January 3, 2016 Posted January 3, 2016 As a follow up to what Paul has said, TP-Link instructions for using one of their routers as a wireless access point is to turn off DHCP in the access point. You might want to double check this was done and then follow Paul's suggestion to restart everything. Dennis
stusviews Posted January 4, 2016 Posted January 4, 2016 Something is amiss. If you can't ping the IP address, then either the address is incorrect or the router that the ISY is wired to cannot see the ISY or you have a conflict. Disconnect every router except the one that the ISY is wired to. A connection to the internet is not required. Search the attached/connected devices list for the ISY. AFAIK, the MAC address should start with 00:21:B9.
rcxyz Posted January 4, 2016 Author Posted January 4, 2016 Thanks so much for pointing me in the right direction. It turns out that if you want to use the Archer C7 as an access point, you must have the incoming ethernet cable plugged into a LAN port, not the WAN port. This is unlike any other router that I've worked with, but once I corrected that problem, everything else is working like clockwork. Thanks again for being such a terrific forum!
paulbates Posted January 4, 2016 Posted January 4, 2016 (edited) Ruth, the WAN port should only be used for a connection to the internet. Inside your house, use the LAN ports to connect devices like APs to other LAN devices so local traffic is switched from device to device. Paul Edited January 4, 2016 by paulbates
Recommended Posts