Howdy,
A month or so ago my sab stopped working. I says it can't connect to the usenet server. I'm using that free one that requires you be on IPv6 in order to use it: ipv6.xsnews.nl.
It had always worked fine and I didn't change anything on my PC but now it's not working.
I anyone else using this host and is it working for you? If so, can anyone give me ay tips on what might have happened to my setup to make the ipv6 stop working? I'm using Windows 7 which has something built in to make ipv6 work that I had to tinker with to get running a long time ago. I just don't recall what that was or how to test it.
OR, does anyone know of ay other usenet server that's free that I could try using instead?
Thanks!!
NewsServer problem - ipv6.xsnews.nl
Forum rules
Help us help you:
Help us help you:
- Are you using the latest stable version of SABnzbd? Downloads page.
- Tell us what system you run SABnzbd on.
- Adhere to the forum rules.
- Do you experience problems during downloading?
Check your connection in Status and Interface settings window.
Use Test Server in Config > Servers.
We will probably ask you to do a test using only basic settings. - Do you experience problems during repair or unpacking?
Enable +Debug logging in the Status and Interface settings window and share the relevant parts of the log here using [ code ] sections.
Re: NewsServer problem - ipv6.xsnews.nl
What does test-ipv6.com tell about your ipv6 .....
Re: NewsServer problem - ipv6.xsnews.nl
When I use that test site it tells me I don't have ipv6,
Ipconfig shows me I have a link-local ipv6 address. Not sure what would have changed.
Any good tutorials on how to get this working again? I'm on Windows 7 via Roadrunner if that matters.
Ipconfig shows me I have a link-local ipv6 address. Not sure what would have changed.
Any good tutorials on how to get this working again? I'm on Windows 7 via Roadrunner if that matters.
Re: NewsServer problem - ipv6.xsnews.nl
Read my thread on tereo miredo.
The usual suspect is a non-microsoft firewall and virus scanner.
The usual suspect is a non-microsoft firewall and virus scanner.