18135 [Solved] vncserver cannot init font path element /usr/local/lib/X11/fonts/Speedo/ - The FreeBSD Forums
The FreeBSD Forums  

Go Back   The FreeBSD Forums > Desktop Usage > X.Org

X.Org X.Org on FreeBSD installation & configuration.

Reply
 
Thread Tools Display Modes
  #1  
Old October 5th, 2009, 21:20
aurora72 aurora72 is offline
Member
 
Join Date: May 2009
Location: Türkiye
Posts: 231
Thanks: 9
Thanked 1 Time in 1 Post
Default vncserver cannot init font path element /usr/local/lib/X11/fonts/Speedo/

Hello,

I've installed vnc-4.1.3_1 with the make config option of vnc server selected so it downloaded additional files named x430src-1.tgz (10MB)
x430src-2.tgz (7775kB)
x430src-3.tgz (11MB)
and successfully compiled into the executable vncserver.

After my first try, vncserver did not work and the log file read:
Code:
IBM# cat /root/.vnc/IBM.HOME.COM:3.log 
Couldn't open RGB_DB '/usr/local/lib/X11/rgb'

Xvnc Free Edition 4.1.3 - built Oct  5 2009 02:38:39
Copyright (C) 2002-2008 RealVNC Ltd.
See http://www.realvnc.com for information on VNC.
Underlying X server release 40300000, The XFree86 Project, Inc


Mon Oct  5 03:45:00 2009
 vncext:      VNC extension running!
 vncext:      Listening for VNC connections on port 5903
 vncext:      Listening for HTTP connections on port 5803
 vncext:      created VNC server for screen 0
error opening security policy file /usr/local/lib/X11/xserver/SecurityPolicy
Could not init font path element /usr/local/lib/X11/fonts/Speedo/, removing from list!
Could not init font path element /usr/local/lib/X11/fonts/CID/, removing from list!
xsetroot:  unknown color "grey"
Xlib:  extension "Generic Event Extension" missing on display ":3.0".
Xlib:  extension "Generic Event Extension" missing on display ":3.0".
twm:  invalid color name "black"
twm:  invalid color name "white"
twm:  invalid color name "slategrey"
twm:  invalid color name "gray85"
twm:  invalid color name "gray85"
twm:  invalid color name "gray85"
twm:  invalid color name "slategrey"
twm:  invalid color name "gray70"
twm:  invalid color name "gray85"
twm:  invalid color name "gray85"
twm:  invalid color name "gray85"
After this error, a friend in this forum suggested that I check the existence of the file /usr/local/lib/X11/xserver/SecurityPolicy , so I checked it and it wasn't available in that path but in:

/usr/ports/net/vnc/work/vnc-4_1_3-unixsrc/unix/xc/programs/Xserver/Xext/SecurityPolicy

Then I've copied the SecurityPolicy from this location to
/usr/local/lib/X11/xserver/SecurityPolicy, and

Code:
error opening security policy file /usr/local/lib/X11/xserver/SecurityPolicy
part of the error log is gone.

It seems that the problem is basically about the path & existence of the files so I searched for the next missing file, namely the rgb and installed the rgb :

Code:
cd /usr/ports/x11/rgb & make install clean
and the rgb part of the error is gone.

Now I'm left only with this error:
Code:
IBM# cat /root/.vnc/IBM.HOME.COM:2.log

Xvnc Free Edition 4.1.3 - built Oct  5 2009 02:38:39
Copyright (C) 2002-2008 RealVNC Ltd.
See http://www.realvnc.com for information on VNC.
Underlying X server release 40300000, The XFree86 Project, Inc


Mon Oct  5 16:32:33 2009
 vncext:      VNC extension running!
 vncext:      Listening for VNC connections on port 5902
 vncext:      Listening for HTTP connections on port 5802
 vncext:      created VNC server for screen 0
Could not init font path element /usr/local/lib/X11/fonts/Speedo/, removing from list!
Could not init font path element /usr/local/lib/X11/fonts/CID/, removing from list!
Xlib:  extension "Generic Event Extension" missing on display ":2.0".
Xlib:  extension "Generic Event Extension" missing on display ":2.0".
At this site it is reported that adding /usr/X11/bin to PATH eliminated that kind of problem. I've added "/usr/X11R6/bin" to the PATH variable at /.profile as there was no /usr/X11/bin in my FreeBSD 7.2.
So the resulting PATH is:
Code:
PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/games:/usr/local/sbin:/usr/local/bin:~/bin:/usr/X11R6/bin
But, still the # vncserver results in the same error I've given above. What should I do now?

Thanks.
__________________
FreeBSD 7.4 on PII 400 Mhz 100 Mhz FSB, 512MB PC100 SDRAM, 80GB HDD, 100Mb Ethernet, PCI Wireless.
Reply With Quote
  #2  
Old October 5th, 2009, 21:28
SirDice's Avatar
SirDice SirDice is offline
Moderator
 
Join Date: Nov 2008
Location: Rotterdam, Netherlands
Posts: 13,852
Thanks: 48
Thanked 2,061 Times in 1,890 Posts
Default

Code:
Could not init font path element /usr/local/lib/X11/fonts/Speedo/, removing from list!
Could not init font path element /usr/local/lib/X11/fonts/CID/, removing from list!
These fonts don't exist anymore since a few Xorg versions. Remove them from your xorg.conf. It's not the reason why vnc isn't working.

Code:
 vncext:      created VNC server for screen 0
This tells me it's running.
__________________
Senior UNIX Engineer at Unix Support Nederland
Experience is something you don't get until just after you need it.
Reply With Quote
  #3  
Old October 5th, 2009, 21:55
aurora72 aurora72 is offline
Member
 
Join Date: May 2009
Location: Türkiye
Posts: 231
Thanks: 9
Thanked 1 Time in 1 Post
Default

Thank you for the reply.

Checking my xorg.conf file at /etc/X11/ the section containing the font paths read:

Code:
Section "Files"
        ModulePath   "/usr/local/lib/xorg/modules"
        FontPath     "/usr/local/lib/X11/fonts/misc/"
        FontPath     "/usr/local/lib/X11/fonts/TTF/"
        FontPath     "/usr/local/lib/X11/fonts/OTF"
        FontPath     "/usr/local/lib/X11/fonts/Type1/"
        FontPath     "/usr/local/lib/X11/fonts/100dpi/"
        FontPath     "/usr/local/lib/X11/fonts/75dpi/"
EndSection
xorg.conf doesn't seem to contain Speedo and CID fonts. How should I proceed in this case?

Thanks.
__________________
FreeBSD 7.4 on PII 400 Mhz 100 Mhz FSB, 512MB PC100 SDRAM, 80GB HDD, 100Mb Ethernet, PCI Wireless.
Reply With Quote
  #4  
Old October 5th, 2009, 22:06
SirDice's Avatar
SirDice SirDice is offline
Moderator
 
Join Date: Nov 2008
Location: Rotterdam, Netherlands
Posts: 13,852
Thanks: 48
Thanked 2,061 Times in 1,890 Posts
Default

I've never used vnc, I usually install tightvnc. Tightvnc has a config file, I presume vnc has one too. The font paths might be defined in there.
__________________
Senior UNIX Engineer at Unix Support Nederland
Experience is something you don't get until just after you need it.
Reply With Quote
  #5  
Old October 5th, 2009, 22:51
aurora72 aurora72 is offline
Member
 
Join Date: May 2009
Location: Türkiye
Posts: 231
Thanks: 9
Thanked 1 Time in 1 Post
Default

There just doesn't seem to be a config file related to vnc.

This might give a clue:

Code:
IBM# find / -name "*vnc*"
/usr/local/bin/vncviewer
/usr/local/bin/vncpasswd
/usr/local/bin/vncconfig
/usr/local/bin/x0vncserver
/usr/local/bin/Xvnc
/usr/local/bin/vncserver
/usr/local/man/man1/vncconfig.1.gz
/usr/local/man/man1/Xvnc.1.gz
/usr/local/man/man1/vncviewer.1.gz
/usr/local/man/man1/vncpasswd.1.gz
/usr/local/man/man1/x0vncserver.1.gz
/usr/local/man/man1/vncserver.1.gz
/usr/local/share/WindowMaker/Pixmaps/vnc.tif
/usr/local/share/nmap/scripts/realvnc-auth-bypass.nse
/usr/local/share/vnc
/usr/local/share/vnc/classes/index.vnc
/usr/local/share/vnc/classes/vncviewer.jar
/usr/src/sys/fs/pseudofs/pseudofs_vncache.c
/usr/ports/emulators/linux_base-fc4/work/usr/share/terminfo/a/amiga-vnc
/usr/ports/net/gnome-vnc
/usr/ports/net/gnome-vnc/files/patch-gnome-vnc-viewer.c
/usr/ports/net/gnome-vnc/files/patch-vnc-viewer.c
/usr/ports/net/gtk-vnc
/usr/ports/net/gtk-vnc/files/patch-src_gvnc.h
/usr/ports/net/libvncserver
/usr/ports/net/nxserver/files/patch-nxviewer-include-vncauth.h
/usr/ports/net/nxserver/files/patch-nxviewer-libvncauth-vncauth.c
/usr/ports/net/nxserver/files/patch-nxviewer-nxviewer-vncviewer.h
/usr/ports/net/service-discovery-applet/files/patch-plugins_xvncviewer.py.in
/usr/ports/net/ssvnc
/usr/ports/net/tightvnc
/usr/ports/net/tightvnc/files/patch-Xvnc::config::cf::FreeBSD.cf
/usr/ports/net/tightvnc/files/patch-Xvnc::config::cf::Imake.cf
/usr/ports/net/tightvnc/files/patch-Xvnc::config::cf::vnclibs.def
/usr/ports/net/tightvnc/files/patch-Xvnc::config::imake::imakemdep.h
/usr/ports/net/tightvnc/files/patch-Xvnc::include::Xos.h
/usr/ports/net/tightvnc/files/patch-Xvnc::programs::Xserver::dix::Imakefile
/usr/ports/net/tightvnc/files/patch-Xvnc::programs::Xserver::hw::vnc::sockets.c
/usr/ports/net/tightvnc/files/patch-Xvnc::programs::Xserver::os::Imakefile
/usr/ports/net/tightvnc/files/patch-Xvnc::programs::Xserver::os::access.c
/usr/ports/net/tightvnc/files/patch-vncserver
/usr/ports/net/tightvnc/files/patch-vncviewer::Imakefile
/usr/ports/net/tridiavnc
/usr/ports/net/tridiavnc/files/patch-Xvnc::config::cf::Imake.cf
/usr/ports/net/tridiavnc/files/patch-Xvnc::config::cf::Imake.tmpl
/usr/ports/net/tridiavnc/files/patch-Xvnc::config::cf::vnclibs.def
/usr/ports/net/tridiavnc/files/patch-Xvnc::config::cf::xfree86.cf
/usr/ports/net/tridiavnc/files/patch-Xvnc::config::imake::imakemdep.h
/usr/ports/net/tridiavnc/files/patch-Xvnc::include::Xos.h
/usr/ports/net/tridiavnc/files/patch-Xvnc::programs::Xserver::dix::Imakefile
/usr/ports/net/tridiavnc/files/patch-Xvnc::programs::Xserver::hw::vnc::rfb.h
/usr/ports/net/tridiavnc/files/patch-Xvnc::programs::Xserver::hw::vnc::sockets.c
/usr/ports/net/tridiavnc/files/patch-vncviewer::Imakefile
/usr/ports/net/vino/files/patch-server_libvncserver_sockets.c
/usr/ports/net/vnc
/usr/ports/net/vnc/files/extra-patch-fix_Xvnc_no_valid_address
/usr/ports/net/vnc/files/patch-unix-x0vncserver-x0vncserver.cxx
/usr/ports/net/vnc/files/patch-xc-programs-Xserver-vnc-vncExtInit.cc
/usr/ports/net/vnc/files/vnc.def-patch
/usr/ports/net/vnc/work/vnc-4_1_3-unixsrc
/usr/ports/net/vnc/work/vnc-4_1_3-unixsrc/common/javabin/vncviewer.jar
/usr/ports/net/vnc/work/vnc-4_1_3-unixsrc/common/javabin/index.vnc
/usr/ports/net/vnc/work/vnc-4_1_3-unixsrc/unix/xc/programs/Xserver/Xvnc.man
/usr/ports/net/vnc/work/vnc-4_1_3-unixsrc/unix/xc/programs/Xserver/vnc
/usr/ports/net/vnc/work/vnc-4_1_3-unixsrc/unix/xc/programs/Xserver/vnc/vncExtInit.cc
/usr/ports/net/vnc/work/vnc-4_1_3-unixsrc/unix/xc/programs/Xserver/vnc/xf86vncModule.cc
/usr/ports/net/vnc/work/vnc-4_1_3-unixsrc/unix/xc/programs/Xserver/vnc/vncHooks.cc
/usr/ports/net/vnc/work/vnc-4_1_3-unixsrc/unix/xc/programs/Xserver/vnc/module/vncExtInit.cc
/usr/ports/net/vnc/work/vnc-4_1_3-unixsrc/unix/xc/programs/Xserver/vnc/module/vncHooks.cc
/usr/ports/net/vnc/work/vnc-4_1_3-unixsrc/unix/xc/programs/Xserver/vnc/module/xf86vncModule.cc
/usr/ports/net/vnc/work/vnc-4_1_3-unixsrc/unix/xc/programs/Xserver/vnc/module/vncExtInit.o
/usr/ports/net/vnc/work/vnc-4_1_3-unixsrc/unix/xc/programs/Xserver/vnc/module/vncHooks.o
/usr/ports/net/vnc/work/vnc-4_1_3-unixsrc/unix/xc/programs/Xserver/vnc/module/xf86vncModule.o
/usr/ports/net/vnc/work/vnc-4_1_3-unixsrc/unix/xc/programs/Xserver/vnc/vncExtInit.h
/usr/ports/net/vnc/work/vnc-4_1_3-unixsrc/unix/xc/programs/Xserver/vnc/vncHooks.h
/usr/ports/net/vnc/work/vnc-4_1_3-unixsrc/unix/xc/programs/Xserver/vnc/Xvnc
/usr/ports/net/vnc/work/vnc-4_1_3-unixsrc/unix/xc/programs/Xserver/vnc/Xvnc/xvnc.cc
/usr/ports/net/vnc/work/vnc-4_1_3-unixsrc/unix/xc/programs/Xserver/vnc/Xvnc/xvnc.o
/usr/ports/net/vnc/work/vnc-4_1_3-unixsrc/unix/xc/programs/Xserver/vnc/Xvnc/libxvnc.a
/usr/ports/net/vnc/work/vnc-4_1_3-unixsrc/unix/xc/programs/Xserver/vnc/vncExtInit.cc.orig
/usr/ports/net/vnc/work/vnc-4_1_3-unixsrc/unix/xc/programs/Xserver/vnc/vncExtInit.o
/usr/ports/net/vnc/work/vnc-4_1_3-unixsrc/unix/xc/programs/Xserver/vnc/vncHooks.o
/usr/ports/net/vnc/work/vnc-4_1_3-unixsrc/unix/xc/programs/Xserver/vnc/libvnc.a
/usr/ports/net/vnc/work/vnc-4_1_3-unixsrc/unix/xc/programs/Xserver/Xvnc
/usr/ports/net/vnc/work/vnc-4_1_3-unixsrc/unix/xc/config/cf/vnc.def
/usr/ports/net/vnc/work/vnc-4_1_3-unixsrc/unix/xc/config/cf/vnc.def.orig
/usr/ports/net/vnc/work/vnc-4_1_3-unixsrc/unix/x0vncserver
/usr/ports/net/vnc/work/vnc-4_1_3-unixsrc/unix/x0vncserver/x0vncserver.cxx
/usr/ports/net/vnc/work/vnc-4_1_3-unixsrc/unix/x0vncserver/x0vncserver.man
/usr/ports/net/vnc/work/vnc-4_1_3-unixsrc/unix/x0vncserver/x0vncserver.cxx.orig
/usr/ports/net/vnc/work/vnc-4_1_3-unixsrc/unix/x0vncserver/x0vncserver.o
/usr/ports/net/vnc/work/vnc-4_1_3-unixsrc/unix/x0vncserver/x0vncserver
/usr/ports/net/vnc/work/vnc-4_1_3-unixsrc/unix/vncinstall
/usr/ports/net/vnc/work/vnc-4_1_3-unixsrc/unix/vncserver.man
/usr/ports/net/vnc/work/vnc-4_1_3-unixsrc/unix/vncserver
/usr/ports/net/vnc/work/vnc-4_1_3-unixsrc/unix/vncpasswd
/usr/ports/net/vnc/work/vnc-4_1_3-unixsrc/unix/vncpasswd/vncpasswd.man
/usr/ports/net/vnc/work/vnc-4_1_3-unixsrc/unix/vncpasswd/vncpasswd.cxx
/usr/ports/net/vnc/work/vnc-4_1_3-unixsrc/unix/vncpasswd/vncpasswd.o
/usr/ports/net/vnc/work/vnc-4_1_3-unixsrc/unix/vncpasswd/vncpasswd
/usr/ports/net/vnc/work/vnc-4_1_3-unixsrc/unix/vncviewer
/usr/ports/net/vnc/work/vnc-4_1_3-unixsrc/unix/vncviewer/vncviewer.man
/usr/ports/net/vnc/work/vnc-4_1_3-unixsrc/unix/vncviewer/vncviewer.cxx
/usr/ports/net/vnc/work/vnc-4_1_3-unixsrc/unix/vncviewer/vncviewer.o
/usr/ports/net/vnc/work/vnc-4_1_3-unixsrc/unix/vncviewer/vncviewer
/usr/ports/net/vnc/work/vnc-4_1_3-unixsrc/unix/vncmkdepend
/usr/ports/net/vnc/work/vnc-4_1_3-unixsrc/unix/vncconfig
/usr/ports/net/vnc/work/vnc-4_1_3-unixsrc/unix/vncconfig/vncExt.h
/usr/ports/net/vnc/work/vnc-4_1_3-unixsrc/unix/vncconfig/vncExt.c
/usr/ports/net/vnc/work/vnc-4_1_3-unixsrc/unix/vncconfig/vncconfig.man
/usr/ports/net/vnc/work/vnc-4_1_3-unixsrc/unix/vncconfig/vncconfig.cxx
/usr/ports/net/vnc/work/vnc-4_1_3-unixsrc/unix/vncconfig/vncExt.o
/usr/ports/net/vnc/work/vnc-4_1_3-unixsrc/unix/vncconfig/vncconfig.o
/usr/ports/net/vnc/work/vnc-4_1_3-unixsrc/unix/vncconfig/vncconfig
/usr/ports/net/vnc/work/vnc-4_1_3-unixsrc/unix/vncserver.bak
/usr/ports/net/vnc/work/.extract_done.vnc._usr_local
/usr/ports/net/vnc/work/.patch_done.vnc._usr_local
/usr/ports/net/vnc/work/.configure_done.vnc._usr_local
/usr/ports/net/vnc/work/.build_done.vnc._usr_local
/usr/ports/net/vnc/work/.install_done.vnc._usr_local
/usr/ports/net/vnc2swf
/usr/ports/net/vncreflector
/usr/ports/net/vncreflector/files/vncreflector.sh.in
/usr/ports/net/x11vnc
/usr/ports/net/xrdp/files/patch-vnc__Makefile
/usr/ports/security/vnccrack
/usr/ports/vietnamese/vnconvert
/usr/ports/vietnamese/vnconvert/files/vnconvert.1
/usr/ports/x11-servers/x2vnc
/usr/ports/distfiles/xc/vnc-4_1_3-unixsrc.tar.gz
/usr/compat/linux/usr/share/terminfo/a/amiga-vnc
/var/db/pkg/vnc-4.1.3_1
/var/db/ports/vnc
/root/.vnc
I've inspected the files under /root/.vnc if they were configurable, but seemingly, none of them were configurable...
__________________
FreeBSD 7.4 on PII 400 Mhz 100 Mhz FSB, 512MB PC100 SDRAM, 80GB HDD, 100Mb Ethernet, PCI Wireless.
Reply With Quote
  #6  
Old October 6th, 2009, 08:14
SirDice's Avatar
SirDice SirDice is offline
Moderator
 
Join Date: Nov 2008
Location: Rotterdam, Netherlands
Posts: 13,852
Thanks: 48
Thanked 2,061 Times in 1,890 Posts
Default

BTW what makes you think it's not working? The output shows vnc is started. Have you tried connecting to it regardless of the warnings? What happens if you do?
__________________
Senior UNIX Engineer at Unix Support Nederland
Experience is something you don't get until just after you need it.
Reply With Quote
  #7  
Old October 6th, 2009, 11:15
aurora72 aurora72 is offline
Member
 
Join Date: May 2009
Location: Türkiye
Posts: 231
Thanks: 9
Thanked 1 Time in 1 Post
Default

Thank you for the comment.

I have renewed password with #vncpasswd and tried once more

using RealVNC viewer, i.e.

Code:
# vncviewer --> (192.168.1.253)
returned "Aborted" without the password prompt.

Just to be sure I've also tried connecting with "Chicken of the VNC" from a MAC OS X and UltraVNC from a WinXP, still no connection.

I must also mention the following:

--> The same vncserver program causes almost the same problem in my Ubuntu 9.04
--> The machines have no TCP/IP or related problem (eg.they can connect each other using ssh)
__________________
FreeBSD 7.4 on PII 400 Mhz 100 Mhz FSB, 512MB PC100 SDRAM, 80GB HDD, 100Mb Ethernet, PCI Wireless.
Reply With Quote
  #8  
Old October 6th, 2009, 12:27
SirDice's Avatar
SirDice SirDice is offline
Moderator
 
Join Date: Nov 2008
Location: Rotterdam, Netherlands
Posts: 13,852
Thanks: 48
Thanked 2,061 Times in 1,890 Posts
Default

As I've said I usually don't use vnc, you could try just deinstalling this one and installing net/tightvnc. I know that one works.
__________________
Senior UNIX Engineer at Unix Support Nederland
Experience is something you don't get until just after you need it.
Reply With Quote
  #9  
Old October 6th, 2009, 16:47
aurora72 aurora72 is offline
Member
 
Join Date: May 2009
Location: Türkiye
Posts: 231
Thanks: 9
Thanked 1 Time in 1 Post
Default

Thank you for the suggestion, i.e. use of TightVNC.

Well, after investing so much time on troubleshooting the RealVNC, I hesitate to replace it with another vnc like the tightvnc you recommend, because that kind of troubleshooting also helps me learn how things work in FreeBSD.

Ironically, I have seen this thread about TightVNC causing a similiar problem on FreeBSD.

After some further investigation, I started to realise that the content of "vncserver" (which is a Perl script) could be problematic.

Inspired by this thread I tried changing the $cmd .= -fp ... section to

Code:
$cmd .= " -fp /usr/local/lib/X11/fonts/misc/,/usr/local/lib/X11/fonts/TTF/,/usr/local/lib/X11/fonts/OTF/,/usr/local/lib/X11/font
s/Type1/,/usr/local/lib/X11/fonts/100dpi/,/usr/local/lib/X11/fonts/75dpi/";
and the

"Could not init font path element /usr/local/lib/X11/fonts/CID/, removing from list!"


error is gone, but

Xlib: extension "Generic Event Extension" missing on display ":3.0".

error still remains.

Currently, I'm working on this error...
__________________
FreeBSD 7.4 on PII 400 Mhz 100 Mhz FSB, 512MB PC100 SDRAM, 80GB HDD, 100Mb Ethernet, PCI Wireless.
Reply With Quote
  #10  
Old October 6th, 2009, 16:57
SirDice's Avatar
SirDice SirDice is offline
Moderator
 
Join Date: Nov 2008
Location: Rotterdam, Netherlands
Posts: 13,852
Thanks: 48
Thanked 2,061 Times in 1,890 Posts
Default

Quote:
Originally Posted by aurora72 View Post
Xlib: extension "Generic Event Extension" missing on display ":3.0".
As far as I know that's not really an error. It means that Xlib has a feature missing (XGE) while the server does have it. Nothing really important, it should work regardless of this message.
__________________
Senior UNIX Engineer at Unix Support Nederland
Experience is something you don't get until just after you need it.
Reply With Quote
The Following User Says Thank You to SirDice For This Useful Post:
aurora72 (October 7th, 2009)
  #11  
Old October 7th, 2009, 00:30
aurora72 aurora72 is offline
Member
 
Join Date: May 2009
Location: Türkiye
Posts: 231
Thanks: 9
Thanked 1 Time in 1 Post
Default

What you say is right, because I've finally managed to connect to it! At the final round, I 've forgotten that the vncserver's port number was automatically increasing whenever I re-run it.

At each try the port number was going like 5900 to 5901, 5902..
So at the vnc client I must have written:

vncviewer 192.168.1.253, 192.168.1.253:1, 192.168.1.253:2 respectively.

It's working now, thank you for the guidance!
__________________
FreeBSD 7.4 on PII 400 Mhz 100 Mhz FSB, 512MB PC100 SDRAM, 80GB HDD, 100Mb Ethernet, PCI Wireless.
Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
/usr/local/lib/libX11.so: undefined reference to `shmctl@FBSD_1.1' osx-addict Installation and Maintenance of FreeBSD Ports or Packages 2 November 9th, 2009 11:58
/etc/rc.d/ versus /usr/local/etc/rc.d/ rambetter General 9 August 25th, 2009 19:40
ldconfig will not link /usr/local/lib DarkenedReality General 21 August 19th, 2009 08:54
visudo: /usr/local/etc/sudoers busy, try again later MarS Installation and Maintenance of FreeBSD Ports or Packages 10 January 23rd, 2009 22:12
default local fonts Slesarev GNOME 18 December 12th, 2008 23:40


All times are GMT +1. The time now is 06:24.


Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2013, vBulletin Solutions, Inc.
The mark FreeBSD is a registered trademark of The FreeBSD Foundation and is used by The FreeBSD Project with the permission of The FreeBSD Foundation.
Web protection and acceleration provided by CloudFlare
0