Error code: POL-0011

Printable View

04-12-2012, 04:43 PM
Daniel_Hatcher

Error code: POL-0011

Details: Upon logging in I receive the error:

Quote:

Error code:POL-0011
The network is busy or there is no response from the server. please try again later or verify cables, networking devices, and networking settings are properly configured.

Steps:
1. Login!
2. Receive error.
3. Reboot Modem.
4. Receive error.
5. Check firewall settings.
6. Receive error.

Date & Time: 08:40 AM GMT (12 April 2012)

Frequency:All the time

Platform: Windows

PC Manufacturer & Model Number: Dell Studio 17

OS: Windows 7

Graphics Card: ATI

ISP: BT

Type of Internet Connection: BroadBand
04-21-2012, 05:28 PM
CPBismarck

your not alone, i have the same issue another thread with multiple people complaining to have same issue also. its BS and if this isnt resolved imma request my bank takes the money i paid this month back as fraud. this is ludicrous. they dont give a rats monkeys ass and just ignore the rest of us having problems!
04-22-2012, 07:17 PM
RAIST

Quote:

Originally Posted by CPBismarck

your not alone, i have the same issue another thread with multiple people complaining to have same issue also. its BS and if this isnt resolved imma request my bank takes the money i paid this month back as fraud. this is ludicrous. they dont give a rats monkeys ass and just ignore the rest of us having problems!

The issue appears to be localized to either one ISP or one region--not necessarily something SE has control over. I've had routing issues in the past and after tracing and working with my South East regional offices for my ISP, we found it was a failing segment in VA one time, and another time in Nova Scotia.....segments managed by someone else entirely. SE is not responsible for problems that may be occuring at the 13th to 18th hop from your PC that is managed by Verizon or some other entity not affiliated with SE.
04-23-2012, 07:48 PM
CPBismarck

As i have in another post i will here and appologise in my outburst to SE (more out of frustrtion). The problem in fact does rest upon your ISP in my case BE and if your with O2 they rent their servers from BE so your in the same boat.

However that doesnt change the fact that a SE member could have come here and said exactly what your saying Raist. Not everyone knows how to do a tracert to check if the IP to SE can be reached. Not saying SE has to teach people how to do it but a simple forwarding statement explaining the problem isnt theirs and its the ISP thats the issue would be something. Instead they decided to sit there and ignore whats happening. So yeah as i stated im sorry for my outburst, its not a SE problem but their CS department needs some work...