Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!news.albasani.net!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: "J.O. Aho" Newsgroups: comp.databases.mysql Subject: Re: how to connect to online database from my home machine Date: Sat, 09 Apr 2011 18:44:38 +0200 Lines: 42 Message-ID: <90bgnnFec4U1@mid.individual.net> References: <1vq9pdiivcq41$.dlg@evanplatt.sux> <4da0495d$0$65870$e4fe514c@news.xs4all.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Trace: individual.net g57Xol9hSzp0gy5rbi8lJAQrnWHtavqsPbtC2HL5hnMzmMSDma Cancel-Lock: sha1:iioYCHVizffL7fY9ciwuLo03B3I= User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.17) Gecko/20110306 Gentoo/2.0.12 SeaMonkey/2.0.12 In-Reply-To: Xref: x330-a1.tempe.blueboxinc.net comp.databases.mysql:548 The Natural Philosopher wrote: > Luuk wrote: >> On 09-04-2011 07:39, richard wrote: >>> Specifically, what is the proper URL coding for this? >>> What exactly do I replace "localhost" with? >>> As there are three different ways to do this, with neither seeming to >>> work. >>> >>> 1) example.com:3000 (for reference only) >>> 2) www.example.com:3000 >>> 3) http://example.com:3000 >>> >>> What I am attempting to do is, create a script on my local machine, that >>> will create the table on the actual domain database. >>> >>> Then, do I use the port and how do I find out exactly which port to use? >>> When I created the database on the server, I saw the port number of >>> 3306. >>> Is that the port number of the table or the database(s) location? >> >> You need to learn about firewalls... >> >> Those things tend to STOP traffic at ports that are not allowed, like >> port 3306. >> >> So, generally, you are right, and you should be able to access your >> remote database through remoteservername:3306, Where remoteservername >> can be example.com, www.example.com, or whatever.example.com... >> >> But in most, if not all, situations there is a firewall which makes this >> impossible >> > even if its enabled at mysqld level. which it may not be. In those cases you can always use ssh tunnels, if and only if you have ssh access on the remote server (which people in most cases don't). -- //Aho