Can't Log Into ISY

[Crusty]

I've had it up and running for just a few months, and frankly have only done a minimal amount with it. A couple of basic programs - that's it.

 

Last night, I wanted to log in to check why a specific light didn't come on. I'm not sure what happened, but it kept asking me for the log in authentication over and over. I got distracted by something else and just closed it out. Never did log in successfully.

 

Tonight, I notice that one of the nightly programs did not run properly. One did, another didn't. I tried to log in again to see what's happened. I can't log in. I've never changed the default log-in, but now it won't take it. Keeps coming back and asking for authentication over and over.

 

I also note that in seeing the screen display of the program, there is no status noted for any of my devices. Maybe it has to see a correct log-in before posting that. I never paid attention to that detail before.

 

Anyway, I can't log in and it's driving me nuts. I tried pulling the power for a few seconds and re-booting. Seemed to come back normally. I know I must have the right ID and password, because if I intentionally put the wrong one in, I get a failure notice.

 

Any idea what's going on?

[Crusty]

I have to modify what I said above after playing with it for a bit more.

 

It seems that I'm logging in just fine. After the ID and password window clears, the normal screen starts to load, and I see all my devices. But there is nothing listed for any of them under current status. Then, about 15-20 seconds passes, and the authentication window pops up again. I don't have to re-enter my ID and password, as they are already there. If I click "Ok" on that window, it clears, nothing changes regarding the current status column, and the authentication window comes back again in another 15-20 seconds. I can never get past that.

 

I tried re-loading Java to see if it might be that - no joy there.

 

Any other ideas?

[Crusty]

Looks like I've discovered the problem - it's obviously a Java issue on one of my PC's.

 

I fired up an old notebook I rarely use this morning to check this issue, and sure enough, on that platform everything looks fine. No issue with the ISY.

 

So now on to figuring out how to solve the Java problem. Oh joy!

[Crusty]

Sorry to be continuing this issue, but an update...

 

I uninstalled and then re-installed Java. Still have the same problem.

 

I note that my older computer is running version 6 update 26, while my newer PC is running update 27.

 

Any known issues with update 27? Or should I look elsewhere to fix this?

[TJF1960]

Hello Crusty,

 

Please, don't be sorry. I am surprised no one has replied yet.

 

I know very little about troubleshooting the issue you are having. However I have been around for a few years and the question of "what firewall or antivirus software are you running" seems to always come up. Also what ISY99 firmware version is installed?

 

Tim

[Brian H]

Update 27 must be very recent. On 09/09/2011 my check for Java updates didn't find 27 and said 26 was the latest.

So no one else may have tried 27 yet.

I have 26 and as you found. Working OK.

 

Gee in another thread someone found the newest Avast Update, released recently, also was causing problems.

[Crusty]

Gee in another thread someone found the newest Avast Update, released recently, also was causing problems.

BINGO! That's the winner.

 

Credit to TJF1960 for suggesting antivirus as well.

 

As it turns out, Avast had an update a few days ago, and something in that created a port problem that was the root of all this. I got on with their tech folks and clear it up.

 

So Java update 27 seems fine - it was all the anti-virus' fault

 

If anyone needs an explanation of the steps required to fix this, I'd be happy to provide.

[Brian H]

OK thanks for the update.

I can now allow Java to update and tell Avast to hold off. Until data on how to correct it is avilable.

 

Yes please share. Maybe in the Avast Thread as it relates to the problem.

[northportphoneguy]

Hi,

I had the other thread with the Avast problem. Would love to know what Avast techs had as an explaination.

[Crusty]

Sorry it took me a few days to come back to this and provide the info about how to adjust Avast to fix this problem.

 

For definition's sake, I'll summarize the issue: a recent update (early Sept, 2011) of Avast anti-virus has created a port problem in accessing the ISY's functions. You can log in - sort of - but are unable to see the current status of any devices and the authentication window keeps popping back up over and over.

 

Here's the fix...

 

-- Open the main Avast program window

 

-- Click on "Settings" in the upper right to bring up that window

 

-- Click on "Troubleshooting" (last item in the list), and open the "Redirect Settings" area

 

-- Delete any port numbers or addresses in both the "Web" and "Mail" sections of the window. All areas should be blank and nothing checked.

 

-- In the same "Settings" window, click on the "Update" option

 

-- Open the "Proxy Settings" portion of the window

 

-- Select the "Direct Connection (no proxy)" radio button

 

-- Click "Ok"

 

 

That should fix it. If by chance you notice that the main window tells you your system is now un-secure after making these changes, you can turn security back on from that same main window (look in the "Summary" section). Doing so won't un-do the port changes you just made.

 

Now obviously, if someone has any of these specific options set to something important for their system for whatever purpose, you should be careful about using these instructions as it might harm other functions. In my case, I had never touched these things in the past, and they were set to whatever Avast had set them to. If you've done something different, you mileage may vary - a lot.

 

Good luck with this. It worked for me and I hope it does for you.

[Brian H]

Thanks for their fix.

 

I did the following.

It seemed to fix my problems.

 

Though in my case the Authentication request didn't keep popping up.

Status updates and real time things like Queries and link database reads where not there.

 

viewtopic.php?f=3&p=52927

[johnnyt]

what's the security implication of this on the rest of my surfing and emailing, etc.?

[brookbphx]

While the above suggestions do resolve the problem on not being able to correctly communicate with the ISY from your computer, the security implications of removing all of the port numbers in Avast are pretty severe. Basically, those are the standard web page and email ports. If you remove those ports from the list on this page, Avast will not scan them. In other words, you are basically disabling Avast scanning for all of your web and email surfing. You may think Avast Web Shield is working, because Avast says it is "Enabled". However, it is enabled and checking NOTHING. Removing the ports defeats the whole purpose of the Web Shield. You want to disable Avast Web Shield checking for communications between your computer and the ISY - but NOT between your computer and the entire internet.

 

Here's a way to get the ISY interface to work without breaking the security provided by Avast Web Shield. (At least this worked for me)

 

In Avast, click on "Settings" in the upper right corner. A new window will pop up. Select the "Troubleshooting" item at the bottom of the list on the left. Now, click the down arrow next to "Redirect Settings".

 

Under Settings->Troubleshooting->Redirect Settings:

 

[*] Put the IP address of your ISY-99 in the Ignored Addresses field under the WEB heading. Leave Ignored addresses blank for MAIL. (Note: you need to set up the ISY and/or your DHCP server in your router to always assign the same address to the ISY so that this address will always be correct).

[*] If you previously cleared the Port numbers for HTTP ports, put them back. The defaults are: 80,8080,8091,8081,8008,8888,3124,3127,3128. This will restore the Avast web shield scanning security for web browsing on the standard WWW ports.

[*] If you previously cleared the Port numbers for Mail ports, put them back. The defaults are: SMTP:25,587; POP:110; IMAP:143; NNTP:119 . This will restore the Avast web shield scanning security for email if you use a web application (such as Outlook or Outlook Express) on the standard Mail ports.

[*] Click "OK"

 

Under Settings->Updates->Proxy Settings

 

[*] If you previously changed the proxy settings per the above suggestions to "Direct Connection (No Proxy)", you may choose to set it back to the default of "Auto detect (use Internet Explorer settings)". However, most people do not use proxies. So if you leave it set to Direct, chances are everything will still be OK.

[*] Click "OK"

 

If you still can't see the status updates on the UD Admin Console after making these changes, shut down and restart the Admin Console. You may also want to stop and restart the Avast Web Shield.

[Michel Kohanim]

Hello brookbphx,

 

Just wanted to send you a personal thank you as Avast has been a nightmare for us to deal with.

 

I really do appreciate it.

 

With kind regards,

Michel

[kaisersoze]

I use Avast and I don't feel comfortable completely disabling the scanning feature permanently. My solution is to temporarily stop the real-time web shield. If you open up Avast, click Real-Time Shields, click Web Shield, click Stop and select the time frame you will be accessing the ISY from your computer. I usually pick 10 minutes, occasionally the 1 hour option. This eliminates mucking around with the ports and the web shield automatically turns back on if I forget to re-enable it.