Robert,
I think we're in exactly the same process, as I had the same problem today !
First I thought that it was our firewalls here, that did not let the traffic through, so I spoke to the network guys but they said that they couldn't see any ports listening on my ASE server ?
So I took a look at the manual, and as far as I could find out it wasn't enough to just start Cockpit. You also have to start all the "Services", but outside Cockpit and before you start Cockpit ! So I reckon that you alter some kind of config file (that I haven't found yet) with these commands ?
What I did was the following :
./cockpit.sh -enable Tds
./cockpit.sh -enable EmbeddedwebContainer
./cockpit.sh -enable Messaging
./cockpit.sh
Then you can check your ports and see so that they actually are listening with :
netstat -tpnl
You can also see that the ports have changed from "false" to "true" with "info -p" ?
That is as far as I've come now. I can get the logon screen, but no "system" has been discovered yet, and I think one have to specify that too before starting Cockpit ? So I did that too with :
./cockpit.sh -instance <the ASE name> -user sa -password <sa password>
But I still cannot choose any "system" in my loon screen on my browser...
Regards
Mike