Кардшаринг НТВ+ на cardsharing .cc - самый надёжный и стабильный шаринг!

CardSharing Server ENG => News and announcements => Тема начата: suma от 10 Августа 2016, 18:30:12

Название: Check if your IP is blocked by the server
Отправлено: suma от 10 Августа 2016, 18:30:12
Dear subscribers,

On 9.08.2016, a possibility to check if your IP is blocked by the server has been introduced in the billing. From now on, you will be able to unblock your IP by yourself.
If you have any problem with connection and you cannot ping the server, most probably that your IP was blacklisted due to the server rule violation.
Ex., you made login or password mistake and your receiver is trying to connect the server every second using wrong data.
Or you forgot to delete old settings from receiver after your subscription is expired.
Either, receiver is connecting wrong port, wrong protocol is used, etc.
In this case, server protection is activated and IP of the abuser will be blocked.

Before unblocking your IP using the panel, you have to find out and eliminate the reason, otherwise your IP will be blocked again.
Please compare your settings to those in the billing, to those in all your receivers (if more than one). Better, delete all settings and add them again.
If your Internet provider is providing all the clients with the only IP, the reason of block can be your "guy-next-door" who is violating the rules.
In this case, request a unique external IP from the provider for yourself. There is no other way out.
To check if your IP is blocked, use cmd command ("command line" available in any Windows OS version) by typing ping server.name -t, where instead of server.name, type the real name of the server host specified in the billing ("My subscription"), ex. ping serv.99.com -t and press enter.
If you see response with response time from the server in milliseconds, it means that your IP is not blocked. If there is no response, it means that your IP is blocked or you made an error typing the server name.

Response from xxx.xxx.xxx.xxx: bytes=32 time=50ms TTL=55
Response from xxx.xxx.xxx.xxx: bytes=32 time=50ms TTL=55