No connection to Snapstream..

[flavius]

Don't read any further - if you can't stand anger and graphic language ..

I get the message "Setup Wizard failed to detect active internet connection. You must be connected to the internet to complete the SnapStream.Net portion of the Setup Wizard.

This happens with 3.3, 3.4 and 3.5. When you search the forum, you'll find several posts ..

Well, I read all that stuff . I'm really starting to pull my hair here. I've been installing this - how many times now? And the deeper I look into this, the less appealing it becomes. Do you guys have any idea how many registry keys there are? And how many of them the so-called 'complete' uninstall removes?

Of, course I have a working direct internet connection.

I'm getting really pissed here. I'm one inch away from throwing this piece of s$$$ out of the window.

[jkoon]

Do you have any firewall software installed?

And have you checked your system for spyware and whatnot?

[flavius]

Firewall is disabled. No spyware. HP network tool is telling everything is fine. Every other program has network access.

[RobertH]

If you open internet explorer and visit:
http://wsdl.snapstream.net
and
https://wsdl.snapstream.net
what do you see?

in your hosts file (c:\windows\system32\drivers\etc\hosts, you can open this with notepad) the only thing should be a bunch of lines starting with # and one that has:
127.0.0.1 localhost
on it, if there is anything else something has hijacked your network stack.

you should also try running the following tool:
http://tntmax.com/Download/Software/...XPFix.exe/view
it will repair the windows network stack after crapware, spyware, some firewalls, and other things have broken it

and by the way, do not curse on these forums

[flavius]

I see a snapstream logo twice. The software did not fix it. -"Try again.."
Why is there not a single message in the log?- Without network access it's useless.

Amateurs.

[flavius]

Resolved.- After removing all .NET stuff from the machine, BTV 3.5 reloaded the stuff it needs.

That should be put into the FAQ "Things you can do before you jump out of the window.."

[Grasshopper]

I moved BTV from one machine to another and now I am having this same problem. I searched and saw some people managed to fix this but I have not. Please help!

I have a fresh install of XP Pro with all of the latest updates. Snapstream is the first app I've tried to install so I doubt there is any corruption in .NET or the TCP/IP stack. Firewall is turned off. No antivirus software installed. Nothing special done on the router config. (Do I need to open any specific ports?) All other apps see the Internet just fine. I'm using BTV 3.5.3.

I've been using BTV for over a year and had zero problems up to now.

[beverlyjc]

I had a similar problem and was going crazy trying to solve it. One minute everything worked, then the next- no connection. It turned out to be a patch for microsoft net framework that was messing everything up. Once I uninstalled the patch everything worked again. Hope this info helps someone.

beverlyjc

[Grasshopper]

Well this is driving me nuts. I've tried everything I can think of:

- Three different versions of BTV (3.5.1, 3.5.3, latest beta)
- Tried uninstalling BTV and everything .NET and reinstalling. I tried it with all the .NET updates and I tried it after successively installing .NET updates.
- Checked to make sure there are no viruses (viri?) and spyware.
- Removed all virus scanners and anti-spyware scanners.
- Opened all ports on the router.
- Disabled Windows firewall.

I know I have a good internet connection as I can browse the web, download, and access www.snapstream.net with no problem.

I noticed that when installing .NET Windows does not always re-download the install files. I am assuming if it finds them in it's cache it just uses what it finds. How can I clear the download cache? (Maybe there is a corrupt install file on my drive that keeps getting re-installed.)
Any help, or even wild guesses, appreciated.

[Grasshopper]

I've been working with Snapstream support on this and they now tell me that the error is occuring somewhere in MFC. Any ideas on how to re-install this Windows component?