Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 2 replies
  • Subscribers 0 subscribers
  • Views 8783 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Sophos WS500 and Join.Me

taekwanleap

Wondered if anyone else are having trouble downloading and installing the Join.Me client when being filtered by the Sophos WS500 or other similar appliance?

When I click to download the Join.Me client, I get an application error message pop-up on all of our desktops no matter if it is Windows 7 or Windows XP.

I created an access-list to exclude my PC from going through the WS500 web filter (not filtered at all) and was able to download and install the Join.Me client with no problems or application errors.   I then uninstalled the Join.Me client and removed my PCs IP Address from the access-list so my PC is being filter by the WS500.  Then when I try to download and install the Join.Me client, the application error message is back.   So it is definitely something with the Sophos WS500 causing the problem.  Just can't figure it out.

Wondered if anyone else was or is experiencing the same problem and no what the work around or fix is.  I am sure it is some obscure URL needing to be unblocked causing the problem.

Any help or ideas appreciated!  Thanks!

ON EDIT:

The application error pop-up is:

ClickOnceDeployer has stopped working

Event Viewer Message:

Log Name:      Application
Source:        Application Error
Date:          9/12/2012 9:56:32 AM
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      XXXXXXXXXXXX
Description:
Faulting application name: join.me.exe, version: 1.0.0.0, time stamp: 0x4c488adf
Faulting module name: KERNELBASE.dll, version: 6.1.7601.17651, time stamp: 0x4e21213c
Exception code: 0xe053534f
Fault offset: 0x000000000000cacd
Faulting process id: 0x%9
Faulting application start time: 0x%10
Faulting application path: %11
Faulting module path: %12
Report Id: %13
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2012-09-12T14:56:32.000000000Z" />
    <EventRecordID>34423</EventRecordID>
    <Channel>Application</Channel>
    <Computer>XXXXXXXXXXXX</Computer>
    <Security />
  </System>
  <EventData>
    <Data>join.me.exe</Data>
    <Data>1.0.0.0</Data>
    <Data>4c488adf</Data>
    <Data>KERNELBASE.dll</Data>
    <Data>6.1.7601.17651</Data>
    <Data>4e21213c</Data>
    <Data>e053534f</Data>
    <Data>000000000000cacd</Data>
  </EventData>
</Event>

:29467


This thread was automatically locked due to age.
  • 0

    We have similar problems with the Web Appliance and join.me. My testing has shown that the appliance does not actually proxy for the join.me sessions. It hands off the communication to the desktop computer after the intial authentication. The only way we are able to get join.me to work is to apply an access list and NAT our desktops out to the Internet. This is obviously not the preferred method.

    I engaged support, but there hasn't been any luck finding a solution. The problem is the web application doesn't act as a true proxy for the join.me screen application. Proof of this is in the local computer join.me log file: "Error - Socket - 64.94.46.201:443 - Error in connect. A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. (10060)"

    I have tried every configuration option I can think of with relation to: HTTPS Scanning, Authentication, Profiles, etc.

    Has anyone found a work around that does not require NATting workstations out to the Internet?

    :33277
  • 0

    Are you using a Cisco Firewall or Cisco ASA?

    Instead of NATing the workstation.  Create an access-list for your wccp-traffic to deny your specific PCs private IP adress from going through the filter temporarily.  This will at least allow you to download and install it.  Now, I do not know if after the client has been downloaded and installed and you remove your specific PCs from the access-list so that it is filtered if the Join.Me client will work correctly after that or not.

    Not sure if I am making any sense to you on this or not.

    So here is my Cisco ASA config related to WCC-TRAFFIC:

    access-list wccp-servers extended permit ip host (IP Address of your Web Appliance) any
    access-list wccp-traffic extended deny ip host (IP Address of PC you do not want to go through your web appliance - in other words not filtered) any
    access-list wccp-traffic extended permit ip any any

    This will make your internal private ip address of the PC not be filtered through your web appliance giving you complete free reign of the Internet.  You can then download and install the client.

    Once you are done - remove the line:

    access-list wccp-traffic extended deny ip host (IP Address of PC you do not want to go through your web appliance - in other words not filtered) any

    Hope this helps.  I might have to deny my PC - download the Join-Me client - then put my PC back to being filter - try the client and see if it works or not.  I suspect it would work.  It is just bombing out on the download/install process.

    So a quick and easy temporary work around for now.

    Let me know if you need any more help with the Cisco ASA config to get this setup.

    :33281
Unfiltered HTML