Hi all, thank you for your help. We did what you suggest already but I'll try to descibe the problem we get:
1. we launch the command vncserver :30 -depth 24 -geometry 1280x1024 and we get the output New 'cnsicol2:30 ()' desktop is cnsicol2:30 Starting applications specified in //.vnc/xstartup Log file is //.vnc/cnsicol2:30.log
2. in the //.vnc/cnsicol2:30.log file we find few errors as follows: Xvnc version 4.0 - built Jun 14 2004 11:53:25 Underlying X server release 0, unknown Mon Nov 15 12:27:09 2004 vncext: VNC extension running! vncext: Listening for VNC connections on port 5930 vncext: created VNC server for screen 0 Could not init font path element /usr/lib/X11/fonts/Speedo/, removing from list! Could not init font path element /usr/lib/X11/fonts/Type1/, removing from list! Could not init font path element /usr/lib/X11/fonts/CID/, removing from list! Could not init font path element /usr/lib/X11/fonts/100dpi/, removing from list! Could not init font path element /usr/lib/X11/fonts/75dpi/, removing from list!
3. we export DISPLAY by using the command: export DISPLAY=:30
4. we launch NNM map by using the command: ovw&
5. we find the ovw process is running on the management server
The problem is that when we try to connect to NNM map through NNM web access, it's not possible to open the map because it seems NNM does not find the NNM map opened on the management server.
Hi Pat, as you said it's not a font problem because we tried to connect to the vnc session using vncclient and the map is correctly loaded. The name of the map we are trying to open via Web is correctly named as well.
But one thing has changed now: we launched the vncviewer and now, even if we have closed the vncviewer once the map is loaded, the web map has no problem to be loaded also.
Do you know then if it's mandatory to launch the vncviewer at least once on a server different by the server where vncserver is running???
Caterine, I don't know what the problem was but as I said earlier, IMHO it's not related to connecting to the client using a vnc client. I only asked you just to make sure that the ovw client was running & thus narrow down the problem by elimination.
Again, all I use to run NNM in VNC sessions are the two lines I posted earlier. The call to ov.envvars.sh is usually unneccesary as well.