Quote:
Originally Posted by toryglen-boy
Hi Peter, i must admit i am confused.
Vista used an IPv6 address (although "4" could be selected) and Windows 7, will very probably need 2 use an IPv6 address.
Your infomation shows that none of your interfaces have an IP address assigned, there are a few things you could try, although you probably already have!
assigning a manual IP address? You said when you connect online, you get an IP address thats static, is it really static? or is the DHCP lease on the address still current?
flushing the DNS cache from a DOS prompt, so its forced to renew DNS entries?
soz to not offer more, i am unfamiliar with the software, or what your trying to do, if you can post more background on here, then i will endeavour to help
 |
Hi Duncan,
Thanks for the quick reply. The IP address when online changes so its dynamic I guess.
The best background I can give - Fire up the Sky6, connect to the telescope. Create a script of galaxies in The Sky6 I want to image then export them into Orchestrate (another Software Bisque programme). Open Orchestrate - create a new file and then paste the exported data I got from The Sky6 into it. From here under Windows XP it was simply a matter of going into the connection drop down menu in Orchestrate and clicking on "link to the SKY6" (and the scope and the camera). This would then mean I could just click start in Orchestrate and the programme would slew the telescope to each galaxy as per the script written.
When I do the drop down "connect" in Orchestrate using Vista or Win 7 I get an error message noting " error connecting to the sky address family not supported by protocol family" with some various error codes, this is what the internal IPV4 address typed into client in Orchestrate is supposed to fix according to Software Bisque.
Now with (and previously Vista) Win7 seems I have to enter a client into Orchestrate as per SB instruction in my first post.
By the way another member, Thunderchild also familiar in using The Sky6 and Orchestrate tried the same and got the same error message.
I don't know if this helps but I sure appreciate any assistance.
PeterM.