Home
Features
Members
F.A.Q.
Download
Guide
Blog
Forums

Woopra Forums » Troubleshooting » Windows Software

Help! Why can't I connect?

(19 posts)
  • Started 2 months ago by barnsleypct
  • Latest reply from raymer
  • This topic is not resolved

  • James
    Member

    Hi

    I've been trying unsuccessfully, since Woopra 1.0 to use the client software at work on our corporate network. (I'm on the NHS's N3 network in the UK for any that know about it)

    I am told by our IT guys that they are not actively blocking ports (other than MSN) so as far as they are concerned there is no problem with their network.

    Unfortunately though, Woopra still fails to connect to my site at work. The Blog and Adverts appear and it shows me as logged in. But the site just shows "Connecting" for ever.

    I really like Woopra and it works fine at home. But does anyone have any ideas why this might be happening at work?

    For the record, at home where it works, I use a OSX Leopard. At work, where it doesn't, I use WinXP.

    Posted 2 months ago #

  • Benoit
    Member

    I started having exactly the same issue since I upgraded Wordpress plugin to version 1.3. I'm running XP. I tried removing the plugin, doing manual installation: no change, get the connecting forever, then back to login screen. Redownloaded Woopra altogether, reinstalled, did manual install: same thing. Redeleted everything, redownloaded latest PC version, latest plugin version: same thing again, i.e. it launches, says connecting forever, then back to login screen. I'm totally stumped. Any suggestions for a fix?

    Posted 2 months ago #

  • Shane
    Bugs Tracker

    A suggestion if you can... try to run the application as "administrator" using the "Run as Administrator" option.

    Posted 2 months ago #

  • Benoit
    Member

    Shane, I tried. No change.

    What I find most frustrating with this is the way Woopra is build, there is actually no indication at all about what is happening and what hangs where. On other betas I've been on, there is generally a log of sorts or a debug mode so that you can actually see what goes on and pinpoint the issue. Not that I am an advanced tech who can fix everything, but as I'm sure you know, more often than not, issues aren't automatically complex either.

    As it stands, it does show signing in as working (connected shows at the top left under the Woopra logo), then the connecting for my site starts but some handshaking doesn't seem to happen. Why? No clue.

    Posted 2 months ago #

  • Shane
    Bugs Tracker

    This is a long shot, but try upgrading Java run time files. I am on Vista and have no XP machine to test on, but check to see if they are up-to-date.

    Posted 2 months ago #

  • Benoit
    Member

    I always run the latest version. Checking on the Java Site, get the message

    Congratulations! The latest version of the JRE is installed and running correctly on your system.

    Your Java configuration is:

    Vendor: Sun Microsystems Inc.

    Version: Java 6 update 7

    Operating System: Windows XP

    Posted 2 months ago #

  • Shane
    Bugs Tracker

    Umm... same version. Windows Firewall?

    Posted 2 months ago #

  • Benoit
    Member

    I even attempted totally turning it off, same issue. IF I could get my hands on the previous version of the plugin (1.1), I would revert to that as it worked just fine with it. It's only since getting the new version of the plugin, starting with 1.2 that I began having issues. Sadly, while quite a few plugins on the Wordpress repository also give you access to previous versions (specifically for this kind of issue), Woopra doesn't.

    Posted 2 months ago #

  • Shane
    Bugs Tracker

    We just added it to the repository during the 1.3 line. What is your website URL?

    Posted 2 months ago #

  • Benoit
    Member

    Hi Shane. Site URL is http://lebuzz.info

    Posted 2 months ago #

  • James
    Member

    My problem has nothing to do with the wordpress plugin as the site appears to be collecting stats quite happily.

    I just can't access it through the work network.

    I am a local admin on my machine and java is up-to-date.

    When I've looked at packet traffic it does appear that the Woopra client does receive some data (not port 80) from the outside world initially, however with the new blogs and adverts in the client I don't know if the traffic is related to that or to the stats.

    Posted 2 months ago #

  • James
    Member

    Any ideas anyone?

    Posted 2 months ago #

  • freakoid99
    Member

    I have this problem on my linux machine. Windows machine is fine. Same network. One machine sitting right next to the other.
    Not sure if this helps.

    Oh! I will mention that when on VPN into my office from home, Woopra does not work. In fact, it's the only thing that doesn't work, internet-wise.

    Posted 2 months ago #

  • stargate
    Member

    James,

    Your IT guys are wrong theyre blocking the traffic, perhaps woopra can confirm for us what port the client connects on and protocol so we can ensure its open. Otherwise if you have a proxy use that, you can set that setting in TOOLS > Options

    Freakoid99, iptables -F, try again?

    If we do get a response from woopra and confirm the port and host the client connects to, your next step should be to open a command line prompt and "telnet <hostname> <port>" if you can't connect at that point you can be assured there is a firewall/antivirus issue blocking it.

    Posted 2 months ago #

  • stargate
    Member

    As an after thought, and this is more of a feature request I suppose.. Woopra should implement a timeout after trying to connect for X seconds and throw an actual error stating the connection could not be made rather than having the client sit at 'connecting' with nothing further. I think it's a bit confusing to members when this happens, any verbosity in the error would be very helpful.

    Posted 2 months ago #

  • stargate
    Member

    Found It!

    my client is connecting to 72.233.107.33/8611

    And I had to have this opened on our corporate firewall to gain access.

    I would suggest (since Im not sure if that IP changes) opening either everything on port 8611 or a broad range, say 72.233.X.X on port 8611

    Hope that helps some folks!

    Posted 2 months ago #

  • raymer
    Member

    Maybe the OP (James) can confirm whether this port is open on his network and see if opening it will resolve his problem. If so he should mark the thread as resolved so others know there is a solution buried in here ;-)

    Posted 2 months ago #

  • freakoid99
    Member

    iptables -f doesn't do anything.
    iptables -L shows everything is open. no firewall set up.
    and telnet 72.233.107.33 8611 connects fine.

    It's got to be the woopra client. Especially since I can connect just fine on my windows box on the same network.

    Posted 2 months ago #

  • raymer
    Member

    freakoid,
    I don't think the OP is using Linux. If you have a linux-specific problem maybe you should consider starting a thread specific to that and including version info etc.???

    Posted 2 months ago #

RSS feed for this topic

Reply

You must log in to post.