New Router, Portal Does Not Work

[jgcharlotte]

I changed routers, now my portal does not work.  It is showing 'ISY Offline' and admin console is showing 'offline/registered' and 'refresh' button does nothing.  I have not found any instructions on how to re-sync the portal, only instructions on installing new.

I guess I could delete the ISY from the portal and re-install, but I assume I would have to redo all of my Echo instructions, so I don't want to do that if I don't have to!

Ideas?

 

Of course I tried rebooting the ISY

 

Thanks!

[paulbates]

Let's start by seeing if its ISY wide, or just the portal.  

• Assuming you have an NTP server configured; open the admin console, go to the configuration tab and click "Synchronize Now" under Clock.
• Try the "Test" button under Email/Groups

Did those work?

Yes-Its portal specific, I would submit a ticket to UDI for help

No- Something in the new router is not letting the ISY "dial out"

 

Paul

[jgcharlotte]

Thanks for the help!

 

Hmmm, no go (attached).

[jgcharlotte]

 Maybe DNS Relay should be enabled?

 

[paulbates]

Yes, do that. Your symptoms are network connectivity with no DNS,

 

DNS Relay causes the router to translate whatever your WAN DNS address is (like 8.8.8.8 ) to a local NAT address, like 192.168.1.1

 

Since its not checked, and the graphic in the previous post show the ISY is configured to need DNS relay, you'll need to. 

 

Paul

[jgcharlotte]

Well that didn't work after enabling it in the router, I'm rebooting ISY to make sure.

[larryllix]

In the other thread you started for this, you stated your ISY was assigned a static IP address that was not included in your router allowed IP address range.

 

If the IP address is not part of your router's LAN it will not likely route any of it's data through to the Internet.

Turn DHCP back on in your ISY and reboot it, as a trial for the portal.

 

Right now your ISY is not on your LAN sub-net and nothing should respond to it.

[paulbates]

Depending on the role of dchp you may have to reboot both. I didn't read the other thread, so not sure. It can't hurt. Router first, then ISY

 

Paul

[jgcharlotte]

I think the range is 254?  I am using 161.

 

Private Starting Address 192.168.0.  (2~254)   Number of CPEs   Public Starting Address 0.0.0.  (2~254)   Number of CPEs 

 

I was going to change to DHCP earlier, but I was worried that my Admin Console could not then find the ISY.

[paulbates]

Yeh there may be multiple things going on. The DNS relay was one them for sure. 

 

I'm also assuming that turning on relay provides the local DNS server at the router's of 192.168.1.1... is that the router's address?

 

Go to a window computer, open a command window and type in ipconfig... check the gateway and dns addresses provided.. the ISY's should be the same

 

Paul

[paulbates]

Ok, I see what Larry is saying, this the other problem

 

Where you have 192.168.x.y  :

Right now, x=1

In the ISY, change x=0

 

Paul

[jgcharlotte]

attached

[jgcharlotte]

Ok it's rebooting now.

[paulbates]

ok, the pictures suggest that changing the 3rd octet from 1 to 0 should make it work. There was no route to the internet for 192.168.1.y

 

Paul

[jgcharlotte]

ok but now I can't get in to admin console

[paulbates]

The router may have the ISY's mac address at the old IP stuck in ARP. Unplug them both for ~2 minutes. Bring the router up first, wait 2 more minutes, then plug in ISY. I think you are very close

 

Paul

[jgcharlotte]

LOL I hope so.

[jgcharlotte]

It looks like it still is not working, can't get in to the console now.  It comes up with that ISY finder, hit 'add' it asks me for URL, I type in the URL listed and it doesn't do anything.  I guess I'm not doing something right there.

[jgcharlotte]

I have to go out, feel free to leave more suggestions    You guys are great, thanks for the help.  It's probably something simple.

[paulbates]

Assuming you kept 192.168.0.161 as the address (and nothing else randomly picked up that address)

add this to the finder

 

http://192.168.0.161/desc

[jgcharlotte]

Tried that, it didn't seem to do anything, maybe I'm not using the finder right.   Am I supposed to save it?

[paulbates]

Can you ping 192.168.0.161 from your windows system?

 

Does the new router provide a table of connected clients with IPs, usually you can find the ISY there

 

Paul

[larryllix]

From the other thread:

 

Thanks,

The static IP I'm using is 161, so it is well out of the range DHCP would assign.

I'd actually rather get the portal working on the new router, I did this cause the old one already worked.  But I don't want to cause more problems.

I'm just not sure what needs to be done there.

I noticed upnp was disabled in the new router.  Wondering if that would affect the portal interface.

 

 

 

I guess I don't understand the purpose or the point of the ISY finder applet but in three years of using ISY the finder has never found my ISY yet, and tried on many different computers. 

 

I have always had to manually add my ISY's IP address to the Finder. Then, if there are two possible addresses listed I have to manually select one every time to load the admin console.

[stusviews]

From the other thread:

 

 

 

I guess I don't understand the purpose or the point of the ISY finder applet but in three years of using ISY the finder has never found my ISY yet, and tried on many different computers. 

 

I have always had to manually add my ISY's IP address to the Finder. Then, if there are two possible addresses listed I have to manually select one every time to load the admin console.

 

That's exactly the purpose of the finder. If you have more than one ISY, how else could you select which one you wanted to access? You can also use the finder to choose between http and https if you have both configurations.

 

But, you shouldn't have to add an address manually each time.

[mwester]

If the finder can't find your ISY, then something is wrong with your network (unless of course, you deliberately and knowingly configured your network in such a fashion to disallow the finder the ability to find your ISY).  Start by turning off all the firewalls and antivirus and antimalware and anti-this-or-that-posing-as-security-ware software -- if that doesn't help, then you probably have disjoint subnets (multiple routers/firewalls) or you have subnet problems (router mis-configuration or host PC mis-configuration).