jdva Posted November 10, 2007 Share Posted November 10, 2007 I just recieved my ISY-26 and I am anxious to make it work but I can't login. It seems to get an IP address just fine. It appears in My Network Places. The application runs and I get a login prompt. However, everytime I try to login (using amdmin,admin) it says "Negotiating Keys" and then I get this error: "Socket Open Failed java.lang.NullPointerException" I have unistalled the java jre and reinstalled from the supplied disk. I have tried it in both IE7 and FireFox I have even tried to login from another machine. I ran the serial console and did a hard reset. I am apparently communicating with it because when I try to login with the console open it displays this: http://192.168.1.9:16613/> H_ERROR:-13000 : H_ERROR:-5015 : LOGGER:-13000 : n=[null] c=[null] a=[null] LOGGER:-5015 : n=[null] c=[null] a=[null] H_ERROR:-10061 : LOGGER:-10061 : n=[null] c=[null] a=[null] H_ERROR:-10061 : LOGGER:-10061 : n=[null] c=[null] a=[null] However, nothing has worked! I can't tell if it's the ISY or my PC but I have tried so many different PC configurations I am thinking its the ISY. I purchased the unit refurbished because that was all that was available, I hope that wasn't a mistake? Please help? Thanks, -jd Link to comment
jdva Posted November 10, 2007 Author Share Posted November 10, 2007 Just some additional info... I have also disabled my windows firewall and virus protection. No change! -jd Link to comment
jdva Posted November 10, 2007 Author Share Posted November 10, 2007 even more info... Java logging on the client shows this as the exception: network: Cache entry found Exception occurred during event dispatching: java.lang.NullPointerException at com.universaldevices.upnp.UDProxyDevice.expireSessionKeys(Unknown Source) at com.universaldevices.ui.security.UserCredentialOperations.ok(Unknown Source) at com.universaldevices.ui.security.UserCredentialOperations.ok(Unknown Source) at com.universaldevices.dialog.UDDialog.actionPerformed(Unknown Source) at javax.swing.AbstractButton.fireActionPerformed(Unknown Source) at javax.swing.AbstractButton$Handler.actionPerformed(Unknown Source) at javax.swing.DefaultButtonModel.fireActionPerformed(Unknown Source) at javax.swing.DefaultButtonModel.setPressed(Unknown Source) at javax.swing.plaf.basic.BasicButtonListener.mouseReleased(Unknown Source) at java.awt.Component.processMouseEvent(Unknown Source) at javax.swing.JComponent.processMouseEvent(Unknown Source) at java.awt.Component.processEvent(Unknown Source) at java.awt.Container.processEvent(Unknown Source) at java.awt.Component.dispatchEventImpl(Unknown Source) at java.awt.Container.dispatchEventImpl(Unknown Source) at java.awt.Component.dispatchEvent(Unknown Source) at java.awt.LightweightDispatcher.retargetMouseEvent(Unknown Source) at java.awt.LightweightDispatcher.processMouseEvent(Unknown Source) at java.awt.LightweightDispatcher.dispatchEvent(Unknown Source) at java.awt.Container.dispatchEventImpl(Unknown Source) at java.awt.Window.dispatchEventImpl(Unknown Source) at java.awt.Component.dispatchEvent(Unknown Source) at java.awt.EventQueue.dispatchEvent(Unknown Source) at java.awt.EventDispatchThread.pumpOneEventForFilters(Unknown Source) at java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source) at java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source) at java.awt.Dialog$1.run(Unknown Source) at java.awt.event.InvocationEvent.dispatch(Unknown Source) at java.awt.EventQueue.dispatchEvent(Unknown Source) at java.awt.EventDispatchThread.pumpOneEventForFilters(Unknown Source) at java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source) at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source) at java.awt.EventDispatchThread.pumpEvents(Unknown Source) at java.awt.EventDispatchThread.pumpEvents(Unknown Source) at java.awt.EventDispatchThread.run(Unknown Source) Link to comment
jdva Posted November 10, 2007 Author Share Posted November 10, 2007 Update: I have successfully logged into the device. I had to go to the console configuration and fix the IP address as opposed to what was provided through DHCP. Not sure why? If you have any ideas I would appreciated it. Thanks, -jd Link to comment
Mark Sanctuary Posted November 10, 2007 Share Posted November 10, 2007 Good to hear you got logged in. If you can't get logged in sometimes the web links work better. Also sometimes clearing the web browser cache helps get rid of any stale ISY java code. Non-beta Link: http://www.universal-devices.com/MyInsteonISY/ Beta Link: http://www.universal-devices.com/beta/ Link to comment
Michel Kohanim Posted November 11, 2007 Share Posted November 11, 2007 jd, Do you have McAfee installed by any chance? With kind regards, Michel Update: I have successfully logged into the device. I had to go to the console configuration and fix the IP address as opposed to what was provided through DHCP. Not sure why? If you have any ideas I would appreciated it. Thanks, -jd Link to comment
Sub-Routine Posted November 11, 2007 Share Posted November 11, 2007 I have McAfee and have never had to disable it. jdva wrote:Very Happy Update: I have successfully logged into the device. I had to go to the console configuration and fix the IP address as opposed to what was provided through DHCP. Not sure why? If you have any ideas I would appreciated it. Thanks, -jd I am thinking router trouble. Sometimes a restart of the router can fix things. I'm glad you got past it. So now that you are in, What do you think of the ISY-26? I was very surprised! Rand Link to comment
Michel Kohanim Posted November 12, 2007 Share Posted November 12, 2007 Hi Rand, Long time no see! I am very much surprised that you have not had any issues with McAfee. Is it an older version? Thanks so very much, With kind regards, Michel I have McAfee and have never had to disable it. jdva wrote:Very Happy Update: I have successfully logged into the device. I had to go to the console configuration and fix the IP address as opposed to what was provided through DHCP. Not sure why? If you have any ideas I would appreciated it. Thanks, -jd I am thinking router trouble. Sometimes a restart of the router can fix things. I'm glad you got past it. So now that you are in, What do you think of the ISY-26? I was very surprised! Rand Link to comment
Sub-Routine Posted November 12, 2007 Share Posted November 12, 2007 Hello Michel, Yes it has been a long time. No news = good news I am using the latest McAfee (updated this morning) but it is not the AOL McAfee, or the Comcast McAfee, or any other * McAfee. I use the McAfee McAfee, if that makes a difference. Thank you, Rand Link to comment
Michel Kohanim Posted November 12, 2007 Share Posted November 12, 2007 Hi Rand, Yes, indeed no news = good news. Have you tried upgrading your ISY lately using your McAfee? I am quite certain you're going to get "Invalid Length" ... Please do let me know if/when you do, As always, with kind regards, Michel Hello Michel, Yes it has been a long time. No news = good news I am using the latest McAfee (updated this morning) but it is not the AOL McAfee, or the Comcast McAfee, or any other * McAfee. I use the McAfee McAfee, if that makes a difference. Thank you, Rand Link to comment
tabraham Posted November 17, 2007 Share Posted November 17, 2007 I'm having the same issue. I just received my ISY from Smarthome today. Windows XP Pro SP2, Norton Internet Security 2008. I can telnet into the ISY just fine, UPnP is fine and the app opens up, but admin/admin login just results in NullPointerException Socket Closed. I have tried disabling all Norton protection to no avail. Perhaps I will also have to try fixing the IP address in the ISY. Thanks, Tom Link to comment
tabraham Posted November 17, 2007 Share Posted November 17, 2007 Just as jdva reported, when I switched the ISY to a static IP address, suddenly I can connect through the app just fine. Any ideas as to why a DHCP-provided address doesn't work? It doesn't make much sense. Link to comment
Michel Kohanim Posted November 18, 2007 Share Posted November 18, 2007 tabraham, With sincere apologies for a tardy repsonse. This is indeed strange. We could've passed jdva's sypmtoms as one of a kind but now that we have two cases reported, we are going to do a root cause analyis. Thanks so very much for bringing this to our attention, With kind regards, Michel Just as jdva reported, when I switched the ISY to a static IP address, suddenly I can connect through the app just fine. Any ideas as to why a DHCP-provided address doesn't work? It doesn't make much sense. Link to comment
Sub-Routine Posted November 18, 2007 Share Posted November 18, 2007 Not that it helps with the DHCP problem but, Hi Rand, Yes, indeed no news = good news. Have you tried upgrading your ISY lately using your McAfee? I am quite certain you're going to get "Invalid Length" ... Please do let me know if/when you do, As always, with kind regards, Michel Hello Michel, Yes it has been a long time. No news = good news I am using the latest McAfee (updated this morning) but it is not the AOL McAfee, or the Comcast McAfee, or any other * McAfee. I use the McAfee McAfee, if that makes a difference. Thank you, Rand Updated to 2.4.15 14-Nov-07, no problemo Keep up the good work! Rand Link to comment
Michel Kohanim Posted November 18, 2007 Share Posted November 18, 2007 Hi Rand, That's totally unbelievable but I am so glad that it works. Thanks so very much for the update, With kind regards, Michel Not that it helps with the DHCP problem but, Hi Rand, Yes, indeed no news = good news. Have you tried upgrading your ISY lately using your McAfee? I am quite certain you're going to get "Invalid Length" ... Please do let me know if/when you do, As always, with kind regards, Michel Hello Michel, Yes it has been a long time. No news = good news I am using the latest McAfee (updated this morning) but it is not the AOL McAfee, or the Comcast McAfee, or any other * McAfee. I use the McAfee McAfee, if that makes a difference. Thank you, Rand Updated to 2.4.15 14-Nov-07, no problemo Keep up the good work! Rand Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.