any final advice on "cannot connect" error?

K

kelly crowell

Junior Member
Hello,

So I see some folks have had luck with getting PD4 running on a new machine (bought and downloaded for 79 USD, potentially the last time I'll ever do that, not to mention no upgrade purchases on two other machines nor good word of mouth to other Macintelsh owners) after having the 'cannot connect' error first raised during the private beta. I've made attempts as described there and on this forum to no avail on a brand new MBPro. The upgrade to 4 from 3 worked perfectly for me on my home Mac Pro. I just received the new laptop and was hoping to be able to do some billable windows-based work while away during the Thanksgorging holidays.

Could someone in the know please offer a summation of what is know about this issue? Will a fresh install of OS X solve the issue? If so is there a firewall state I need to maintain until I successfully run the software? I did a migration of files and settings from my old (and still beloved) Powerbook G4 but did not bring over applications or global Library files... might this have had an effect? Sure, I could experiment, but someone at Parallels should already have a good idea of this before I waste another evening trying to get back to the starting line.

Information would be much appreciated.
Cheer$,
Kelly Crowell, Once Was Impressed
 
Hi Kelly.

Please take a look on threads:

http://forum.parallels.com/showthread.php?p=132872
http://forum.parallels.com/showthread.php?t=31151

For some people Mac OS X reinstallation actually help. But i recommend you to do follow things at first:

1. Please check that prl_disp_service alive. You can do it through Activity Monitor or through Terminal by performing command:
sudo ps aux -c | grep prl_disp

2. Please check that dispatcher service listening incoming connections. To do it please perform follow command from Terminal:
sudo netstat -an | grep LISTEN
If all normal you should to see listen socket on port 64000

3. Please check whether you can to connect to dispatcher service through telnet . To do it please perform follow command through Terminal:
telnet localhost 64000
If connection succesfully establishment then press Ctrl+] and Enter. After this specify comman "quit" and press Enter in order to exit from telnet application.
If connection won't establishment then please check your firewall settings.

If you'll determine that dispatcher service alive, awaiting incoming connections and accepting connections (from telnet) then it's the situation which still not clear for us and as you can see at above mentioned threads people resolved this issue by Mac OS X reinstallation. Actually it's single known workaround on the moment. Sorry with it.
 
Thanks Alexander,

The dispatch service appears to not be coming up. I've tried the methods for resetting network configurations in one of the other threads to no avail. Given a few hours' sleep I'm calmer now, and will perform a careful reinstall in between tasks at work. Parallels will be the first 3d party install I perform; fingers crossed... I'm really hoping this will work so I can see how the RTM version works with the ArcScene component of ArcGIS on the latest demo I was provided.

Cheers,
Kelly
 
Kelly.

Actually you can wait for a bit time (day or two) - it'll be hotfix update that let you do not drop network configuration of your host.

Also could you send us problem report (when Parallels Desktop'll started and show you message about can't connect - please use Help->Report a Problem menu item) in order to be sure that it's the same well known problem that we already have.
 
Oops, I saw the reply too late, the OS X reinstall has just completed. It was indeed the exact problem from the earlier threads (cannot connect, mac may be down, etc.), and while trying various suggestions in those threads I got similar errors (e.g. 'bus error'). Should the problem recur then I'll take screenshots for proof and eagerly await the hotfix.

Cheers,
Kelly
 
The reinstall seems to have done the trick. I was asked for my license key and successfully activated it. Currently there is no network connectivity so it will be interesting to see how things go once I gain access to networking; I will not add the machine to the office network but will have a cell modem installed on my next break. At that point I'll also try adjusting the firewall and to actually install Windows XP. Once again, fingers crossed.

Luckily my laptop was delivered two days early, so this delay, assuming other things go well, just has me back to my originally envisioned schedule.

Cheers,
Kelly
 
I was able to resolve this issue by adding an alias for "localhost" in /etc/hosts to 127.0.0.1

It appears that the app is hardcoded to connect to "localhost" but many Macs don't actually have any IP mapping for the alias (as opposed to Windows where it's wired into the OS).
 
I got it to work by fixing /etc/hosts

When I tried
3. Please check whether you can to connect to dispatcher service through telnet . To do it please perform follow command through Terminal:
telnet localhost 64000
If connection succesfully establishment then press Ctrl+] and Enter. After this specify comman "quit" and press Enter in order to exit from telnet application.
If connection won't establishment then please check your firewall settings.
Click to expand...

It still didn't connect even with the firewall off.

I checked, and it turned out the the line of my /etc/hosts file that should have read :

127.0.0.1 localhost

was commented out. I fixed this, and Parallels started fine.
 
I found that anything funky in my /etc/hosts file was causing trouble with getting Parallels to start up -- especially relating to being able to resolve localhost. To be safe, I split my multiple entries for localhost to separate entries.

eg: NOT 127.0.0.1 localhost test.local project1.local
split them out
127.0.0.1 localhost
127.0.0.1 test.local
127.0.0.1 project1.local

this allowed me to get the GUI running. Hope this helps someone else.
 
You must log in or register to reply here.
Back
Top