Btw i looked at other post about this problem
i have DishNET
and for the proxy text
=======================================================================
This request appears NOT to have come via a proxy.
The request appears to have originated from host dpc6935179248.direcpc.com which has ip address 69.35.179.248
The Lagado Proxy Test shows details of any proxy servers you are using. It is especially useful to expose transparent proxies. These are proxies inserted between your browser and the web, typically by your ISP, and often without you knowing.
Sometimes a proxy will be deliberately hidden so it won't be exposed by this test. In this case you can use the Cache Test to expose stealthed transparent proxy caches.
The Raw Details
Here are the raw details of the request received by this server.
Remote Host dpc6935179248.direcpc.com IP Address 69.35.179.248
Request Protocol HTTP/1.1 Method GET
Request Headers
Host
www.lagado.comUser-Agent Mozilla/5.0 (Windows NT 5.1; rv:30.0) Gecko/20100101 Firefox/30.0
Accept text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language en-us
Accept-Encoding gzip
Referer
http://forum.blockland.us/index.php?topic=245017.msg7042975Connection keep-alive
This Server Host
www.lagado.com IP Address 27.131.76.84
Date: Sunday 22 Jun 2014 12:38:56 GMT+1000
Please Note: The conclusion that the request did not come via a proxy is based on the absense of the Via, Forwarded, X-Forwarded-For and Client-ip headers. It is still possible that a proxy is handling the request without announcing itself in the recommended way. (see rfc2616 & draft-ietf-http-v10-spec-01 & Squid Configuration Guide & Squid Release Notes 1.1)
Update 08 Feb 2002 by Lagado: Added support for Client-ip header used by some transparent proxies. See more background.
Update 30 Apr 2001 by Lagado: Added Cache-Control: no-cache header to proxy-test responses. This discourages HTTP/1.1 compliant proxies from returning cached test results. Also freshened the document references.