after installation of v1.1

[dagint]

I just install Snapstream version 1.1 (I had previously removed an older copy before)and when I double click the icon recieve "page cannot be displayed". I've reinstalled serveral times, ran a netstat -a -n -p tcp and found that it's listening on the correct port 127.0.0.1:8129. I am however able to hit the machine from another computer, but when I run it locally no luck... Can anyone help?

[rakeshagrawal]

try hitting http://localhost:8129/ -- some systems don't recognize the loopback address http://127.0.0.1:8129/. We switched from using http://localhost to 127.0.0.1 in the latest version b/c localhost didn't work for some but this decision just appears to have flip-flopped the problem.

So http://localhost:8129/ works -- you can favorite or create a desktop shortcut for this.

[rakeshagrawal]

...and obviously, we plan to have this fixed as soon as possible to eliminate the problem.

[dagint]

I've tried all of the ways listed and still no luck. I still get page can not be displayed. I have also check my hosts file and it does have correct information in it so localhost should work fine.

[rkuo]

Do you have any sort of software firewall or some sort of similar product installed?

[dagint]

If your question is do I have a software firewall running on my local machine then my answer would be no. I am not running anytype of security locally (no ipsec and/or IPfiltering). I am however running a linksys router for my internet connection, but that would only effect me if I was trying hit my machine externally. If I'm on the local machine attempting to get to snapstream PVS there should be no need to hit my firewall. I am still having no luck. Do you think my previous installation has anything to do with this?

[rkuo]

I'm not certain what the problem is here for you. Can you post or send us the contents of the activity log? The PVS automatically establishes a network loopback connection to itself upon startup, so if this is working, the problem must lie in your browser or somewhere along those lines.

Couple of things to try:

Different web browser.
See if you have any success looping back to yourself on another port, like port 80.