Capture Pilot & Ad Hoc network

Dirk Wenzel

• June 30, 2011 12:11

Hi all,

I have "capture pilot" tried, and in the local network via my WiFi router over the iMac it works wonderfully.
But if I try an "ad hoc" WiFi - network from my MacBook on location, I keep getting this error message:
"Unreachable Server.Could not connect to the Server."
But: The servers name appears in the list... ❓

How do I get it work for?

The iMac runs with 10.6.x, the MacBookPro with 10.5.8.
Creating an "ad hoc" network is not the problem, the network is there
and the iPad connects to it.
Are there some "things" to do with the network?... Sharing options?
I have read all intructions I have found on PO´s homepage.
Nothing works on the MacBook 🤬

Sorry for my english, translation by google... 🙄

0

• 

  Paul Steunebrink

  • June 30, 2011 12:27

  It could be the firewall off OS X 10.5.8 on your MacBook Pro. I noticed that CO6 on 10.6 creates a exception rule (allow connections) when you first start the Image Server (a.k.a. Capture Pilot server) in CO6. With 10.5 this rule was not created automatically and/or when created not effective.
  
  Check this out by switching your firewall (temporarily) off (System Preferences, Security, Firewall tab, allow incomming connections or some text like that).
  
  The reason that despite the firewall (still an assumption) the server is discovered by Capture Pilot on your iOS device, is a result of the fact that Bonjour traffic is never blocked by the OS X firewall. Bonjour is the network services discovery service used here. But once you connect, HTTP-traffic (TCP/port 80) does the job and is blocked making the server unreachable.

  0
• 

  Dirk Wenzel

  • June 30, 2011 17:08

  [quote="Paul_E" wrote:
  It could be the firewall off OS X 10.5.8 on your MacBook Pro. I noticed that CO6 on 10.6 creates a exception rule (allow connections) when you first start the Image Server (a.k.a. Capture Pilot server) in CO6. With 10.5 this rule was not created automatically and/or when created not effective.
  
  Check this out by switching your firewall (temporarily) off (System Preferences, Security, Firewall tab, allow incomming connections or some text like that)...

  
  💡 Oh boy, thats it ❗️ Thank you very, very much, Paul ❗️
  
  I have made a "exception" for the firewall, allow incoming connections for capture one:
  
  Now it works fine.

  0
• 

  Paul Steunebrink

  • June 30, 2011 17:32

  Your joy is most rewarding. 😉
  
  And you did the right thing with the exception rule.

  0
• 

  Permanently deleted user

  • July 01, 2011 12:41

  Paul E., many thanks. It's gems like this that make this forum so useful, and you seem to provide most of them. Thanks again!

  0
• 

  Paul Steunebrink

  • July 03, 2011 11:33

  Thanks John, I think this forum is a user community to be fond of.

  0

Post is closed for comments.