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 t
o.
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?"ARTMIC" <ARTMIC@.discussions.microsoft.com> wrote in message
news:EFA03B8C-E304-4CB4-AC76-8AE6E73FABF6@.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?
Try equating the IP number to a name in hosts and then use that name in the
connection string.
Showing posts with label address. Show all posts
Showing posts with label address. Show all posts
Sunday, March 11, 2012
Connecting to DB with Static IP over the internet
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
Try including the port at the end of the IP address as shown in
http://www.connectionstrings.com/
John
"ARTMIC" wrote:
> 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,
Have you checked WintowsXP firewall. If it turned on, you need to configure
the exception for this port.
Yuriy
"ARTMIC" wrote:
> 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
Just to check that you have seen http://support.microsoft.com/kb/287932?
John
"John Bell" wrote:
> Hi
> Try including the port at the end of the IP address as shown in
> http://www.connectionstrings.com/
> John
> "ARTMIC" wrote:
> > 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?
> >|||Thanks, i will try that, but i am pretty sure i tried all imaginable
connection strings, what gets to me is that it should work, i know the sql
server is listening to port 5000 ... i can remotely connect to that computer
over that static ip from my other computer with the Remote Desktop
Connection, so it looks ok, but why am i still having all these problems?
The funny thing is if i use the internal ip address of that computer that
connects to the router, then i can use the same connection string, (just
changing ip address) and the sql server responds, so internally it knows
about port 5000, as soon as i use the static ip, it complains about "Invalid
connection string attribute"
"John Bell" wrote:
> Hi
> Try including the port at the end of the IP address as shown in
> http://www.connectionstrings.com/
> John
> "ARTMIC" wrote:
> > 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?
> >|||Thanks, i will read through that, maybe i missed something.
i'm so frustrated by this, i did this before with win2000 server a while
back and it worked ok, but with the Win XP Pro, it is sooooooooooooo hard to
do
"John Bell" wrote:
> Hi
> Just to check that you have seen http://support.microsoft.com/kb/287932?
> John
> "John Bell" wrote:
> > Hi
> >
> > Try including the port at the end of the IP address as shown in
> > http://www.connectionstrings.com/
> >
> > John
> >
> > "ARTMIC" wrote:
> >
> > > 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?
> > >|||i Installed Win XP Pro on a test machine, and did not apply any updates to
that computer, as for the firewall, it is disabled when i'm in the netwrok
properties,
The only difference that i can recall from Windows server 2000 is that in
that operating system i modified the remote accesss routing settings. i can't
find that utility on Win XP Pro
Arghhhhh help
"Yuriy Al" wrote:
> Hi,
> Have you checked WintowsXP firewall. If it turned on, you need to configure
> the exception for this port.
> Yuriy
>
> "ARTMIC" wrote:
> > 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
Have you tried accessing this with osql or SQLPing?
http://www.sqlsecurity.com/Tools/FreeTools/tabid/65/Default.aspx
You may want to try telneting to the port.
John
"ARTMIC" wrote:
> Thanks, i will try that, but i am pretty sure i tried all imaginable
> connection strings, what gets to me is that it should work, i know the sql
> server is listening to port 5000 ... i can remotely connect to that computer
> over that static ip from my other computer with the Remote Desktop
> Connection, so it looks ok, but why am i still having all these problems?
> The funny thing is if i use the internal ip address of that computer that
> connects to the router, then i can use the same connection string, (just
> changing ip address) and the sql server responds, so internally it knows
> about port 5000, as soon as i use the static ip, it complains about "Invalid
> connection string attribute"
> "John Bell" wrote:
> > Hi
> >
> > Try including the port at the end of the IP address as shown in
> > http://www.connectionstrings.com/
> >
> > John
> >
> > "ARTMIC" wrote:
> >
> > > 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?
> > >|||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?
Thanks for the help though, those suggestions made me understand the SQL2000
software a lot more, and that sure is great, i love learning new things.
"John Bell" wrote:
> Hi
> Have you tried accessing this with osql or SQLPing?
> http://www.sqlsecurity.com/Tools/FreeTools/tabid/65/Default.aspx
> You may want to try telneting to the port.
> John
> "ARTMIC" wrote:
> > Thanks, i will try that, but i am pretty sure i tried all imaginable
> > connection strings, what gets to me is that it should work, i know the sql
> > server is listening to port 5000 ... i can remotely connect to that computer
> > over that static ip from my other computer with the Remote Desktop
> > Connection, so it looks ok, but why am i still having all these problems?
> > The funny thing is if i use the internal ip address of that computer that
> > connects to the router, then i can use the same connection string, (just
> > changing ip address) and the sql server responds, so internally it knows
> > about port 5000, as soon as i use the static ip, it complains about "Invalid
> > connection string attribute"
> >
> > "John Bell" wrote:
> >
> > > Hi
> > >
> > > Try including the port at the end of the IP address as shown in
> > > http://www.connectionstrings.com/
> > >
> > > John
> > >
> > > "ARTMIC" wrote:
> > >
> > > > 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
To access the machine from the internal network without going out over the
internet your internal IP address will be needed. You should configure your
firewall/DMZ so that access to this IP address is only allowed internally.
HTH
John
"ARTMIC" wrote:
> 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?
> Thanks for the help though, those suggestions made me understand the SQL2000
> software a lot more, and that sure is great, i love learning new things.
>
> "John Bell" wrote:
> > Hi
> >
> > Have you tried accessing this with osql or SQLPing?
> > http://www.sqlsecurity.com/Tools/FreeTools/tabid/65/Default.aspx
> >
> > You may want to try telneting to the port.
> >
> > John
> >
> > "ARTMIC" wrote:
> >
> > > Thanks, i will try that, but i am pretty sure i tried all imaginable
> > > connection strings, what gets to me is that it should work, i know the sql
> > > server is listening to port 5000 ... i can remotely connect to that computer
> > > over that static ip from my other computer with the Remote Desktop
> > > Connection, so it looks ok, but why am i still having all these problems?
> > > The funny thing is if i use the internal ip address of that computer that
> > > connects to the router, then i can use the same connection string, (just
> > > changing ip address) and the sql server responds, so internally it knows
> > > about port 5000, as soon as i use the static ip, it complains about "Invalid
> > > connection string attribute"
> > >
> > > "John Bell" wrote:
> > >
> > > > Hi
> > > >
> > > > Try including the port at the end of the IP address as shown in
> > > > http://www.connectionstrings.com/
> > > >
> > > > John
> > > >
> > > > "ARTMIC" wrote:
> > > >
> > > > > 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?
> > > > >
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
Try including the port at the end of the IP address as shown in
http://www.connectionstrings.com/
John
"ARTMIC" wrote:
> 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,
Have you checked WintowsXP firewall. If it turned on, you need to configure
the exception for this port.
Yuriy
"ARTMIC" wrote:
> 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
Just to check that you have seen http://support.microsoft.com/kb/287932?
John
"John Bell" wrote:
> Hi
> Try including the port at the end of the IP address as shown in
> http://www.connectionstrings.com/
> John
> "ARTMIC" wrote:
> > 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?
> >|||Thanks, i will try that, but i am pretty sure i tried all imaginable
connection strings, what gets to me is that it should work, i know the sql
server is listening to port 5000 ... i can remotely connect to that computer
over that static ip from my other computer with the Remote Desktop
Connection, so it looks ok, but why am i still having all these problems?
The funny thing is if i use the internal ip address of that computer that
connects to the router, then i can use the same connection string, (just
changing ip address) and the sql server responds, so internally it knows
about port 5000, as soon as i use the static ip, it complains about "Invalid
connection string attribute"
"John Bell" wrote:
> Hi
> Try including the port at the end of the IP address as shown in
> http://www.connectionstrings.com/
> John
> "ARTMIC" wrote:
> > 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?
> >|||Thanks, i will read through that, maybe i missed something.
i'm so frustrated by this, i did this before with win2000 server a while
back and it worked ok, but with the Win XP Pro, it is sooooooooooooo hard to
do
"John Bell" wrote:
> Hi
> Just to check that you have seen http://support.microsoft.com/kb/287932?
> John
> "John Bell" wrote:
> > Hi
> >
> > Try including the port at the end of the IP address as shown in
> > http://www.connectionstrings.com/
> >
> > John
> >
> > "ARTMIC" wrote:
> >
> > > 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?
> > >|||i Installed Win XP Pro on a test machine, and did not apply any updates to
that computer, as for the firewall, it is disabled when i'm in the netwrok
properties,
The only difference that i can recall from Windows server 2000 is that in
that operating system i modified the remote accesss routing settings. i can't
find that utility on Win XP Pro
Arghhhhh help
"Yuriy Al" wrote:
> Hi,
> Have you checked WintowsXP firewall. If it turned on, you need to configure
> the exception for this port.
> Yuriy
>
> "ARTMIC" wrote:
> > 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
Have you tried accessing this with osql or SQLPing?
http://www.sqlsecurity.com/Tools/FreeTools/tabid/65/Default.aspx
You may want to try telneting to the port.
John
"ARTMIC" wrote:
> Thanks, i will try that, but i am pretty sure i tried all imaginable
> connection strings, what gets to me is that it should work, i know the sql
> server is listening to port 5000 ... i can remotely connect to that computer
> over that static ip from my other computer with the Remote Desktop
> Connection, so it looks ok, but why am i still having all these problems?
> The funny thing is if i use the internal ip address of that computer that
> connects to the router, then i can use the same connection string, (just
> changing ip address) and the sql server responds, so internally it knows
> about port 5000, as soon as i use the static ip, it complains about "Invalid
> connection string attribute"
> "John Bell" wrote:
> > Hi
> >
> > Try including the port at the end of the IP address as shown in
> > http://www.connectionstrings.com/
> >
> > John
> >
> > "ARTMIC" wrote:
> >
> > > 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?
> > >|||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?
Thanks for the help though, those suggestions made me understand the SQL2000
software a lot more, and that sure is great, i love learning new things.
"John Bell" wrote:
> Hi
> Have you tried accessing this with osql or SQLPing?
> http://www.sqlsecurity.com/Tools/FreeTools/tabid/65/Default.aspx
> You may want to try telneting to the port.
> John
> "ARTMIC" wrote:
> > Thanks, i will try that, but i am pretty sure i tried all imaginable
> > connection strings, what gets to me is that it should work, i know the sql
> > server is listening to port 5000 ... i can remotely connect to that computer
> > over that static ip from my other computer with the Remote Desktop
> > Connection, so it looks ok, but why am i still having all these problems?
> > The funny thing is if i use the internal ip address of that computer that
> > connects to the router, then i can use the same connection string, (just
> > changing ip address) and the sql server responds, so internally it knows
> > about port 5000, as soon as i use the static ip, it complains about "Invalid
> > connection string attribute"
> >
> > "John Bell" wrote:
> >
> > > Hi
> > >
> > > Try including the port at the end of the IP address as shown in
> > > http://www.connectionstrings.com/
> > >
> > > John
> > >
> > > "ARTMIC" wrote:
> > >
> > > > 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
To access the machine from the internal network without going out over the
internet your internal IP address will be needed. You should configure your
firewall/DMZ so that access to this IP address is only allowed internally.
HTH
John
"ARTMIC" wrote:
> 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?
> Thanks for the help though, those suggestions made me understand the SQL2000
> software a lot more, and that sure is great, i love learning new things.
>
> "John Bell" wrote:
> > Hi
> >
> > Have you tried accessing this with osql or SQLPing?
> > http://www.sqlsecurity.com/Tools/FreeTools/tabid/65/Default.aspx
> >
> > You may want to try telneting to the port.
> >
> > John
> >
> > "ARTMIC" wrote:
> >
> > > Thanks, i will try that, but i am pretty sure i tried all imaginable
> > > connection strings, what gets to me is that it should work, i know the sql
> > > server is listening to port 5000 ... i can remotely connect to that computer
> > > over that static ip from my other computer with the Remote Desktop
> > > Connection, so it looks ok, but why am i still having all these problems?
> > > The funny thing is if i use the internal ip address of that computer that
> > > connects to the router, then i can use the same connection string, (just
> > > changing ip address) and the sql server responds, so internally it knows
> > > about port 5000, as soon as i use the static ip, it complains about "Invalid
> > > connection string attribute"
> > >
> > > "John Bell" wrote:
> > >
> > > > Hi
> > > >
> > > > Try including the port at the end of the IP address as shown in
> > > > http://www.connectionstrings.com/
> > > >
> > > > John
> > > >
> > > > "ARTMIC" wrote:
> > > >
> > > > > 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?
> > > > >
Connecting to DB with Static IP over the internet
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 t
o.
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
Try including the port at the end of the IP address as shown in
http://www.connectionstrings.com/
John
"ARTMIC" wrote:
> 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 th
e
> 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 i
t
> 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 thoug
h I use
> the same thing with another static ip, on a win2000 server, and it works t
he
> 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,
Have you checked WintowsXP firewall. If it turned on, you need to configure
the exception for this port.
Yuriy
"ARTMIC" wrote:
> 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 th
e
> 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 i
t
> 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 thoug
h I use
> the same thing with another static ip, on a win2000 server, and it works t
he
> 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
Just to check that you have seen http://support.microsoft.com/kb/287932?
John
"John Bell" wrote:
[vbcol=seagreen]
> Hi
> Try including the port at the end of the IP address as shown in
> http://www.connectionstrings.com/
> John
> "ARTMIC" wrote:
>|||Thanks, i will try that, but i am pretty sure i tried all imaginable
connection strings, what gets to me is that it should work, i know the sql
server is listening to port 5000 ... i can remotely connect to that computer
over that static ip from my other computer with the Remote Desktop
Connection, so it looks ok, but why am i still having all these problems?
The funny thing is if i use the internal ip address of that computer that
connects to the router, then i can use the same connection string, (just
changing ip address) and the sql server responds, so internally it knows
about port 5000, as soon as i use the static ip, it complains about "Invalid
connection string attribute"
"John Bell" wrote:
[vbcol=seagreen]
> Hi
> Try including the port at the end of the IP address as shown in
> http://www.connectionstrings.com/
> John
> "ARTMIC" wrote:
>|||Thanks, i will read through that, maybe i missed something.
i'm so frustrated by this, i did this before with win2000 server a while
back and it worked ok, but with the Win XP Pro, it is sooooooooooooo hard to
do
"John Bell" wrote:
[vbcol=seagreen]
> Hi
> Just to check that you have seen http://support.microsoft.com/kb/287932?
> John
> "John Bell" wrote:
>|||i Installed Win XP Pro on a test machine, and did not apply any updates to
that computer, as for the firewall, it is disabled when i'm in the netwrok
properties,
The only difference that i can recall from Windows server 2000 is that in
that operating system i modified the remote accesss routing settings. i can'
t
find that utility on Win XP Pro
Arghhhhh help
"Yuriy Al" wrote:
[vbcol=seagreen]
> Hi,
> Have you checked WintowsXP firewall. If it turned on, you need to configur
e
> the exception for this port.
> Yuriy
>
> "ARTMIC" wrote:
>|||Hi
Have you tried accessing this with osql or SQLPing?
http://www.sqlsecurity.com/Tools/Fr...65/Default.aspx
You may want to try telneting to the port.
John
"ARTMIC" wrote:
[vbcol=seagreen]
> Thanks, i will try that, but i am pretty sure i tried all imaginable
> connection strings, what gets to me is that it should work, i know the sql
> server is listening to port 5000 ... i can remotely connect to that comput
er
> over that static ip from my other computer with the Remote Desktop
> Connection, so it looks ok, but why am i still having all these problems?
> The funny thing is if i use the internal ip address of that computer that
> connects to the router, then i can use the same connection string, (just
> changing ip address) and the sql server responds, so internally it knows
> about port 5000, as soon as i use the static ip, it complains about "Inval
id
> connection string attribute"
> "John Bell" wrote:
>|||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 work
s
now,
the only thing i'm wondering is do i need DMZ enabled for that internal ip?
Thanks for the help though, those suggestions made me understand the SQL2000
software a lot more, and that sure is great, i love learning new things.
"John Bell" wrote:
[vbcol=seagreen]
> Hi
> Have you tried accessing this with osql or SQLPing?
> http://www.sqlsecurity.com/Tools/Fr...65/Default.aspx
> You may want to try telneting to the port.
> John
> "ARTMIC" wrote:
>|||Hi
To access the machine from the internal network without going out over the
internet your internal IP address will be needed. You should configure your
firewall/DMZ so that access to this IP address is only allowed internally.
HTH
John
"ARTMIC" wrote:
[vbcol=seagreen]
> 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 wo
rks
> now,
> the only thing i'm wondering is do i need DMZ enabled for that internal ip
?
> Thanks for the help though, those suggestions made me understand the SQL20
00
> software a lot more, and that sure is great, i love learning new things.
>
> "John Bell" wrote:
>
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 t
o.
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
Try including the port at the end of the IP address as shown in
http://www.connectionstrings.com/
John
"ARTMIC" wrote:
> 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 th
e
> 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 i
t
> 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 thoug
h I use
> the same thing with another static ip, on a win2000 server, and it works t
he
> 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,
Have you checked WintowsXP firewall. If it turned on, you need to configure
the exception for this port.
Yuriy
"ARTMIC" wrote:
> 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 th
e
> 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 i
t
> 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 thoug
h I use
> the same thing with another static ip, on a win2000 server, and it works t
he
> 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
Just to check that you have seen http://support.microsoft.com/kb/287932?
John
"John Bell" wrote:
[vbcol=seagreen]
> Hi
> Try including the port at the end of the IP address as shown in
> http://www.connectionstrings.com/
> John
> "ARTMIC" wrote:
>|||Thanks, i will try that, but i am pretty sure i tried all imaginable
connection strings, what gets to me is that it should work, i know the sql
server is listening to port 5000 ... i can remotely connect to that computer
over that static ip from my other computer with the Remote Desktop
Connection, so it looks ok, but why am i still having all these problems?
The funny thing is if i use the internal ip address of that computer that
connects to the router, then i can use the same connection string, (just
changing ip address) and the sql server responds, so internally it knows
about port 5000, as soon as i use the static ip, it complains about "Invalid
connection string attribute"
"John Bell" wrote:
[vbcol=seagreen]
> Hi
> Try including the port at the end of the IP address as shown in
> http://www.connectionstrings.com/
> John
> "ARTMIC" wrote:
>|||Thanks, i will read through that, maybe i missed something.
i'm so frustrated by this, i did this before with win2000 server a while
back and it worked ok, but with the Win XP Pro, it is sooooooooooooo hard to
do
"John Bell" wrote:
[vbcol=seagreen]
> Hi
> Just to check that you have seen http://support.microsoft.com/kb/287932?
> John
> "John Bell" wrote:
>|||i Installed Win XP Pro on a test machine, and did not apply any updates to
that computer, as for the firewall, it is disabled when i'm in the netwrok
properties,
The only difference that i can recall from Windows server 2000 is that in
that operating system i modified the remote accesss routing settings. i can'
t
find that utility on Win XP Pro
Arghhhhh help
"Yuriy Al" wrote:
[vbcol=seagreen]
> Hi,
> Have you checked WintowsXP firewall. If it turned on, you need to configur
e
> the exception for this port.
> Yuriy
>
> "ARTMIC" wrote:
>|||Hi
Have you tried accessing this with osql or SQLPing?
http://www.sqlsecurity.com/Tools/Fr...65/Default.aspx
You may want to try telneting to the port.
John
"ARTMIC" wrote:
[vbcol=seagreen]
> Thanks, i will try that, but i am pretty sure i tried all imaginable
> connection strings, what gets to me is that it should work, i know the sql
> server is listening to port 5000 ... i can remotely connect to that comput
er
> over that static ip from my other computer with the Remote Desktop
> Connection, so it looks ok, but why am i still having all these problems?
> The funny thing is if i use the internal ip address of that computer that
> connects to the router, then i can use the same connection string, (just
> changing ip address) and the sql server responds, so internally it knows
> about port 5000, as soon as i use the static ip, it complains about "Inval
id
> connection string attribute"
> "John Bell" wrote:
>|||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 work
s
now,
the only thing i'm wondering is do i need DMZ enabled for that internal ip?
Thanks for the help though, those suggestions made me understand the SQL2000
software a lot more, and that sure is great, i love learning new things.
"John Bell" wrote:
[vbcol=seagreen]
> Hi
> Have you tried accessing this with osql or SQLPing?
> http://www.sqlsecurity.com/Tools/Fr...65/Default.aspx
> You may want to try telneting to the port.
> John
> "ARTMIC" wrote:
>|||Hi
To access the machine from the internal network without going out over the
internet your internal IP address will be needed. You should configure your
firewall/DMZ so that access to this IP address is only allowed internally.
HTH
John
"ARTMIC" wrote:
[vbcol=seagreen]
> 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 wo
rks
> now,
> the only thing i'm wondering is do i need DMZ enabled for that internal ip
?
> Thanks for the help though, those suggestions made me understand the SQL20
00
> software a lot more, and that sure is great, i love learning new things.
>
> "John Bell" wrote:
>
Thursday, March 8, 2012
Connecting to an alias fails
Created a new alias with the SQL Server client network utility. With
the connection parameters, changed the server name to the IP address -
still no success.
Edited the Sql Server Network utility to use port 1433 to use port 0
(per another google discussion), still no success.
Any other ideas? The goal is to use the alias identically as how we
access the server name. Using the default instance of SQL Server.
Thanks,
-KevinError message? Version of SQL Server? Service packs?
Inquiring minds want to know
Kevin Hill
3NF Consulting
http://www.3nf-inc.com/NewsGroups.htm
Real-world stuff I run across with SQL Server:
http://kevin3nf.blogspot.com
"Justin" <kfwolf@.hotmail.com> wrote in message
news:1166725627.977804.61320@.42g2000cwt.googlegroups.com...
> Created a new alias with the SQL Server client network utility. With
> the connection parameters, changed the server name to the IP address -
> still no success.
> Edited the Sql Server Network utility to use port 1433 to use port 0
> (per another google discussion), still no success.
> Any other ideas? The goal is to use the alias identically as how we
> access the server name. Using the default instance of SQL Server.
> Thanks,
> -Kevin
>
the connection parameters, changed the server name to the IP address -
still no success.
Edited the Sql Server Network utility to use port 1433 to use port 0
(per another google discussion), still no success.
Any other ideas? The goal is to use the alias identically as how we
access the server name. Using the default instance of SQL Server.
Thanks,
-KevinError message? Version of SQL Server? Service packs?
Inquiring minds want to know
Kevin Hill
3NF Consulting
http://www.3nf-inc.com/NewsGroups.htm
Real-world stuff I run across with SQL Server:
http://kevin3nf.blogspot.com
"Justin" <kfwolf@.hotmail.com> wrote in message
news:1166725627.977804.61320@.42g2000cwt.googlegroups.com...
> Created a new alias with the SQL Server client network utility. With
> the connection parameters, changed the server name to the IP address -
> still no success.
> Edited the Sql Server Network utility to use port 1433 to use port 0
> (per another google discussion), still no success.
> Any other ideas? The goal is to use the alias identically as how we
> access the server name. Using the default instance of SQL Server.
> Thanks,
> -Kevin
>
Connecting to an alias fails
Created a new alias with the SQL Server client network utility. With
the connection parameters, changed the server name to the IP address -
still no success.
Edited the Sql Server Network utility to use port 1433 to use port 0
(per another google discussion), still no success.
Any other ideas? The goal is to use the alias identically as how we
access the server name. Using the default instance of SQL Server.
Thanks,
-Kevin
Error message? Version of SQL Server? Service packs?
Inquiring minds want to know
Kevin Hill
3NF Consulting
http://www.3nf-inc.com/NewsGroups.htm
Real-world stuff I run across with SQL Server:
http://kevin3nf.blogspot.com
"Justin" <kfwolf@.hotmail.com> wrote in message
news:1166725627.977804.61320@.42g2000cwt.googlegrou ps.com...
> Created a new alias with the SQL Server client network utility. With
> the connection parameters, changed the server name to the IP address -
> still no success.
> Edited the Sql Server Network utility to use port 1433 to use port 0
> (per another google discussion), still no success.
> Any other ideas? The goal is to use the alias identically as how we
> access the server name. Using the default instance of SQL Server.
> Thanks,
> -Kevin
>
the connection parameters, changed the server name to the IP address -
still no success.
Edited the Sql Server Network utility to use port 1433 to use port 0
(per another google discussion), still no success.
Any other ideas? The goal is to use the alias identically as how we
access the server name. Using the default instance of SQL Server.
Thanks,
-Kevin
Error message? Version of SQL Server? Service packs?
Inquiring minds want to know
Kevin Hill
3NF Consulting
http://www.3nf-inc.com/NewsGroups.htm
Real-world stuff I run across with SQL Server:
http://kevin3nf.blogspot.com
"Justin" <kfwolf@.hotmail.com> wrote in message
news:1166725627.977804.61320@.42g2000cwt.googlegrou ps.com...
> Created a new alias with the SQL Server client network utility. With
> the connection parameters, changed the server name to the IP address -
> still no success.
> Edited the Sql Server Network utility to use port 1433 to use port 0
> (per another google discussion), still no success.
> Any other ideas? The goal is to use the alias identically as how we
> access the server name. Using the default instance of SQL Server.
> Thanks,
> -Kevin
>
Subscribe to:
Posts (Atom)