Får ikke spillt online-spill

[Estra]

Når jeg er hjemme på besøk hos min mor får jeg ikke logget inn på hverken World of Warcraft,

League of Legends og andre online spill.

Får heller ikke kontakt med FTP eller p2p!

 

Har prøvd med port forwarding og godkjenning av visse programmer på firewall-instillingene

Vurderer å tro at IPS har blocka det, siden alt jeg har prøvd ikke fungerer! -_-

 

 

Major Abnormalities

 

It appears there was a significant problem with Netalyzr's execution in this run, as it was not able to look up the name of our server and/or generate connections to our server. As a result, the following results should be considered unreliable.

 

Our first suggestion is to quit your web browser and try again. If that fails, please contact us and we will attempt to diagnose and debug the problem. Thanks, and sorry for the inconvenience.

 

Minor Aberrations

 

* Certain TCP protocols are blocked in outbound traffic

 

Major Abnormalities

Minor Aberrations

Address-based Tests +

NAT detection (?): Failed

 

One of the connections to our server did not receive the expected data.

Local Network Interfaces (?): OK

Your computer reports the following network interfaces, with the following IP addresses for each one:

 

* :

 

DNS-based host information (?): OK

You are not a Tor exit node for HTTP traffic.

You are not listed on any Spamhaus blacklists.

The SORBS DUHL believes you are using a dynamically assigned IP address.

NAT detection (?): Failed

Local Network Interfaces (?): OK

DNS-based host information (?): OK

Reachability Tests –

TCP connectivity (?): Note

 

Direct TCP connections to remote FTP servers (port 21) failed.

 

This is commonly due to how a NAT or firewall handles FTP traffic, as FTP causes unique problems when developing NATs and firewalls.

Direct TCP access to remote SSH servers (port 22) is blocked.

 

Direct TCP access to remote SMTP servers (port 25) is prohibited.

 

This means you cannot send email via SMTP to arbitrary mail servers. Such blocking is a common countermeasure against malware abusing infected machines for generating spam. Your ISP likely provides a specific mail server that is permitted. Also, webmail services remain unaffected.

 

Direct TCP access to remote DNS servers (port 53) is blocked.

 

The network you are using appears to enforce the use of a local DNS resolver.

Direct TCP access to remote HTTP servers (port 80) is allowed.

Direct TCP access to remote POP3 servers (port 110) is allowed.

 

Direct TCP access to remote RPC servers (port 135) is blocked.

 

This is probably for security reasons, as this protocol is generally not designed for use outside the local network.

 

Direct TCP access to remote NetBIOS servers (port 139) is blocked.

 

This is probably for security reasons, as this protocol is generally not designed for use outside the local network.

Direct TCP access to remote IMAP servers (port 143) is allowed.

 

Direct TCP access to remote SNMP servers (port 161) is blocked.

 

This is probably for security reasons, as this protocol is generally not designed for use outside the local network.

Direct TCP access to remote HTTPS servers (port 443) is allowed.

 

Direct TCP access to remote SMB servers (port 445) is blocked.

 

This is probably for security reasons, as this protocol is generally not designed for use outside the local network.

Direct TCP access to remote SMTP/SSL servers (port 465) is blocked.

Direct TCP access to remote secure IMAP servers (port 585) is blocked.

Direct TCP access to remote authenticated SMTP servers (port 587) is blocked.

Direct TCP access to remote IMAP/SSL servers (port 993) is blocked.

Direct TCP access to remote POP/SSL servers (port 995) is blocked.

Direct TCP access to remote OpenVPN servers (port 1194) is blocked.

Direct TCP access to remote PPTP Control servers (port 1723) is blocked.

Direct TCP access to remote SIP servers (port 5060) is blocked.

Direct TCP access to remote BitTorrent servers (port 6881) is blocked.

Direct TCP access to remote TOR servers (port 9001) is blocked.

UDP connectivity (?): OK

 

We are unable to deliver non-DNS UDP datagrams to our servers.

Possible reasons include a restrictive Java security policy, a blocking rule imposed by your firewall or personal firewall configuration, or filtering performed by your ISP. Although it means we cannot conduct the latency and bandwidth tests, it does not necessarily indicate a problem with your network.

Traceroute (?): Not Executed

The test was not executed. Required functionality was unavailable or not permitted.

Path MTU (?): Not Executed

The test was not executed. Required functionality was unavailable or not permitted.

TCP connectivity (?): Note

UDP connectivity (?): OK

Traceroute (?): Not Executed

Path MTU (?): Not Executed

Network Access Link Properties +

Network latency measurements (?): Prohibited

The applet was not permitted to run this test in its entirety. We encourage you to re-run the applet, allowing it to conduct its tests if prompted. However, some system configurations will always block this test. See the corresponding FAQ for help.

TCP connection setup latency (?): 100ms

The time it takes your computer to set up a TCP connection with our server is 100 msec, which is good.

Network background health measurement (?): Not Executed

The test was not executed. Required functionality was unavailable or not permitted.

Network bandwidth measurements (?): Not Executed

The test was not executed. Required functionality was unavailable or not permitted.

Network buffer measurements (?): Not Executed

The test was not executed. Required functionality was unavailable or not permitted.

Network latency measurements (?): Prohibited

TCP connection setup latency (?): 100ms

Network background health measurement (?): Not Executed

Network bandwidth measurements (?): Not Executed

Network buffer measurements (?): Not Executed

HTTP Tests +

Address-based HTTP proxy detection (?): OK

There is no explicit sign of HTTP proxy use based on IP address.

Header-based HTTP proxy detection (?): OK

No HTTP header or content changes hint at the presence of a proxy.

HTTP proxy detection via malformed requests (?): OK

Deliberately malformed HTTP requests arrive at our server unchanged. Thus, the proxies along your path are able to transparently forward invalid HTTP traffic.

Filetype-based filtering (?): OK

We did not detect file-content filtering.

HTTP caching behavior (?): OK

There is no suggestion that a transparent HTTP cache exists in your network.

JavaScript-based tests (?): OK

The applet was not run from within a frame.

Your web browser reports the following cookies for our web page:

 

* netAlizEd = BaR (set by our server)

* netalyzrStatus = running (set by our server)

 

Your web browser was unable to fetch an image using IPv6.

Address-based HTTP proxy detection (?): OK

Header-based HTTP proxy detection (?): OK

HTTP proxy detection via malformed requests (?): OK

Filetype-based filtering (?): OK

HTTP caching behavior (?): OK

JavaScript-based tests (?): OK

DNS Tests +

Restricted domain DNS lookup (?): OK

We can successfully look up a name which resolves to the same IP address as our webserver. This means we are able to conduct many of the tests on your DNS server.

Unrestricted domain DNS lookup (?): OK

We can successfully look up arbitrary names from within the Java applet. This means we are able to conduct all test on your DNS server.

Direct DNS support (?): Not Executed

The test was not executed. Required functionality was unavailable or not permitted.

Direct EDNS support (?): Not Executed

The test was not executed. Required functionality was unavailable or not permitted.

DNS resolver address (?): OK

The IP address of your ISP's DNS Resolver is 193.213.112.71, which resolves to ns12-1.e.nsc.no. Additional nameservers observed for your host: 193.213.112.73

DNS resolver properties (?): Lookup latency 229ms

Your ISP's DNS resolver requires 229 msec to conduct an external lookup. It takes 160 msec for your ISP's DNS resolver to lookup a name on our server.

Your resolver correctly uses TCP requests when necessary.

Your resolver is using QTYPE=A for default queries.

Your resolver is not automatically performing IPv6 queries.

Your DNS resolver requests DNSSEC records.

Your DNS resolver advertises the ability to accept DNS packets of up to 4096 bytes.

Your DNS resolver can successfully receive a smaller (~1400 byte) DNS response.

Your DNS resolver can successfully receive a large (>1500 byte) DNS response.

Your DNS resolver can successfully accept large responses.

Your resolver does not use 0x20 randomization, but will pass names in a case-sensitive manner.

Your ISP's DNS server can't use IPv6.

No transport problems were discovered which could affect the deployment of DNSSEC

DNS glue policy (?): OK

Your ISP's DNS resolver does not accept generic additional (glue) records — good.

Your ISP's DNS resolver does not accept additional (glue) records which correspond to nameservers.

Your ISP's DNS resolver does not follow CNAMEs.

DNS resolver port randomization (?): OK

Your ISP's DNS resolver properly randomizes its local port number.

The following graph shows DNS requests on the x-axis and the detected source ports on the y-axis.

 

port sequence plot

DNS lookups of popular domains (?): OK

79 of 79 popular names were resolved successfully. Show all names.

In the following table reverse lookups that failed but for which a Start Of Authority (SOA) entry indicated correct name associations are shown using an "X", followed by the SOA entry. Absence of both IP address and reverse name indicates failed forward lookups.

Name IP Address Reverse Name/SOA

www.abbey.co.uk 165.160.15.20 X (pdns1.cscdns.net)

ad.doubleclick.net 74.125.79.149 ey-in-f149.1e100.net

www.alliance-leicester.co.uk 194.130.105.121 X (alice.ioko365.com)

www.amazon.com 72.21.210.250 210-250.amazon.com

www.ameritrade.com 216.105.251.204 X (mike.lynn.tdameritrade.com)

www.bankofamerica.com 171.161.148.100 X (primarydmz.bankofamerica.com)

www.bankofscotland.co.uk 195.171.171.21 X (ns0.bt.net)

bit.ly 128.121.254.201 X (ns1.dn.net)

www.capitalone.com 208.80.48.112 X (chia.arin.net)

www.careerbuilder.com 208.82.7.22 X (smokey.careerbuilder.com)

www.chase.com 159.53.64.105 X (ns1.jpmorganchase.com)

chaseonline.chase.com 159.53.60.54 resources-cdc1.chase.com

www.citi.com 192.193.219.58 citibank.com

www.citibank.com 192.193.219.58 citibank.com

www.citimortgage.com 192.193.103.118 citimortgage.com

www.desjardins.com 142.195.132.100 www.desjardins.com

www.e-gold.com 209.200.169.10 unknown.prolexic.com

www.ebay.com 66.135.200.27 hp-core.ebay.com

encrypted.google.com 74.125.77.100 ew-in-f100.1e100.net

www.etrade.com 198.93.34.21 www.etrade.com

www.f-secure.com 93.158.110.114 a93-158-110-114[...]echnologies.com

www.facebook.com 69.63.190.10 www-10-02-ash2.facebook.com

www.fdic.gov 192.147.69.84 www.fdic.gov

www.friendfinder.com 208.88.180.81 X (ii53-30.friendfinderinc.com)

www.google.com 74.125.77.147 ew-in-f147.1e100.net

www.google-analytics.com 74.125.79.100 ey-in-f100.1e100.net

www.halifax.co.uk 62.172.43.225 halifax.co.uk

www.hsbc.co.uk 193.108.74.126 X (ns3.hsbc.com)

www.irs.gov 93.158.110.113 a93-158-110-113[...]echnologies.com

www.jpmorganchase.com 159.53.64.105 X (ns1.jpmorganchase.com)

mail.google.com 74.125.79.83 ey-in-f83.1e100.net

mail.live.com 64.4.20.184 dp3.mail.live.com

mail.yahoo.com 217.146.187.123 l1.login.vip.ird.yahoo.com

www.mbna.com 209.135.59.10 X (ns1.usi.net)

www.mbna.net 209.135.59.10 X (ns1.usi.net)

www.meebo.com 74.114.28.110 X (ns1.meebo.com)

messenger.yahoo.com 68.142.230.204 myc1.msg.vip.re2.yahoo.com

www.microsoft.com 64.4.31.252 wwwbay3vip.microsoft.com

www.nationwide.co.uk 155.131.31.10 www.nationwide.co.uk

www.networksolutions.com 205.178.187.13 www.networksolutions.com

www.newegg.com 204.14.213.185 X (pdns1.ultradns.net)

online.citibank.com 199.67.180.11 citibankonline.com

online.wellsfargo.com 151.151.88.132 percussion-on.wellsfargo.com

www.orange.fr 193.252.148.241 vip1.dyn.hpo.s1.fti.net

partner.googleadservices.com 74.125.79.166 ey-in-f166.1e100.net

www.paypal.com 64.4.241.49 node-64-4-241-4[...]orks.paypal.com

www.rbs.co.uk 155.136.80.222 X (ns0-08.dns.pipex.net)

www.schwab.com 162.93.206.80 wwwschwab-vip.schwab.com

search.yahoo.com 74.6.238.254 syc.search.vip.ac2.yahoo.com

www.secureworks.com 64.31.190.9 X (ns1.telcove.net)

smartzone.comcast.net 76.96.26.12 webmail3.emeryv[...]ail.comcast.net

www.smithbarney.com 192.193.224.11 ssb.com

www.sterlingsavingsbank.com 12.19.55.215 sterlingsavingsbank.com

www.tdameritrade.com 216.105.251.204 X (mike.lynn.tdameritrade.com)

tinyurl.com 195.66.135.139 b2.tinyurl.com

us.etrade.com 198.93.34.50 us.etrade.com

www.usbank.com 170.135.216.181 artown.usbank.com

www.verisign.com 69.58.181.89 www-ilg.verisign.net

www.visa.com 93.158.110.177 a93-158-110-177[...]echnologies.com

www.wachovia.com 169.200.183.139 X (sls-ns1.wachovia.com)

www.wamu.com 159.53.84.27 X (ns1.jpmorganchase.com)

www.wellsfargo.com 151.151.88.133 www.wellsfargo.com

westernunion.com 206.201.228.250 www.wuagentlink.com

windowsupdate.microsoft.com 65.54.221.118 X (msnhst.microsoft.com)

wireless.att.com 135.209.168.22 origin-b2b-al[...]eless.att.com

www.yahoo.com 87.248.122.122 ir1.fp.vip.ch1.yahoo.com

12 popular names have a mild anomaly. The ownership suggested by the reverse name lookup does not match our understanding of the original name. The most likely cause is the site's use of a Content Delivery Network. Show all names.

Name IP Address Reverse Name/SOA

www.barclays.co.uk 212.140.250.32 X (ns0.bt.net)

www.bing.com 93.158.110.120 a93-158-110-120[...]echnologies.com

www.cnn.com 157.166.224.25 X (ns1.timewarner.net)

www.deutsche-bank.de 160.83.8.24 X (ns2.db.com)

www.lloydstsb.com 141.92.130.226 X (ns0.bt.net)

www.nordea.fi 92.43.121.130 X (ns01.tdchosting.dk)

www.postbank.de 195.50.155.73 X (ns1.arcor-ip.de)

www.sears.com 95.100.9.99 X (ns-pri.ripe.net)

www.sparkasse.de 212.34.69.3 rev-212.34.69.3.rev.izb.net

www.ticketmaster.com 95.100.4.199 X (ns-pri.ripe.net)

www.torproject.org 86.59.30.36

www.trendmicro.com 95.101.93.214 X (ns-pri.ripe.net)

One popular name has a mild anomaly: we are unable to find a reverse name associated with the IP address provided by your ISP's DNS server. This is most likely due to a slow responding DNS server or misconfiguration on the part of the domain owner. Show all names.

Name IP Address Reverse Name/SOA

www.bankofthewest.com 204.44.12.103 X

DNS external proxy (?): Not Executed

The test was not executed. Required functionality was unavailable or not permitted.

DNS results wildcarding (?): OK

Your ISP correctly leaves non-resolving names untouched.

Restricted domain DNS lookup (?): OK

Unrestricted domain DNS lookup (?): OK

Direct DNS support (?): Not Executed

Direct EDNS support (?): Not Executed

DNS resolver address (?): OK

DNS resolver properties (?): Lookup latency 229ms

DNS glue policy (?): OK

DNS resolver port randomization (?): OK

DNS lookups of popular domains (?): OK

DNS external proxy (?): Not Executed

DNS results wildcarding (?): OK

IPv6 Tests +

DNS support for IPv6 (?): OK

Your system does not look up IPv6 addresses by default. Your DNS resolver is not on Google's IPv6 "whitelist", which means that Google does not enable IPv6 access to their services for you.

IPv6 Connectivity (?): Not Executed

The test was not executed. Required functionality was unavailable or not permitted.

IPv6 TCP connectivity (?): Not Executed

Your host was not able to contact our IPv6 server for testing.

IPv6 and Your Web Browser (?): No IPv6 Support

Your browser was unable to fetch a test image from an IPv6-only server. IPv4 performance to our IPv4-only server did not differ substantially from our IPv4/IPv6 dual-stacked one.

IPv6 Path MTU (?): Not Executed

The test was not executed. Required functionality was unavailable or not permitted.

IPv6 Traceroute (?): Not Executed

The test was not executed. Required functionality was unavailable or not permitted.

DNS support for IPv6 (?): OK

IPv6 Connectivity (?): Not Executed

IPv6 TCP connectivity (?): Not Executed

IPv6 and Your Web Browser (?): No IPv6 Support

IPv6 Path MTU (?): Not Executed

IPv6 Traceroute (?): Not Executed

Host Properties +

System clock accuracy (?): Not Executed

The test was not executed. Required functionality was unavailable or not permitted.

Browser properties (?): OK

The following parameters are sent by your web browser to all web sites you visit:

 

* User Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; nb-NO; rv:1.9.2.10) Gecko/20100914 BTRS31753 Firefox/3.6.10

* Accept: text/html,application/xhtml+xml,application/xml; q=0.9,*/*; q=0.8

* Accept Language: nb,no;q=0.8,nn;q=0.6,en-us;q=0.4,en;q=0.2

* Accept Encoding: gzip,deflate

* Accept Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7

 

Java identifies your operating system as Windows 7.

Uploaded Data (?): OK

The following additional content was uploaded by the applet:

 

* raw_http_content

 

System clock accuracy (?): Not Executed

Browser properties (?): OK

Uploaded Data (?): OK