Re: Connecting to DB with Static IP over the internet



I forgot to disable DHCP on the computer, so it changed every time so the
port and dmz was forward to the incorect internal ip address :)
as for the comptuer itself, it is stock Windows XP Pro with no Service Pack
installed :) the only thing i did install is the sql 2000 sp4

Thanks for the help though, i learned a whole lot from my brain freeze with
the dhcp stuff

"jebuskrust@xxxxxxxxx" wrote:

You guys are thinking too hard. Try permitting TCP/UDP access to port
5555 and any other ms sql server related ports on the server. This is a
WINDOWS XP machine. Probably with service pack 2 installed.



ARTMIC wrote:
well the Protocol= connection string works on the windows server 2000 OS
with static ip just well, but not on the Windows XP Pro machine.

i tried to do the following 2 methods for connecting:

DOES NOT WORK
Provider=sqloledb;Data Source=10.14.118.151,5555;Network
Library=DBMSSOCN;Initial Catalog=gtt;User ID=dan;Password=dan;


DOES NOT WORK
Data Source=10.14.118.151,5555;Network Library=DBMSSOCN;Initial
Catalog=gtt;User ID=dan;Password=dan;


the weird part is that it now gives me this error message:

[DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access
denied

I don't understand, the sql server is running and listening to the port, and
i have created the dan account to access the database on the sql server side

"Keith Kratochvil" wrote:

I don't think that you can specify PROTOCOL= like you did within the
connection string.

Head over to
http://www.connectionstrings.com/
and expand the "Read more" baloon under SQL Server.

You will see that you should use Network Library=DBMSSOCN

I think that I remember reading somewhere that this param should be the last
item on the connection string.


--
Keith Kratochvil


"ARTMIC" <ARTMIC@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:8796C1F4-8A1A-4390-B2E2-63FE54A5DE4B@xxxxxxxxxxxxxxxx
Hello Did anyone ever get the SQL2000 server or MSDE to work on an XP Pro
computer, with a static IP address? If so how is this done? I've done the
following:

1) setup router to forward to a port 5000
2) I setup MS SQL server to listen to this port, I check error logs, and
it
is listening, I do netstat -a and it does list that it is being listened
to.
3) I make sure the DMZ is clear for the computer that is being forward the
stuff from the internet.
4) I can use the Remote Desktop Connection to connect to that static IP
computer and it works just fine, .
5) When I try to connect to the computer through a connection string I get
the oh so informative "Invalid connection string attribute" even though I
use
the same thing with another static ip, on a win2000 server, and it works
the
connection string looks like this:
User ID=DAN;Password=DAN;Protocol=TCP/IP;Server=60.44.118.127;Port
No=5000;
6) I did setup the server network utility with the port,

I am not sure what I missed, I know on the Server2000 operating system I
did go into the remote access routing utility, but I can't find that on
Windows XP Pro,

Can anyone help me out?






.



Relevant Pages

  • Re: Connecting to Sql Server using an IP address
    ... using IP address without port number (default port number ... of SQL Server is 1433) cannot connect to the SQL Server on a remote ... name in the connection string can connect the remote machine successfully. ... Microsoft Online Community Support ...
    (microsoft.public.dotnet.framework.adonet)
  • Re: Installing Sql Server Express on Vista Home Premium
    ... It seems that your SQL Server instances are Named Instances, ... Default Instances uses 1433 TCP port by default as a Static Port but not the ... If you change your Connection String as following, ...
    (microsoft.public.sqlserver.setup)
  • Re: IIS, SQL 2000 & XPs Firewall
    ... Queries to the Data Engine must go to the port that SQL Server is listening ... More info: How to: Configure a Windows Firewall for Database Engine Access ...
    (microsoft.public.sqlserver.connect)
  • Re: Remote connection problems
    ... tab has Listen All as Yes, then the individual settings for IP1 and IP2 are ... like you are listening on dynamic ports and it is currently listening on ... different port. ... and pick a port number you like, and then restart SQL Server. ...
    (microsoft.public.sqlserver.connect)
  • Re: connect to named instance w/ non-default port
    ... it sounds like there is no need to specify the port number in the connection string. ... It listens on port 1434 for SQL Server requests by name/instance and resolves them to the particular port. ... this is well and good because I am troubleshooting a network where the Sql Server instance is reassigned a new listening port on machine restart. ...
    (microsoft.public.sqlserver.connect)