I can non more access adobeconnect login page from my home wi fi network

[adobeconnect_login]

Some months ago I used to have adobe connect meetings from home regulary, with different accounts, and I had no problems.

I didn't use adobeconnect for some months (last time was at the end of september 2011), then yesterday I tried to access my account and I found that I can't reach the login page: I receive the browser error (I translate it in english from italin) "Impossible to view the web page".

I can rech any other website, http and https, but not adobeconnect login page (es. https://connectpro61501161.adobeconnect.com/)

I tried with different browsers, different browser security settings, I switched off any security system (!?) on my PC but it didn't work

Finally ...I tried with my Iphone and I found that:

- when the Iphone is connected to my home wireless network it receive the error impossible to connect

- when the Iphone is connected to the 3G phone network it can reach and display the adobeconnect login page correctly

So.. as I made no changes to my wi-fi network... what could be?

Any ideas?

Thanks in advance,

Elena

[John_Stegenga]

it's definately in your ISP somewhere.

Do a trace -

From your PC, click the start menu, click Run, then type in CMD and hit enter.

Once you do that you get the old black and white "dos" box.

In the dos box / command line type:

tracert connectpro61501161.adobeconnect.com

You'll get back a trace report showing how your home network and ISP route your traffic.

Your ISP may have installed some caching software or other proxy type device that's causing your issue, or you may have malware - yes, home routers can get malware... its not common, but it can happen.

here is part of my trace to your URL

6   108 ms

61 ms

57 ms  vlan51.ebr1.Atlanta2.Level3.net [4.69.150.62]

  7   156 ms   160 ms   110 ms  ae-6-6.ebr1.Washington12.Level3.net [4.69.148.106]

8	94 ms   102 ms   108 ms  ae-1-100.ebr2.Washington12.Level3.net [4.69.143.214]

9

94 ms

99 ms   102 ms  4.69.148.49

10   176 ms   167 ms   169 ms  ae-44-44.ebr2.London1.Level3.net [4.69.137.77]

11   146 ms   175 ms   164 ms  ae-58-223.csw2.London1.Level3.net [4.69.153.138]

12   163 ms   184 ms   214 ms  ae-22-52.car2.London1.Level3.net [4.69.139.99]

13   184 ms   149 ms   164 ms  OMNITURE-LI.car2.London1.Level3.net [212.187.160.106]

14   181 ms   176 ms   215 ms  sr-b-1-vlan-2009.lon5.omniture.com [66.235.156.5]

15   183 ms   179 ms   167 ms  63.140.42.0

Trace complete.

PS - no idea why this editor put some of that into table cells... Oh well.

[ashley6100]

I'm having the exact same issues, trying to access the connect login page gives a timeout message on various browsers and computers, but trying on a phone connected to 3G will bring the page up fine.

Tried using the above dos command and each attempt states "Request timed out"

If this is a problem with my ISP, what can be done to get around it and get this working?

[John_Stegenga]

First - check your browser settings.  make sure that it is not configured to use some Proxy server settings.

Then look in C:\Windows\System32\drivers\etc\ for a file called hosts

This file should be quite small.  1kb or so.  If it's larger, then you either already run Spybot SD for malware protection, or, you have got Malware on the computer.

If your browser is set to use a proxy, that's another sign of malware.

If your computer is free of malware, the only other thing you can do is try to find a DNS server that resolves the adobe connect URL for you.

Open the DOS box again.

If you run IPCONFIG /ALL on your computer you will see what your computer knows to use for DNS lookup.

   Lease Expires . . . . . . . . . . : Monday, December 1

   Default Gateway . . . . . . . . . : 192.168.2.1

   DHCP Server . . . . . . . . . . . : 192.168.2.1

   DHCPv6 IAID . . . . . . . . . . . : 234890369

   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-16-B0-

  DNS Servers . . . . . . . . . . . : 192.168.2.1

   Primary WINS Server . . . . . . . : 192.168.2.1

This will typically be your ROUTER IP.

You can often find what your ISP's DNS servers are by looking at the status pages for your WiFi router.

In my router I added a 3rd DNS source - 4.2.2.2

4.2.2.2 is Level3 communications - one of their primary resolvers.  If my primary DNS can't find it, the router fails over and looks up on the next one, then the next after that (Level3)...

The command to see if your site is visible to your ISP's DNS is to (again in the command prompt) type:

nslookup <your adobe url> <your ISP dns>

So:

C:\Users\jstegenga>nslookup premiere.adobeconnect.com 64.13.115.12

Server:  UnKnown

Address:  64.13.115.12

Non-authoritative answer:

Name:    na3cps.adobeconnect.com

Address:  66.235.155.64

Aliases:  premiere.adobeconnect.com

in that example, you can see my ISP provides DNS for my site - which is correct, because I can use it!

Hope this all helps!