I received a response from Embanet yesterday evening. This is what they had to say;

Incident Thread
Response (Aaron) 02/07/2012 05:33 PM
Hello Michel,

Thank you for taking the time to contact us.

We are following up with you in regards to your case; we have received a workaround from Xplornet for the connectivity issues you are encountering. Please use the following steps to add proxy settings to your browser:

For Internet Explorer:

1. Access "Tools" and select "Internet Options"
2. Select the "Connections" Tab and select "LAN" settings
3. Select the check box beside “Use a proxy server” and enter the following information:
Address: proxy.ripnet.com
Port: 8888
4. Select the check box beside “Bypass proxy server for local addresses”
5. Select "OK"
6. Select "OK"

For Mozilla FireFox:

1. Access "Tools" and select "Options".
2. Select the "Advanced" tab and select "Network".
3. Under "Connection" select "Settings".
4. Select "Manual Proxy Configuration".
5. Enter in the following information in the appropriate areas:
Address: proxy.ripnet.com
Port: 8888
6. Select "OK" and select "OK" again.


If the steps above don't work please communicate this with Xplornet.

If we may be of any further assistance, please do not hesitate to contact us.

Regards,

Aaron
Helpdesk Support Specialist

You may reply to this email to update your ticket.
Answers to most frequently asked questions may also be found at http://supportcenter.embanet.com/ontariolearn

Response (Aaron) 02/05/2012 12:33 PM


It didn't work. The address that is, and I find this to be a really lame fix. Go onto proxy with higher ms times and downtimes, real smart! I'ts not really a fix, just another evasive way to not work and correct the real problem at hand.

I contacted Xplornet and they have no record of this fix, they say they never sent an email to Embanet regarding this. Hummmmmm! I then proceeded to force the level one tech to patch me through to a supervisor. Normally you can never get to one, I did this time. Dan was bent out of shape at first about speaking with a client but warmed up real fast when I summarized the events that led to me speaking with him. He and I finally hit it off technically and I gave him access to the web based side of PingPlotter Pro and his first reaction was WOOOOOOoooooow!
He used this program once to trace within a network for another company he worked for and loved it. He's fallen in love with PingPlotter Pro again. He started taking snapshots of the conditions in PingPlotter, even logging after we got off the phone!, and assured me that he would get it to his engineer friend in Xplornet to finally fix this issue. I have since been tracing and keeping a record of things for both he, and I. He does agree with my conclusions regarding the problems I've been having and deeply apologized for the length of time it's taken to resolve this issue, he has some techs he will be speaking to.

I will tear a strip off of Embanet when the time comes too.

Once again, I cannot begin to express my gratitude for PingPlotter Pro and Pete Ness. Both your program and you ROCK!

Mike