Post reply

Connecting via TCP/IP

  • September 14, 2006 at 8:42 am

    #170355

    Hello everyone, here's my scenario...

    My client has one static IP. There is a server on their LAN running Win2k3 server with a static route, 10.0.0.3.

    They are running a piece of software that conflicts with Enterprise Manager (for whatever reason), but the SQL Services manager service is running, and it is a named instance, "SBSSERVER".

    I need to build a .NET app that is able to remotely connect to a sql db on this server.

    Question:

    Is it possible to connect to this database with only the SQL Service Manager running, via TCP/IP? If not, what are some options to get connected remotely without being able to install Enterprise Manager?

    TIA for any help!

    Brandon Taylor

    bTaylor Design

  • September 14, 2006 at 2:40 pm

    #660522

    As long as SQL is running and you can query the data your application should be able to work with the SQL Server.

    Thanks

    Sreejith

  • September 15, 2006 at 7:23 am

    #660687

    From the instance name it looks liek this is actually a Windows Small Business Server 03. 

    Things to consider... Because it's SBS, you may need to verify that they have the premium version which comes with SQL Server and not the Standard ed which only comes with MSDE.  Also remember this server already is probably runnign exchange and is a DC, and may be doing File and Print sharing, and running ISA.  so there's already a decent bit of overhead on the server, be careful of performance issues...

    If they are running ISA you'll need to configure that to allow remote connections to the DB.  But basically as Sreejith said if ther SQL Service is running you should be able to connect to it, once you all connections via ISA, Local Firewall etc....

    To help us help you read this[/url]For better help with performance problems please read this[/url]

  • September 15, 2006 at 8:56 am

    #660740

    Watch also the configuration of the SQL server.  It might be setup for only named pipes and not TCP/IP.

    We do access to SQL server via only TCP/IP all the time.  We often set it up to use a different port just to improve security.  Have to watch your client configurations then.

    ATBCharles Kincaid

Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply