Flash progress infinite loop

The progress bar for the chat applet continuously loops, and never fully loads the applet (just the Bible Gateway on the side, which I'm guessing is just HTML code and not embedded Flash content).

I've noticed this only happens on my work comp (work has been slow so I figured "why not?"). I'm working on unraveling the cause, as I know others have had identical and similar issues, but to the mods, if you know the technical cause of it, I would love to be educated.

Thus far, I've tried the following:

1. Different versions of Flash player, including 32 bit and 64 bit versions.
2. Different versions of different browsers - again, both 32 bit and 64 bit.
3. Disabled hardware acceleration.
4. Clean reboot (Safe Mode with services and start up entries disabled). Still got the loading loop.
5. Google search. Different search queries did not yield similar results, although a few brought me to forums that alluded to the code on the site needing adjustment to circumvent other issues with Flash player.

I'll continue to find a workaround, more so for the sake of the CC community, but if Robo or any other admins/mods or technically inclined people (particularly in coding/HTML) know the cause, by all means, share your knowledge.

I'll not lie, I saw the title and thought you had just entered 4 random words.

Also, for what it's worth to those that are willing to troubleshoot with me, my system specs:

Windows 7 Professional 64 bit (SP1)
H57 Chipset (Acer manufacturered board)
CPU: Core i3 - 540
Intel HD Graphics
Realtek HD Audio

Note that my home computer running Windows XP Pro doesn't encounter this problem with chat. This is only recreated on my work computer, and only on CC.

Help me Obi-Wan RoboOP. You're my only hope.

It sounds like a firewall issue. I think at your work there's some kind of firewall. The chat app does connect to our chat server on a non-standard port. If you have any control over the firewall at your work then here's what you need to know: you need to allow connections to port 8081 on any remote IP. (Actually it doesn't need to be on any remote IP but I'm simplifying it. If you need to specify the particular IP then just let me know and I'll give you that info as well.)

P.S. When we design a whole new chat app (Lord willing), we'll try to use more standard ports or perhaps even HTTP-tunneling (just using the standard web server port, port 80, which of course is never blocked by firewalls).

Thanks a bunch for the follow up, Robo. My work doesn't [noticeably] crack down on my usage, so that hadn't even really occurred to me.

What about the issue with users' text not showing up in the dialogue box when they type?