Well it is the default SQL port. Usually a SQL box would be in a DMZ, therefore not available to the web. Even just add a cross-over cable from machine. You could change the default port to something different, but doing so is really security through obscurity, a port scan will find it anyway (with few exceptions:-) ) A decent firewall, and a properly setup win2000 box (ipsec, permissions, lockdown) is really the solution.
Justin > -----Original Message----- > From: samcfug [mailto:doug@;samcfug.org] > Sent: 06 November 2002 19:09 > To: CF-Linux > Subject: Re: Communicating with SQL2000 database from a Red Hat server > > > Thanks all of you for your tips and tricks - I got a unique port > number assigned, the proper > security set, a hard to guess user name and password, and the > connection is successful now. > > I was a little concerned about that port 1433 deal, because of > all the Pacific Rim and European > computers that are constantly hitting that port. > > ===================================== > Douglas White > group Manager > mailto:doug@;samcfug.org > http://www.samcfug.org > ===================================== > ----- Original Message ----- > >From: "Justin MacCarthy" <[EMAIL PROTECTED]> > To: "CF-Linux" <[EMAIL PROTECTED]> > Sent: Wednesday, November 06, 2002 8:59 AM > Subject: RE: Communicating with SQL2000 database from a Red Hat server > > > | One other slightly confusing issue in this area, is the fact you can run > | many "instances" of SQL server, which run on different ports. not just > | 1433... > | > | Just something to look out for > | > | Justin > | > | > -----Original Message----- > | > From: Mark A. Kruger - CFG [mailto:mkruger@;cfwebtools.com] > | > Sent: 06 November 2002 14:43 > | > To: CF-Linux > | > Subject: RE: Communicating with SQL2000 database from a Red Hat server > | > > | > > | > Steve, > | > > | > On the SQL side, make sure that the server is supporting the > tcp/ip net > | > library and you are using "mixed" security. Tcp/ip is supported > | > by default, > | > but you have to choose "mixed" security when you install the > SQL server. > | > Some folks running AD also remove tcp/ip in favor of named > pipes (though > | > this is a mistake IMO). > | > > | > -mk > | > > | > -----Original Message----- > | > >From: Steve Johnson [mailto:steve@;stevejohnson.org] > | > Sent: Tuesday, November 05, 2002 4:53 PM > | > To: CF-Linux > | > Subject: Re: Communicating with SQL2000 database from a Red Hat server > | > > | > > | > >Does anyone know what it takes to connect up a CF application > | > >running on Apache/Linux to communicate > | > >with an SQL2000 database on a windows DB server? Are there ODBC > | > >drivers out there which can be > | > >used? Which machine do they go on? > | > > | > that's one of the included JDBC drivers. you just install CFMX and > | > go set up the datasource in the CF Administrator. > | > > | > make sure you're using RedHat 7.2 or earlier. > | > > | > steve > | > > | > > | > ______________________________________________________________________ Structure your ColdFusion code with Fusebox. Get the official book at http://www.fusionauthority.com/bkinfo.cfm ------------------------------------------------------------------------------ Archives: http://www.mail-archive.com/cf-linux%40houseoffusion.com/ To Unsubscribe visit http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_linux or send a message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
