Forum Thread: Same error with 1.9.0.4

You are currently viewing a forum thread in the Secunia Community Forum. Please note that opinions expressed here are not of Secunia but solely reflect those of the user who wrote it.

This thread was submitted in the following forum:
PSI 2.0 Beta

This thread has been marked as locked.
fulsr Same error with 1.9.0.4
Member 29th Sep, 2010 16:31
Ranking: 0
Posts: 12
User Since: 2nd Sep, 2010
System Score: N/A
Location: PT
Hello,

I was looking for my older Beta thread but it is locked, see http://secunia.com/community/forum/thread/show/535...

So i have downloaded the new Beta 2 and message is "Verifying Internet connection...". That's it, so i'm reverting to 1.5.0.2.

Best,

sneex RE: Same error with 1.9.0.4
Member 30th Sep, 2010 07:18
Score: -15
Posts: 3
User Since: 30th Sep 2010
System Score: N/A
Location: US
Yeah, I got this error until I just re-installed the Beta 2 again; who knows, maybe it's a stuck RegEdit thing ?

Anyways it seems to work more or less the same as the other beta except hopefully this version will actually update itself?

We can only hope;
-Sx-

--
:P lol?
Was this reply relevant?
+0
-0
This user no longer exists RE: Same error with 1.9.0.4
Member 30th Sep, 2010 08:49
Last edited on 30th Sep, 2010 08:50 Hi,

If you are still having the problem with the PSI being stuck at "Verifying Internet Connectivity...", please ensure that all your settings in Internet Explorer (used by the PSI to render it's user interface) match those described in this item of our FAQ:
http://secunia.com/vulnerability_scanning/personal...

If you follow the steps outlined, you should be able to run the PSI without any problems.

As the PSI is a Security Update checker, it will not automatically update itself (as there are no known security holes in any version of the PSI). The choice of whether to update to a new version or not lies with the end user.

hope this helps.
Was this reply relevant?
+0
-0
fulsr RE: Same error with 1.9.0.4
Member 30th Sep, 2010 12:34
Score: 0
Posts: 12
User Since: 2nd Sep 2010
System Score: N/A
Location: PT
Hi Emil,

By 10th time, all is per FAQ, 1.5.0.1, 1.5.0.2 have always worked, 1.9.0.3 and 1.9.04 NEVER have worked. Why?
Was this reply relevant?
+0
-0
This user no longer exists RE: Same error with 1.9.0.4
Member 1st Oct, 2010 09:29
Hi,

Do you still have version 1.9.04 on your system?

If so, could I ask you to send us a new debug report, generated in this new release?
That would certaintly help us close in on the issue.

Have you tried shutting down all Firewalls and other Security Software, and restarting the PSI? Has this changed anything?
Was this reply relevant?
+0
-0
fulsr RE: Same error with 1.9.0.4
Member 1st Oct, 2010 13:43
Score: 0
Posts: 12
User Since: 2nd Sep 2010
System Score: N/A
Location: PT
Last edited on 1st Oct, 2010 13:46
Hi Emil,

A new popup showed today, uploaded to http://lh6.ggpht.com/_jpDZE2f7Jms/TKXI_8Kdo2I/AAAA...

I'm using Windows Firewall and i have previously added PSI to the list of exceptions. I have already tried disabling it but same result. And no, i'm also not using any proxy.

I'll forward log later today.
Was this reply relevant?
+0
-0
fulsr RE: Same error with 1.9.0.4
Member 1st Oct, 2010 14:38
Score: 0
Posts: 12
User Since: 2nd Sep 2010
System Score: N/A
Location: PT
Found problem!!! I had the Workstation service disabled, no idea this was mandatory for PSI.
Was this reply relevant?
+0
-0
This user no longer exists RE: Same error with 1.9.0.4
Member 1st Oct, 2010 14:54
Last edited on 1st Oct, 2010 14:55
Was this reply relevant?
+0
-0
fulsr RE: Same error with 1.9.0.4
Member 1st Oct, 2010 15:08
Score: 0
Posts: 12
User Since: 2nd Sep 2010
System Score: N/A
Location: PT
Last edited on 1st Oct, 2010 15:09
Yes, i agree, except i disable all Windows services i don't need starting with network services since i am not in a network. This is a new PSI requirement, FAQ should be updated to reflect it, Workstation service must be set to Automatic startup since setting it to Manual causes PSI to fail. I see your debug log was also updated since this time allowed me to identify culprit in the first couple of lines. Good job :-)
Was this reply relevant?
+0
-0

This thread has been marked as locked.