Thanks for the help, i figured it out, i was so into the sql part that i
forgot to disable dhcp, in other words the damn internal ip address changed
on me every time i rebooted and that is why i couldn't connect, i filled in
the DSN, and internal computer iP and made sure to forward port and dmz to it
and it works now,
the only thing i'm wondering is do i need DMZ enabled for that internal ip?
[quoted text, click to view] "Sagaert Johan" wrote:
> I put the port in the connectionstring
>
> eg: Data Source=192.168.1.50,1433\YOURMSDEINSTANCENAME;....
>
> Hope this helps
>
>
>
> "ARTMIC" <ARTMIC@discussions.microsoft.com> wrote in message
> news:3AF938EA-A913-471B-B09A-6CE6C407177B@microsoft.com...
> > 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?
> >
>
>
hi,
[quoted text, click to view] ARTMIC wrote:
> Thanks for the help, i figured it out, i was so into the sql part
> that i forgot to disable dhcp, in other words the damn internal ip
> address changed on me every time i rebooted and that is why i
> couldn't connect, i filled in the DSN, and internal computer iP and
> made sure to forward port and dmz to it and it works now,
> the only thing i'm wondering is do i need DMZ enabled for that
> internal ip?
I would...
I actually do not "like" a SQL Server instance open to the net at all... at
least I'd provide access only trought a vpn, but perhaps this is not a
viable solution for you.. the preferred method is access only via an
application server such as IIS...
I'd require a written "order" by the CEO to open one of my instances to the
wild.wild.wild.net :D
your data, your business, your risks.. be carefull :D
--
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz http://italy.mvps.org DbaMgr2k ver 0.19.0 - DbaMgr ver 0.63.0 and further SQL Tools
--------- remove DMO to reply