This error is generated due to an internal issue on your local network. The software attempting to initiate a connection to the server decided to abort further attempts because there is essentially a backlog (traffic jam) of information trying to leave your computer.
This can be caused by stuck or hung processes that are/were still trying to communicate with the outside world. There are many possible reasons for this since the hang-up can be anywhere in your home including your Modem, Router or Computer.
The recommended troubleshooting for this is to do the following in this order, moving on to the next suggestion up until things start working again:
• Verify that you have working internet connectivity
• Close your newsreader for 2 minutes and attempt to reconnect
• Temporarily disable ALL firewalls and attempt to reconnect
• Reboot your computer and attempt to reconnect
• Shut down your newsreader, power-cycle your Router, and then attempt to connect again.
• Shut down your newsreader, power-cycle your Modem, and attempt to connect again.
You can also try the following:
1. Run the Command prompt as administrator by right-clicking on it to get that option (Start > All Programs > Accessories > Command Prompt)
2. Type in the following, and then hit enter:
netsh int ip reset
3. You should get back something that says “Resetting Global, OK! Resetting Interface, OK! Restart the computer to complete this action.”
4. Close the black command prompt window and restart the computer.
This will reset all your IP settings and should allow you to connect.
This error is generated due to an internal issue on your local network. The software attempting to initiate a connection to the server decided to abort further attempts because there is essentially a backlog (traffic jam) of information trying to leave your computer.
Quade wrote:This error is generated due to an internal issue on your local network. The software attempting to initiate a connection to the server decided to abort further attempts because there is essentially a backlog (traffic jam) of information trying to leave your computer.
The DNS error happens because Newsbin asks windows to translate the server name to the actual address and windows says "Can't do it". Now the DNS error might be a problem on your local network. In fact it's that or your DNS server but that has nothing to do with giving up on trying to make a connection. When the DNS fails, there is no attempt to connect to the server because it can't find the server's address. No DNS = no connection attempt. It's like trying to make a phone call but not knowing the number.
OK. Maybe better to use the server IP address instead in this case.
Quade wrote:OK. Maybe better to use the server IP address instead in this case.
If they only have one server. Some servers use a server farm and have multiple IP's behind the same address.
Quade wrote:Non-authoritative answer:
news.newshosting.com canonical name = usa.na.news.geo.newshosting.com
tl wrote:Using the name is the only way to get the full service, anything else means you're more likely to hit various issues. If you can't trust your ISP's DNS servers, either set up one yourself (not an option for many) or use either Google DNS or OpenDNS.
tl wrote:Actually, I need to know the server IP address for another issue; I am using a VPN but the speed maxes out at about 35 Mbps ( Image link not allowed for unregistered users ).
I am therefore bypassing the VPN by adding the newshosting server IP to the routing table. I do not think that it is possible to add the server name instead.
Error: WSASend Socket Error Code: 10058 A request to send or receive data was disallowed because the socket had already been shut down in that direction with a previous shutdown call.
Return to V6 Technical Support
Users browsing this forum: Google [Bot] and 4 guests