VNC, X, and Opmnctl

I don't know if this is in the discussions groups already. I'm just putting this out there just in case.
I am running Application Server 9.0.1.4.0 on Red Hat 3 ES. After a power failure, running opmnctl startall gave me this error:
04/12/13 17:20:09 [4] ONS server initiated
04/12/13 17:20:09 [2] BIND (Address already in use)
04/12/13 17:20:09 [2] 0.0.23.115:6003 - listener BIND failed
04/12/13 17:20:09 [4] Listener thread -1303270480: 192.168.2.9:6003 (0x404) terminating
04/12/13 17:20:09 [1] Local listener terminated
Apparently our X server and an opmnctl process is trying to use ports 6001 to 6003 at the same time. Opmnctl tries these ports and gives up at 6003. We were running multiple Vnc sessions, and so were tying up the ports.
I reduced port usage in this range allowed opmnctl to start without any errors.

Interesting.
The X Window System protocol uses ports 600x where x is same as display number.
Vnc server has three port ranges: ports 580x for web, 590x for viewer and X server part of VNC uses 600x (for remote apps to display themselves). So vncserver :3 will (try to) use port 6003.
Example from a RHEL 3 machine:
(PIDs 1926 and 1943 is vnc :1 and :2, respectively)
# netstat -napt | egrep '580|590|600'
tcp 0 0 0.0.0.0:5801 0.0.0.0:* LISTEN 1926/Xvnc
tcp 0 0 0.0.0.0:5802 0.0.0.0:* LISTEN 1943/Xvnc
tcp 0 0 0.0.0.0:5901 0.0.0.0:* LISTEN 1926/Xvnc
tcp 0 0 0.0.0.0:5902 0.0.0.0:* LISTEN 1943/Xvnc
tcp 0 0 0.0.0.0:6000 0.0.0.0:* LISTEN 1026/X
tcp 0 0 0.0.0.0:6001 0.0.0.0:* LISTEN 1926/Xvnc
tcp 0 0 0.0.0.0:6002 0.0.0.0:* LISTEN 1943/Xvnc
tcp 0 0 host:5902 user:1618 ESTABLISHED 1943/Xvnc
The list of know ports is getting a bit crowded...
(NB. 9.0.1.4 is Metadata Repository Database server version, not AS version. AS in this case is probably 9.0.2.x)

Similar Messages

Mac OS X 10.5.7 as VNC server and Windows as VNC server

Hi,
I try to enable screen sharing from Mac OS X as VNC server and we would like to use a Windows client as VNC client.
I try to anable it from system pref., set the password, ecc.
When I insert VNC password from Windows, VNC send me this message.
read: Connection aborted (10053)
Have you got any advice?
If I use Windows as VNC server and Mac 10.5.7 as client all works fine.
Windows Vista SP1, RealVNC VNCviewer 4.1.3 free edition.
Thank you
Regards.
Ganimede Dignan.

Re: Ganimede Dignan
Re: justinvallon
I have found that if a 3rd party client is not happy with the Mac OS X VNC server, then switching to the Vine Server (aka OSXvnc) often times does the job. Vine Server is a free download:
<http://www.versiontracker.com/dyn/moreinfo/macosx/16699>

Diff between "opmnctl stopall" and "opmnctl shutdown" ?

As far as I found out there are two similar commands:
"opmnctl stopall"
and
"opmnctl shutdown"
What is the difference?
Peter

"opmnctl stopall" : This will stop all the processes in controlled manner. It means if any work is in progress than untill it finishes that component would not stop. Also from the time you execute this command new task would not be initiated and thus the component would not be avaialble for new requests.
"opmnctl shutdown" : This is equivalent to ctrl+c instruction to any process running from windows command prompt or similar instruction in other OS. This will initiate the forcefull shutdown of processes and may lead to loss of data if process are not complete and performing some task. This should be used when you left with no other option to bring down the server.

OMS and OPMNCTL question?

Hi All,
what is the difference between
emctl start oms
and
opmnctl startall

You should be able to perform these actions in four different tools:
opmnctl, emctl, dcmctl and Application Server control
Nothing like a wealth of possibilities.

Back to My Mac/VNC/Screen and File Sharing with a PC

Ok back to my mac is great but it doesn't work with a pc. What is the best alternative to screen and file sharing with a PC???
Thanks,

Use VNC.
On the PC.
http://www.realvnc.com/products/free/4.1/index.html
On the PocketPC
http://www.windowsfordevices.com/news/NS5673359231.html
Apple's Remote Desktop allows for VNC control through a password.
iFelix

VNC OSX and OS9 not working

I'm using the following applications:
Server (OS 9):
http://www.redstonesoftware.com/vnc.html#OS9vnc
Client (OS X):
http://sourceforge.net/projects/cotvnc/
I can not seem to see the OS9.2.2 G3 W/B from the Snow Leopard MacPro. By all the searching I've done, these two applications seemed highly recommended if one could not afford to purchase Apple Remote Desktop (WAAAAY too expensive)
I've set up file sharing as well and even then the two machine do not see each other. The Mac Pro will access the HD of the G3 after I tell it what IP address to go to, but it does not automatically see it like I see other computers on my network. So I have to wonder what I'm missing.
I need to access the G3 on the network and remote control it. Any suggestions?

Hi, Howab. When you erased the drive and reinstalled OS 10.3, you probably did so using a retail OS 10.3 installer disk set or a retail 10.3 upgrade set, neither of which contains or can reinstall any version of OS 9. Then perhaps you tried to reinstall OS 9.2.2 using an updater rather than a full installer disk. An updater requires some previous OS 9 version to be in place so it can be updated; the updater is not a full installer.
To reinstall OS 9 if you don't have the set of discs that came with your iMac, you will need to buy a retail OS 9.x installer CD (white with a big gold "9" on the label). Don't buy a gray OS 9 installer disc: those are all model-specific and unlikely to work on any model other than the one with which they were originally shipped.
Note that if your hard drive was erased without selecting the option to install OS 9 drivers on it, it will not be visible when you start the computer up from an OS 9 installer CD. In that case, there is no option but to erase it again, being sure to select that option when re-erasing it.

ARD3.1 and frequent VNC crashes and garbage screen on login.

Hey everyone,
I know this questions have been up before but has anyone found a solution to those problems.
I am using Xserve G5 with 10.4.8 OS X Server and ARD 3.1
On certain servers my VNC deamon crashes frequently everytime I remote into it.
Subsequently if I authenticate on the remote server to login I get a garbage screen and have to log out again and repeat the step before it works.
Any ideas?

"Subsequently if I authenticate on the remote server to login I get a garbage screen and have to log out again and repeat the step before it works."
I have exact the same problem with garbage screen on my new XServer and ARD 3.1.
Is there any fix from Apple?
JO

Vnc server and java

Hi,
how can i initialize VNC from java?.
I want to access other compuers from java using VNC viewer.
any one have the idea.
thanks

Maybe

VNC into Mac and keyboard layout

Hi,
I'm trying to get keyboard layout mapping to work between the mac mini which is the VNC server and any remote VNC clients (linux, windows, mac). Tried ultravnc, tightvnc, realvnc clients. And 10.5.x built-in as well as Vine VNC servers. The mini has an Alphagrip keyboard with US+Finnish layouts. The client PCs have Finnish layout typically, also US or German.
Problem is that any pipe, tilde, @ etc "special" characters typed through the clients end up as umlauts or other characters in the VNC.
Any suggestions how I could make VNC work so that the VNC keyboard layout is always the client layout?
Thanks,
- Jan

Thanks for pointers!
Setting "US" in OSXvnc did not work with any local client-side layout, oddly not even EN/US local + EN/US remote with OSXvnc use either "US" or "Current Layout".
But the following nearly works. Client Finnish keyboard, server Mac Mini Finnish keyboard, for the ultraVNC client change Finnish/FI to US winxp locale (using XP's/Vista's Language Bar), in OSXvnc choose "Current Layout" and set global Mac layout to Finnish.
I.e. have same keyboard at both ends but set the "wrong" US locale in WinXP for the ultraVNC client.
Now nearly everything works (with this laptop and server) - all umlauts and special characters. The only and unfortunately also critical problem is that the key "|" does not "work", it outputs "'*" instead. On the Mac the key is on the left of spacebar, on the client on the right. I don't see how this alone could change the scancodes. But apparently it does. Because it does not work.
Is there not some UTF / Unicode version of VNC for all OS X, Windows, Linux?
Or some VNC that would handle keyboard layouts smartly, transparent to the user?
Another option, IME with RDP (MS Terminal Services, rdesktop) there is no problem with keyboard layouts. Perhaps you guys know some RDP server for OS X?

Apple Remote Desktop 3 and Real VNC

Just wanted to post an FYI, that recently I found out VNC (Real VNC) Server & Viewer were conflicting with ARD 3.2 in terms of screen sharing/control. All other connections were fine. (e.g. chat, message, package install, etc..) For me to regain a successful connection to my clients I had to uninstall VNC, reboot and "whalla" screen share/control was full functional again. I don't know if anyone had a work around for the two programs to work simultaneously, but I couldn't figure it out and just uninstalled VNC. Not sure if this would be the same case with Ultra VNC, but I think it is safe to say that if you are wanting to remote manage a group of Macs (PC's included) you should stick with just one program. Any thoughts out there?

The "normal" version:
Yep. All generic VNC software will conflict with ARD. This is a good note for most admins out there.
The "geek" version:
Tell RealVNC to use port 5901. Look at the "Connection Options" section of the documentation for your server-side os/version.
The "too much information?" version:
Actually, VNC servers and ARD do just fine side by side. (Aside from listening and bonjour advertising and that), both servers are actually inactive until they receive a connection request. The clincher is that any services ...from Apache to ARD reports to SMB to VNC... always need to be listening to different sockets on different ports. In the good old days, VNC servers could actually listen on several ports and would serve at different color depths and resolutions based on the port number of an incoming request. In fact even today, because ARD uses a mostly standards-compliant VNC implementation, it has to use a different port for reports and commands and such so it won't conflict with the inbuilt VNC server.
VNC is usually on port 5900 nowadays. ARD uses 5900 for its VNC without asking. ARD also uses (or has used) 3283, 5432, 5433, and 5988 for reports and other non-VNC communication. (See: Apple's [list of common ports|http://support.apple.com/kb/TS1629].) In my experience, ARD's VNC client can very reliably control standards-compliant VNC servers, though your mileage may vary.
-- To control a non-ARD VNC server via ARD, just do whatever you normally would in ARD. When controlling, it may warn you that the VNC server doesn't support keystroke encryption, etc. but should still work fine.
-- To connect ARD to a VNC service running on a different port, choose "Add by Address… ⌥⇧⌘N" and in the address field, type the domain name or IP address as you normally would, but append a full colon ":" and the port number. For example, jsmith.example.com:5901 would connect to the computer named jsmith but would look for the VNC service on port 5901.
-- To control a Mac which is running the OS's ARD-VNC server from a third-party VNC app, you must have 'plain' VNC access turned server-side (that is, on the Mac to be controlled: System Prefs > Sharing > Remote Management > Computer Settings > "VNC viewers…"). As long as you use a decent client, it should work reliably after that.
I routinely run the standard ARD "Remote Management" services on my servers for normal remote interaction, but then have a Vine Server set up on 5901 with vastly different settings to benefit low bandwidth connections from the internet, from my iPod's VNC client, or through bouncy ssh tunnels.
If you have any other experiences or questions, or especially if anyone wants try any of this and encounters problems, by all means post back.
Cheers, Joel

Help with Chicken of the VNC and Airport

I had my airport working with Chicken of the VNC perfectly and lost the settigns. Now I cannot get it to work again. What do I do a bridge or port forwarding? And how?
There is so much contradictory information that I have just spent the whole night not doing anything of use. Any precise help would be greatly appreciated.
Thanks in advance!

The basic steps to configure for VNC are as follows:
o Configure the machine you want to control (VNC Server) to allow VNC access. If the VNC Server is behind a router, then this would entail at least three things: 1) Configure the OS X Firewall to allow VNC access, 2) Configure the router to map port 5900 to the VNC Server, and 3) Know the WAN IP address of your router. (Note: One way to get the WAN IP is to go to the web site http://whatismyip.com and make a note of the ip address.)
o Connect to your VNC Server from a VNC Client from the Internet.
And I tried to do port forwarding but it doesn't seem to work.
Let's double-check your port mapping settings.
1. Reserve a DHCP-provided IP address for the VNC Server.
Internet > DHCP tab
o On the DHCP tab, click the "+" (Add) button to enter DHCP Reservations.
o Description: <enter the desired description of the host device>
o Reserve address by: MAC Address
o Click Continue.
o MAC Address: <enter the MAC (what Apple calls Ethernet ID if you are using wired or AirPort ID if wireless) hardware address of the VNC Server>
o IPv4 Address: <enter the desired IP address>
o Click Done.
2. Setup Port Mapping on the AEBSn.
Advanced > Port Mapping tab
o Click the "+" (Add) button
o Service: <you can ignore this setting>
o Public UDP Port(s): 5900
o Public TCP Port(s): 5900
o Private IP Address: <enter the IP address of the VNC Server from the above step>
o Private UDP Port(s): 5900
o Private TCP Port(s): 5900
o Click "Continue"
(ref: "Well Known" TCP and UDP ports used by Apple software products)

VNC errors with OVM 3.0.3 Manager and Server

Hi all,
I installed the Linux RPM for Tight VNC View and have errors:
[root@myserver]# rpm -qa|grep tightvnc
tightvnc-java-1.3.9-3
[root@myserver]# which tightvnc
/usr/bin/which: no tightvnc in (/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/root/bin)
OVM 3.0.3 then complains:
Failed to execute local configured vnc viewer due to
java.io.IOException: Cannot run program no such file or directory
How would I resolve this issue to get the console working for the VM?

Hi Avi,
When I open the console from OVM 3.0.3 Manager, it prompts me to open the following Java files:
ovm_rasproxy-ws.jnlp
vnc-viewer.jnlp
then it opens a VNC window with Options menu on the OVM Manager host.
I removed the hostname from the setting from the VNC window
Now it complains "Login Failed" from the Oracle VM Manager Linux host.
I verified that tightvnc RPM has been successfully installed so not sure why this is happening.
Both errors occur on the actual OVM 3.0.3 Manager Linux host from where I run the OVM Manager web based application.

A stable, fast reliable VNC connection to Lion or Lion server

I hope this post help people with VNC setup from non Mac machines to a Mac running Lion or Lion Server 10.7.4.
Apple has changed quite a few things in Lion regrading VNC and screen sharing. As a consequence many VNC viewers are no longer compatible until the VNC software is upgraded to be Lion compatible. You will find many posts about this topic in this forum, eg
https://discussions.apple.com/thread/3289794?start=0&tstart=0
Often, the result is that the user can't proceed beyond the gray login screen (screen locks up etc).
This post describes how configure Real VNCs VNC server on Lion Server 10.7.4 to work in conjunction! with ARD, thus allowing you to keep screen sharing enabled and still use ARD from client if that is desired)
Download the VNC server at (Version 5! necessary)
http://www.realvnc.com/download/vnc/latest/
and install the VNC server on the host (the computer you want to login to via VNC)
Single User Host setup
==================
- Install the VNC server and follow the intsruction
(If you your Mac is configured for remote management, screen sharing, remote apple events the installation may complete with error stating to contact the manufacturer....ignore the error as it most likely caused by a port conflict because VNC server and ARD (or apple scrren sgaring both use port 5900 per default), the software was still completely and correctly installed.
- start VNC Server by opening Finder -> Applications -> Real VNC -> VNC Server (User Mode)
You will see a small VNC icon in the top tsak bar of the screen.
(if you open the "information Center" the issues tab will show a port 5900 conflict)
- open VNCserver Options and select the connections tab:
+Change the default port from 5900 to 5901 and serve Java viewer on Port from 5800 to 5801
+ Change Authetication to "Mac password"
+ Select Encryption "always on"
- Selct the expert tab
+scroll down to the bottom of the list and change "StopUserModeOnSwitchOut" to "no"
(this settings prevents the VNC server to be stopped automatically if you have Fast Switching User Mode enabled on the host.)
- select "Apply"
(now if you open the Information Center" again, the port conflict problem should be solved.
- select "open" from the VNC server menu:
If the configuration was succesful, thw window will show a check mark in a green box stating everything is ok.
- In addition you will find the address that the client user will need to connect to the VNC server on the host
it will say something like "VNC viewer user can connect using the address 192.168.x.y:1"
Note: If you start several VNC servers, each session will need a dedicated port (like 5902, 5903 etc)
Router/Firewall Settings:
===================
Depending on the router/firewall you use your ports may have been automatically configured for you (airPort extreme for example).
You need to open port 5901 and 5801 and forward these ports to the IP address of the host. If ARD was alredy working in your setup, you can copy the port coniguration for ports 5900, 3283 and 3306 that are used by ARD and implement the same rules for the new port used by VNC 5901.
Review the settings of your firewall/router.
VNC client
========
- download the VNC client for your OS from
http://www.realvnc.com/download/viewer/
and follow the install instructions.
- Start the VNC client on your client PC (Windows for example) and enter the address that the VNC server reported to you earlier (192.168.x.y:1)
- Encryption : "Let VNC Server choose"
- select "connect"
- enter your Mac username and password that was setup on your host
you are now connected via VNC to your host.
You can also configure the VNC server to allow other users to login to the same! VNC session using their user credentials (friends/family or serverAdmins that want to share access to the host)
To do this open the options dialog box on the VNC server host computer and select "configure" next to authentication.
- add the users that are supposed to get access to your VNC session using their own credentials. (make sure this is what you really want, otherwise read on in the multi user section of this post)
Multi User Host Setup
=================
If multiple users are supposed to access the host computer using their own credentials logging into their own! desktop, follow these instructions:
- first enable Fast User Switching on your host computer by going to
System preferences -> User/Groups -> Login Options and select the check box "show fast user switching menu as..."
- For each user on the host that should be reached via a VNC session start VNC server (user) as described before and assign a new port number to the new user like 5902 etc.
- repeat the configuration outlined above for each user (eg. "StopUserModeOnSwitchOut" to "no")
(note initilally when you start the VNC server for the first time again, you will get notified that a port conflict exists again....this disappears as soon as the new port is configured)
now another user can login via VNC into his own desktop using the server address : "191.168..x.y.:2"
Final notes:
=========
I spent hours trying to get a variety of VNC viewers to work with the new screen sharing/VNC implementation in Lion and finally gave up. I called Apple Enterprise support and they confirmed that "a majority of the existing VNC products are not compatible with the new VNC implementation in Lion yet and that Apple recommends ARD". The discussion on what other non Mac users (Windows, Linux) should do did not go anywhere....
I have tested the above configuration with the free version VNC server 5 on the host and the free version VNC viewer 5 on a client. It worked flawlessly, fast, reproducable and very stable. You need to be aware that depending on the features you want (number of desktops, users etc) that you may have to purchase the personal or enterprise edition for the server.
The featurs are described here:
http://www.realvnc.com/products/vnc/
I personally installed the enterprise edition after I verified that the free editions worked stable and reliably as I needed them to work.
I hope you now have a stable VNC link into your Lion host from the platform of your choice !

I'm using the free VNC edition from RealVNC on Mt. Lion (10.8.5) and the basic information is in this article for Lion is confirmed for the VNC Server 5.0.6 (r113416) on Mt. Lion.
The main Options... window shows the Connections tab and I just changed my port to something other than 5900 and the port conflict went away.
The Free edition does not allow Mac password and encryption can't be enabled. (Ya gotta pay for that.)
Connected to it from my iPod Touch using Mocha VNC with no problems.

Screen Sharing and finder

Just bought an Apple Time Capsule a fortnight ago.
Previously I was able to see local computers and conduct screen sharing through finder with no problems with my old wireless setup.
Having problems do so now. I have reinstalled 10.5.6 on my main mac but all the details and shares are standard and setup on the other.
I am able to screen sharing if I do it by ip but it is a mess around and not as easy as before.
Am I missing a setup item/process in Time Capsule?
Cheers.

Hi amthflea
I have a very similar setup.
I VNC to my other computers using JollyFast VNC (free and open software) - very very very fast and a lot better than the built in one. Very easy to use. You need to input the ip once, that's it, then it saves an easy list of your computers.
http://www.jinx.de/JollysFastVNC.html
I don't know about the sharing though. The devices i VNC to Are PPC-models and it pops up fine in finder.
In sharing
Personal File Sharing
Apple Remote Desktop and Printer Sharing are enabled.

Screen Sharing and Remote Login suddenly stopped working

I have had Screen Sharing and Remote Login turned on on my iMac for several weeks and they have been working fine up until now. I have been accessing the computer via VNC programs and command-line ssh logins from other computers on the same local network. When I tried to connect today, i was given the following error message.
ssh: connect to host xxx.xxx.xxx.xxx port 22: No route to host
I have all of the required settings turned on in System preferences and there are no firewalls or router settings blocking it. I connected the two computers together via ethernet cable and the error message still occurred.
I can ssh from the machine to 127.0.0.1, so the ssh server is running. I can ssh to other locations from the laptop i am attempting to connect with, so that's not the problem either. I just spent an hour on the phone with the apple tech support line and they couldn't figure anything out either. Can anybody figure something out?

have you tried the obvious - restarting the computers involved and the router?

VNC, X, and Opmnctl

Similar Messages

Maybe you are looking for