MySQL Workbench on Remote Snow Leopard Server

How do I connect to MySQL on Snow Leopard Server using Workbench ???
I have freed up some of the permissions, such as port 3306, in the firewall section of Admin. However,
this has not done the job and need to keep a firewall on a server running remotely. It is necessary to connect to MySQL before you install the database. It is needed because you must connect to the server in order to install the database enabling the script of the SQL file. I get an error that says: "Lost connection to MySQL server at 'reading initial communication packet,' error 61." This happens when I press the button in Workbench that says: "Test Connection." I can go into MySQL and enter a password and create a database. This is necessary to load the actual data at a later time. I am also using Cold Fusion. This, too, is waiting for a connection to the MySQL server from Workbench.
Any ideas ???? Thx, Ted

If this is Adobe Workbench as I might suspect, that's probably the wrong tool to use for troubleshooting connections and related.
Try [Sequel Pro|http://www.sequelpro.com> or another similar tool.
If you're running remotely via VPN, that adds additional complexity to the configuration. As part of both local and particularly remote testing, using light-weight diagnostics (such as ping) would be warranted. This before running any juggernaut-class packages over the link.
(Put bluntly, very few juggernaut-class software packages from most any vendor will generate decent diagnostics for network errors.)

Similar Messages

  • MySql Database set up on Snow Leopard Server for Wordpress

    I am trying to set up a mySql database on the snow leopard server in order to install wordpress.
    I have played around with the MySql database settings (in the server admin window) but can't seem to figure out how to set the database name, username, and password within the Snow leopard server.
    Do I need to use third party software like Navicat to create the database and user names etc? If yes, any idea how to do that? If now, how do I create a MySql database, username and pw?
    I have put the Wordpress install folder on my Snow leopard server. When I navigate to my domain it says I need to configure wordpress by providing my database name, username and password.
    Thanks in advance.. I am struggling here.

    That's set up via the [MySQL command line|http://labs.hoffmanlabs.com/node/376]. Or you can install the (free) Sequel Pro GUI package, given you're probably more comfortable in the GUI. The steps required for Mac OS X Server are the same as most any other platform, so [launch the MySQL client per the Wordpress Codex|http://codex.wordpress.org/Installing_WordPress], and follow the instructions.

  • Remote Desktop and Snow Leopard Server

    What is the best way to use Remote Desktop with Snow Leopard Server?
    I purchased a mac mini with snow leopard server and Remote desktop so I can easily manage my 11 computers, install and upgrade software etc. etc.
    The mac mini server will basically be nothing but a server.
    I will use as my main computer a mac pro. Do I need to install Remote Desktop on the server and on my mac pro? What is the best way to deploy the services of Remote desktop and mac os x server?

    You install Apple Remote Desktop on the machine you want to control from. In this case, install on your Mac Pro. All you have to do on the clients (controlled Macs) is enable remote management in the System Preferences under Sharing. Just make sure that all your controlled Macs are up to date on their ARD version (v3.3.2) which can be taken care of from Software Update.

  • MySQL installation in Snow Leopard Server appears to be broken?

    I tried
    sudo gem install mysql -- --with-mysql-config=/usr/bin/mysql_config
    and it failed.
    The mkmf.log said (in part):
    "gcc -o conftest -I. -I/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/universal-darwin10.0 -I. -DXOPENSOURCE -DDARWIN_CSOURCE -I/usr/include -fno-omit-frame-pointer -pipe -DP1003_1BVISIBLE -DSIGNALWITH_VIOCLOSE -DSIGNALSDONT_BREAKREAD -DIGNORESIGHUPSIGQUIT -arch x86_64 -g -Os -pipe -fno-common -DENABLE_DTRACE -fno-common -pipe -fno-common conftest.c -L. -L/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib -L. -arch x86_64 -pipe -L/usr/lib -lmysqlclient -lz -lm -lruby -pipe -L/usr/lib -lmysqlclient -lz -lm -lpthread -ldl "
    ld: library not found for -lmysqlclient
    collect2: ld returned 1 exit status
    checked program was:
    /* begin */
    1: /top/
    2: int main() { return 0; }
    3: int t() { mysqlsslset(); return 0; }
    /* end */
    So, I checked mysql_config:
    Usage: /usr/bin/mysql_config [OPTIONS]
    Options:
    --cflags [-I/usr/include -fno-omit-frame-pointer -pipe -DP1003_1BVISIBLE -DSIGNALWITH_VIOCLOSE -DSIGNALSDONT_BREAKREAD -DIGNORESIGHUPSIGQUIT]
    --include [-I/usr/include]
    --libs [-pipe -L/usr/lib -lmysqlclient -lz -lm]
    --libs_r [-pipe -L/usr/lib -lmysqlclient_r -lz -lm]
    --socket [/var/mysql/mysql.sock]
    --port [0]
    --version [5.0.91]
    --libmysqld-libs [-pipe -L/usr/lib -lmysqld -lz -lm]
    Note that mysql_config appears to have been compiled with an assumption that /usr/lib
    would contain a -lmysqlclient shared library.
    Which assumption fails on my Snow Leopard Server installation:
    minisvr:~ root# ls -la /usr/lib/mysql
    ls: /usr/lib/mysql: No such file or directory
    Now, I'm reasonably certain that I have done nothing to cause this library to be missing;
    as I am also reasonably certain that the mysql_config found in /usr/bin is one shipped by
    Apple (as opposed to one I could have picked up somewhere else).
    Can anyone else out there verify: does Apple ship /usr/bin/mysql_config?
    If so, does it supply linker options like -L/usr/lib -lmysqlclient?
    If that also is true, does your /usr/lib actually contain an Apple-supplied libmysqlclient.*?
    Now, assuming that my installation is reasonably close to what Apple actually shipped,
    what should I do about it? Would I be better off to go find a source distribution,
    and build and install mysql, foregoing the Apple-supplied integration with
    management tools (e.g., using Server Manager to start/stop and monitor logfiles)?
    What do other users of mysql on Mac OS X Server do?
    Thanks,
    Tommy K

    I tried
    sudo gem install mysql -- --with-mysql-config=/usr/bin/mysql_config
    and it failed.
    The mkmf.log said (in part):
    "gcc -o conftest -I. -I/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/universal-darwin10.0 -I. -DXOPENSOURCE -DDARWIN_CSOURCE -I/usr/include -fno-omit-frame-pointer -pipe -DP1003_1BVISIBLE -DSIGNALWITH_VIOCLOSE -DSIGNALSDONT_BREAKREAD -DIGNORESIGHUPSIGQUIT -arch x86_64 -g -Os -pipe -fno-common -DENABLE_DTRACE -fno-common -pipe -fno-common conftest.c -L. -L/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib -L. -arch x86_64 -pipe -L/usr/lib -lmysqlclient -lz -lm -lruby -pipe -L/usr/lib -lmysqlclient -lz -lm -lpthread -ldl "
    ld: library not found for -lmysqlclient
    collect2: ld returned 1 exit status
    checked program was:
    /* begin */
    1: /top/
    2: int main() { return 0; }
    3: int t() { mysqlsslset(); return 0; }
    /* end */
    So, I checked mysql_config:
    Usage: /usr/bin/mysql_config [OPTIONS]
    Options:
    --cflags [-I/usr/include -fno-omit-frame-pointer -pipe -DP1003_1BVISIBLE -DSIGNALWITH_VIOCLOSE -DSIGNALSDONT_BREAKREAD -DIGNORESIGHUPSIGQUIT]
    --include [-I/usr/include]
    --libs [-pipe -L/usr/lib -lmysqlclient -lz -lm]
    --libs_r [-pipe -L/usr/lib -lmysqlclient_r -lz -lm]
    --socket [/var/mysql/mysql.sock]
    --port [0]
    --version [5.0.91]
    --libmysqld-libs [-pipe -L/usr/lib -lmysqld -lz -lm]
    Note that mysql_config appears to have been compiled with an assumption that /usr/lib
    would contain a -lmysqlclient shared library.
    Which assumption fails on my Snow Leopard Server installation:
    minisvr:~ root# ls -la /usr/lib/mysql
    ls: /usr/lib/mysql: No such file or directory
    Now, I'm reasonably certain that I have done nothing to cause this library to be missing;
    as I am also reasonably certain that the mysql_config found in /usr/bin is one shipped by
    Apple (as opposed to one I could have picked up somewhere else).
    Can anyone else out there verify: does Apple ship /usr/bin/mysql_config?
    If so, does it supply linker options like -L/usr/lib -lmysqlclient?
    If that also is true, does your /usr/lib actually contain an Apple-supplied libmysqlclient.*?
    Now, assuming that my installation is reasonably close to what Apple actually shipped,
    what should I do about it? Would I be better off to go find a source distribution,
    and build and install mysql, foregoing the Apple-supplied integration with
    management tools (e.g., using Server Manager to start/stop and monitor logfiles)?
    What do other users of mysql on Mac OS X Server do?
    Thanks,
    Tommy K

  • Trying to stop MYSQL service without success in snow leopard server

    Hello
    I trying to enabled MySQL service on snow leopard server.
    My hard drive name is "Macintosh HD2".
    I receive this message :
    Can't change dir to '/Volumes/Macintosh HD2/ServiceData/MySQL/' (Errcode: 2)
    I try to stop without success MySQL service for rename my HD without blank
    How do that please ?

    That's set up via the [MySQL command line|http://labs.hoffmanlabs.com/node/376]. Or you can install the (free) Sequel Pro GUI package, given you're probably more comfortable in the GUI. The steps required for Mac OS X Server are the same as most any other platform, so [launch the MySQL client per the Wordpress Codex|http://codex.wordpress.org/Installing_WordPress], and follow the instructions.

  • Snow Leopard Server - Remote Mail Access

    Greetings,
    I'm looking to see the best way to support remote users of an OS X server for handling mail/calendar synchronization. Some users will be in environments where they could connect directly, while others would be able to use the standard VPN services in OS X server to connect and synchronize. Others, however, would probably be limited to HTTP/HTTPS access to the server.
    I know that the web mail interface would work for this, though Squirrel Mail has never been a favorite of mine, but I'm attempting to support synchronization with their native clients. These would likely be Mail or Outlook, depending on the platform, though possibly Thunderbird would be in play.
    When reviewing options, it seems as if installing an SSL VPN software package may be the best bet, even if that's not an OS X standard software component. These would appear to allow connectivity via HTTPS, and I'm wondering if anybody has had positive experiences on OS X Server with these.
    Another option is different software all together for mail services, such as Zimbra Professional Edition. It has plugins to support directly synchronizing via HTTPS and thats certainly a good benefit, though it brings it's own infrastructure and doesn't use the OS X server internal capabilities.
    Are there other features that I am missing that would provide this type of capability within the standard Snow Leopard Server installation, or other recommended products for supporting this in a heterogeneous environment?
    Thanks!

    Hi
    Multi client full bandwidth VPN done directly on a server tends to be pretty wretched stuff. Dedicated VPN boxes are cheap enough if your firewall router does not already have VPN built into it.
    Bob

  • Small problem: how using "Remote Desktop" on Snow Leopard Server

    Hello,
    How can I login to the Mac Mini Snow Leopard Server from 2 different Macs ?
    Before I bought my Mac Mini Server in July, I asked the Apple Support if Snow Leopard Server has the equivalent of the Windows Remote Desktop functionality. He told me that it is possible. He did not tell me how, but I believed him.
    I cannot find it in the documentation. Only 1 person can use screensharing. But I need more than 1 person working on the Mac OS X Server.
    I moved our Photo library to the Mac OS X Server. With filesharing it takes 5 minutes to start iPhoto on our client iMac ( 1Gbps network). That is unworkable. So, from more iMacs users have to login to the server and start iPhoto on the server.
    Thanks for the solution.
    Hubert Anemaat

    As per Jason's reply, there are two Terminal Server products available for Mac OS X. I have been testing both, both work in the same sort of way and will allow multiple simultaneous users to connect.
    The typical approach is to (obviously) first to install one of these Terminal Server programs on your server. Then you (ideally) need another server hosting your Mac network home directories, and it needs to share the network home directories via NFS rather than AFP.
    Note: Due to the way Mac OS X handles mounting AFP shares, you cannot have two users using the same share at the same time as the login defines the privileged's and the first logins privileged's would not be suitable for the second user, this is also why you cannot use "Fast User Switching" with two network login accounts when using AFP.
    So, a client uses an RDC client (e.g. the free Microsoft Remote Desktop Client) to connect to the Terminal Server, this initiates a network login which access the users home directory via NFS.
    RDC client (Mac or PC) ------> Mac Terminal Server <------ Mac network home directories
    I have not tried iPhoto, but have tried various other applications, e.g. FileMaker, AppleScript, Microsoft Office 2004, etc. and the only problem I have hit so far is that Visual Basic in Office 2004 generates errors but Word and Excel otherwise work. Remember Office 2008 does not support Visual Basic (i.e. Macros).
    I would actually expect iPhoto to work for multiple users as long as you use NFS. Using NFS for network home directories rather than AFP has actually 'fixed' a couple of badly written applications that had problems with AFP based network home directories, e.g. Adobe Acrobat 9.
    I am using Mac OS X 10.6.4 Servers.

  • Upgrade MySQL in Snow Leopard Server

    Hi all. This is my first post.
    I have a Mac Mini Server with Mac OS X Server 10.6.8 (aka. Snow Leopard Server)
    wanted to update the native MySQL. I followed these instructions
    http://support.apple.com/kb/HT4006
    Now I know that it is parallel installation of MySQL.
    https://discussions.apple.com/message/15535136#15535136
    Finally,I installed MySQL 5.5.15 from MySQL.com (x86 dmg file)
    Now I have three MySQL servers in the system. Runs only the oldest (native 5.0.92)
    I want to:
    1) Remove unnecessary MySQL servers.
    2) I would like to MySQL service could be run in the Server Admin.app. If this is not possible to run the “MySQL Preference Pane” in System Preferences.
    If this is not possible then I would be able to run in "MySQL Preference Pane" in System Preferences.
    Working with AS is probably possible.http://www.jamesbantz.com/2010/08/08/upgrading-mysql-on-mac-os-x-10-6-snow-leopa rd-server/#more-172 (See step 6)
    Now I have a “little problem” with the distinction which files belong which MySQL.
    Please help
    Thanks

    Welcome to the forums.
    The cited Apple directions in HT4006 are for adding headers and client components for Mac OS X Server for MySQL, and not particularly for upgrading MySQL on Mac OS X Server.  (That may well cause problems.)
    How good are your pre-installation backups?  I'd roll those in, and undo the HT4006 changes, and (if you're not going to scratch this whole upgrade) follow what Mr Bantz describes in his posting.
    Irrespective of the particular path followed here, you do also still get to "own" all of these changes, including the on-going maintenance and upgrades, which means that you own any security problems, the inevitable software upgrades and updates, and whatever other fixes might be needed.
    Alternatively, consider moving to Mac OS X Server Lion (10.7), as it does not contain MySQL, so you can load whatever MySQL you want and (so long as you keep it from getting tangled with PostgreSQL) you're good to go.
    I would not generally expect to be able to use Server Admin or the other tools to use or manage your local MySQL.  The Server Admin tools are not set up for these sorts of changes and have a history of getting tangled when the underlying servers are changed.   If you do manage this goal and do have Server Admin working and whether following Mr Bantz's directions or via some other means, then your changes still might not survive any particular future Mac OS X Server upgrade, or Server Tools upgrade.  (Which means you'll have to debug and rework the changes, or find somebody that has figured out what broken and follow those instructions.)
    If you discover you have the need for these sorts of upgrades often, I'd suggest loading and using Linux or one of the BSDs.  Installing newer versions of stuff means more work and sometimes far more work, and tends to un-do what Apple provides, and tends to cause problems like you've encountered here.  In all seriousness, Linux or BSD is the platform you'll want, if you find yourself tweaking; they're set up for exactly this sort of tweaking.  Mac OS X and Mac OS X Server aims at a different market.

  • Why won't Snow Leopard server use an up to date mySQL?

    I'm about to have to throw away a perfectly good Xserve since it won't update to mySQL 5.1.33 for Moodle 2.3. I'm almost to the point of deleting snow leopard and installing Ubuntu server in its place.  I have no budget for buying an OS upgrade (our budgets have been cut >35%). so if snow leopard server cannot be upgraded (I see no technical reason for not doing so on Apple's part- I have this version on mysql running on an old FreeBSD 7 server for a trouble ticket server).
    No, upgrading to a new version of the Mac server is not an option.

    Grant, thank you so much for the quick reply.  Yes, you're right, the tower is heavy as sin!  Our more recent computers out west are iMacs which are much easier for us to deal with.  We do have the tower upright.  Bill just moved it here to our vacation house for the winter.  Is it possible [don't underestimate him] that he could have inadvertantly opened the tower DVD slot and a decidedly important part fell out during the disconnect in B'ham?  The discs don't seat themselves.  It's like they're too large by just a smidge and won't sit level in the depression.  As I close the tray the top of the opening scrapes the disc off.  It won't let it go inside so I can begin the struggle with the install itself.

  • How do I remotely access my Snow Leopard server from my Mountain Lion MacBook Air

    Does anyone know of an idiot's guide to setting up a VPN to access my server? I'm running Snow Leopard server in the office and I'd like to be able to access the server, probably just from one computer (MacBook Air runnung Mountain Lion) from home.
    I'm not sure if it complicates things or not, but the office is in an area with poor broadband and so the internet connection is via satellite broadband. The set up is a satellite modem into a Gigabit router and the server is connected to the router via an unmanaged switch.
    As an aside, I'm considering changing this set up so that the modem plugs into a Time Capsule and the server will connect directly into the TC. The desktops will then run into the server via the unmanaged switch or wirelessly via TC - any thoughts on the best set up here? Are cables into a switch better/worse than using TC's wireless facility.
    Is this something that I, as a reasonably competent computer operator but definitely not an IT expert, could do, or should I get someone in to set it up for me?
    Thanks in advance
    Jim

    VPNs aren't particularly special or weird or secret or such.  They're "just" a network connection.  A sometimes very fussy network connection, but a network connection.
    My preference is to use a firewall that includes an embedded VPN server.  This for several reasons, as it avoids trying to forward the VPN through a device that's using NAT [1], and it means you can connect to multiple devices on the target LAN, and you can connect even if the OS X Server box is down.
    Other folks will forward the VPN through NAT, and use the VPN server that's available in various versions of OS X Server.
    Forwarding a VPN through NAT does work, but can also sometimes not work.  NAT can cause some types of VPNs to get tossed off when (for instance) there's a second VPN connection arriving.
    In various cases everything connects and works the first time, and in other cases it's trial-and-error.
    With a VPN-capable firewall (which is a step above your average residential firewall), usually configuring the firewall as a L2TP server or the Cisco protocol, if you want to use the standard OS X or iOS clients.  Or PPTP — which is easier to get working — but less secure.  Once the firewall and the VPN server is set up — and that's where most of the "fun" is — then the set-up in Network Preferences is (usually) pretty simple.
    There are thousands of OS X VPN set-up articles around, but the details all hinge on the particular VPN server, and whether you're going to try to push the VPN through (for instance) that Tome Capsule and its NAT.   Until you sort out your VPN target and/or VPN client, and what sort of attacks you're securing against...
    As for this case, satellite latency is large.  The latency involved is the time it takes to the command or the text from your local Mac to the satellite ~35,786 kilometers up and then ~35,786 kilometers back down, and then the response back again.  That's about a quarter second, each way, at the speed of light.  Transferring big files is fine (once the connection is open and the transfer gets rolling), but anything interactive — such as a typical use of a VPN — is going to have a noticable lag.
    Yes, it'll be easiest to get somebody to work through your requirements and expectations, and initially set this up for you.  Or you can use this as an opportunity to read about and learn more about IP routing and networking and VPNs, too.
    [1] VPNs seek to ensure that the network connection is secure, and from a known client IP source address to the IP address of the target VPN server.  NAT explicitly obscures the network connections, and often has multiple client hosts located behind one IP address.   Put another way, the VPN and NAT software implementations are working at cross-purposes.

  • Lion server or Snow Leopard Server?

    From a quick check of postings here, my question of whether to use Lion Server or Snow Leopard server on a Mac Mini for a small office, looks to be "stay away from Lion server" Snow Leopard server just works and is easier to support.
    Most of these posts are from 2011, has anything changed where someone can say Lion is now a much better server choice now than considering Snow Leopard Server?
    It seems that most posters feel Lion server is a real step backwards, is this the case?
    Thanks in advance - Lewis

    Which services have been removed or depreicated?
    You have to bear in mind that 'removed' or 'deprecated' only really means 'no longer bundled and supported by Apple'. Just because Mac OS X Lion Server doesn't ship with a foobar server that doesn't mean you can't download and install your own foobar server. It just won't be integrated into the Server Admin apps.
    For example, Lion Server no longer ships MySQL Server. So download and install your own copy. It's not like the GUI apps gave you any control over the MySQL anyway, other than starting it up and controlling the network ports.
    Likewise for print server. Some of the advanced print features such as quotas have been removed from the GUI, but you can implement them yourself.
    Likewise with QuickTime Streaming Server, where the functionality is little more than a web service.
    What features that have been enhanced?
    Lion Server has simplified the setup of a server for small workgroups with simple requirements. If that's you then the whole experience may be enhanced since you're not swamped with a slew of options that you don't understand, or need.
    I think a lot of people were also stymied by Snow Leopard Server because they expected the GUI apps to cover all the options, which was never the case.
    So my original point stands. There is pretty much nothing you cannot do in Lion Server than you could do in Snow Leopard Server, it's just that it might not be supported by the GUI. Most serious server admins eschew Server Admin.app anyway since even Snow Leopard Server's admin app doesn't cover all the capabilities of some of the services, so you end up driving it via the command line anyway.

  • How to enter hidden SSID in Snow Leopard Server

    I am re-installing Snow Leopard Server on a Mac Mini Server (2009) from the recovery disk.  I successfully installed, using Remote Installation.  However, it did not keep my network settings.  The SSID is hidden, so normally, I would select to enter "other network".  But, in this case, that option is not showing up. What am I missing?

    Airport was enabled; however, the network name box did not have an option to "Join Other Network". I was very surprised, because I had used Airport to remotely install the OS in the first place, and that box did have the "Join Other Network" option.
    I understand that sniffing tools, used by any network-savvy person, can easily find hidden networks. As a matter of fact, most newer network selection software distributed with network card drivers are able to find and display hidden SSIDs. I just like to use the most security I possibly can, and that's one tool at my disposal. Along with WPA2 and a strong key, the hidden SSID keeps my network out of sight and mind of the casual hacker who just wants to see what's out there to pick and poke at. They're most likely to hack at the easily displayed stuff and, hopefully, ignore what they can't see. Again, just one more tool - not the best, but not totally useless, either.

  • Using ms office 2008 for mac home & student edition with snow leopard serv

    Hi all,
    I have a very particular question.
    I have a new small business starting up and we want to make full use of leopard and snow leopard server in our infrastructure. We also want to use os x for all our client machines.
    We want to use ms office 2008 for mac as our main offfice software but i believe we don't need all the uses or festures of the business edtion and i need to seek good advice and clarity on this.
    We won't ever use any microsoft exchange servers but instead willl use the apple mail servers and all the other apple server services.
    My question is, based on the fact that we will have an all apple mac os x backend and client frontend but want to use the ms office for mac as our business software, and also based on the fact that we wont use the "Build your Brand clip art, Build your skills by lynda.com, the Remote Desktop for mac 2, the Microsoft Exchange Server Support and the Microsoft Windows sharepoint services support, do we really need to go for the business edition? Can we not just use the home and student edition and get the same functionality using everything else apart form what we listed as we wont need these?
    The other question is, the Entourage 2008, Web services Edition, will this work with an apple backend instead of ms exchange server?
    Kind regards and thanks for your wise advice,
    Neil Watson

    Thanks, Kurt--I understand now. 
    One reason I was alarmed was that evidently when the tech installed Office 2008, something went awry with either the key installer or the key code, because when I finished the first two updates (12.1 and 12.2), I tried to open Entourage to see if the problem I'd been having was resolved. Instead of opening, Office gave me a message that my product key was invalid!  I did find the product key, and called the tech, who will come by to see what's wrong (he's an honest guy, so I'm sure it's a legitimate error of some kind, not a pirated copy). But the thought of installing two pages of updates and maybe running into the same glitch every time made me blanch.  So I'm glad to know that Microsoft is still doing Service Packs for 2008!

  • Windows VNC clients cannot connect to Snow Leopard Server native VNC server

    I am resurfacing the following related comment made in another post that discusses the same issue I am having with VNC on Snow Leopard. This is still an issue and I cannot connect to our Xserve's Snow Leopard Server with a VNC client on Windows.
    I don't want to install another third party VNC server onto our SL Server, and am looking for a VNC client for windows that will connect to our SL Server.
    Does anyone have any solutions?
    == QUOTED TEXT BELOW ==
    Re: Newbie: Connect Windows -> OSX Server
    Posted: Nov 4, 2009 9:26 AM in response to: Antonio Rocco
    I would politely disagree. Yes, definitely, the Mac 'Screen Sharing' app works a treat, and Apple Remote Desktop.app works as well, but I am coming from a Window's PeeCee.
    For me, connecting to my 10.5(.8) Server via tightvnc gives 'Server did not offer supported security type!". Using RealVNC to this machine states "No matching security types Do you wish to reconnect to ... ?" a telnet to this AppleVNCServer service (port 5900), shows RFB 003.889 *, or Remote Frame Buffer Major 3, minor 889.
    Also, connecting to multiple 10.6(.1) Clients with Tightvnc correctly asks for a password but then hangs at "Status: Security type requested". Using RealVNC opens, connects, asks for authentication, and exits. Telneting to this AppleVNCServer service (port 5900), also shows RFB 003.889 *.
    The Current Version of the protocol is supposed to be 3.8, that is Major version 3, minor version 8. Not 80 or 800 but Eight). http://www.realvnc.com/docs/rfbproto.pdf and I believe that tightvnc only supports up to version 3.7.
    On each station I have installed the 'old' OSXVnc.app as a service (to a unique port). OSXVnc utilizes protocol 3.3 and I can control them successfully, but that is of my own doing because of this issue.
    Now JollysFastVNC works a treat to any machine I have EVER tried to connect to. I have not tried COTVNC or any of the others (too slow for me, when they wer e around)
    Also, I just noticed that RealVNC states that their free and personal version will not connect to Mac OSX (x86 and PPC) but the Enterprise one will. I just Dl'ed the Enterprise Viewer and it gave essentially the same thing ('protocol is not valid' message, even after it asks for a password). Anyway, I am not here to hijack this thread, just trying to keep the info flowing and open.
    Maybe I am the only one with these problems but the bottom line is I cannot use Real or Tight, or UltraVNC to administer my server or clients as long as AppleVNCServer gives out the 003.889 protocol version.
    Peter
    * The ProtocolVersion message consists of 12 bytes interpreted as a string of ASCII characters in the format "RFB xxx.yyy\n" where xxx and yyy are the major and
    minor version numbers, padded with zeros.

    Searching on the net brought me to the same solution that Mr. Hoffman found as well, I was a bit skeptical at first but since he recommended it, and all my other attempts failed, it was a last resort and I have some additional notes of my own for a successful solution. Read the two links below first before doing anything, as they contribute to the solution in tandem.
    http://forums.macrumors.com/showpost.php?p=7221295&postcount=20
    http://forums.macrumors.com/showpost.php?p=9081641&postcount=28
    I should probably just create an entirely new post with all of the steps that worked for me, but it's rather straightforward nonetheless.

  • Making Snow Leopard Server services accessible through Time Capsule

    Sorry, this will be a fairly long explanation. I think this is the right forum but the question kind of spans several component elements.
    During the setup of Snow Leopard Server I let it configure the Time Capsule for services that it is providing, which I want to make available to both the local network and to computers coming in from the Internet. However, there seem to be some conflicts between Time Capsule ports and Snow Leopard ones.
    First my set-up: I have Verizon FIOS and have set up my Actiontech Router into bridge mode to the Time Capsule so that the Time Capsule grabs the public IP address. The Snow Leopard Server has a dedicated private IP from the Time Capsule through the DHCP reservation. I have a dynamic DNS setup which consistently points to the public IP address assigned to the Time Capsule. After starting services on Snow Leopard Server, I can see the port mappings created on the Time Capsule by the server allocated to the server's dedicated private IP address. However, the File Sharing (AFP, SMB) entry can't be enabled because the ports used for those services conflict with the ports opened by the Time Capsule to enable backups from client Time Machines (TCP Ports 548, 139). Therefore, any external access to those ports are going to the Time Capsule and not routed to the Snow Leopard Server.
    Two questions:
    1. Should I map the DNS hostname to the Time Capsule on the Hostnames screen on AirPort utility? While this will enable remote access to the Time Capsule (so that if my client computers are outside coming from the Internet), will this mess up remote access to the Snow Leopard Server?
    2. How do I get around the problem of the port conflicts between what Time Machine needs to get to the Time Capsule for backups versus enabling the ports for AFP and SMB on the server?

    I actually found an Apple support tip and am posting it here to answer the question:
    http://support.apple.com/kb/TS2963
    Bottom line: you can't have both devices doing file sharing unless you set up VPN access.

Maybe you are looking for