SQL Server 2000 & MS SP2

Am using Powerbuilder 8.0.4 and SQL Server 2000. Have just installed
Windows XP SP2, and can no longer connect to my SQL Server db. Someone
suggested that I need to reset the port for the db at 1033. Is this the
correct port number, and how do I change the port?

re: SQL Server 2000 & MS SP2

You don't reset the port itself.
What hapened is that XP SP2 by default enables built-in firewall blocking
incoming and outgoing connections
on all the ports other than the service ones (like http:80)
What you can do is just disable the firewall - for this you right click on
your network connection
and somewhere in properties you will find firewall settings

But frankly, SP2 sucks, half of my apps didn't want to start after i've
installed the beast, and teh only remedy was to reinstall the OS.

HIH
Andrey


"William F. O'Neill" <wfoneill@bellsouth.net> wrote in message
news:cj7Zc.936$Np2.234@bignews4.bellsouth.net...[color=blue]
> Am using Powerbuilder 8.0.4 and SQL Server 2000. Have just installed
> Windows XP SP2, and can no longer connect to my SQL Server db. Someone
> suggested that I need to reset the port for the db at 1033. Is this the
> correct port number, and how do I change the port?
>
>
>[/color]

re: SQL Server 2000 & MS SP2

I disabled the firewall, and still cannot connect; get error message about
connect(). Any other suggestions? Should I attempt to reinstall SQL Server
2000?


"Muzzy" <leyandrew@yahoo.com> wrote in message
news:VD7Zc.78561$9d6.23796@attbi_s54...[color=blue]
> You don't reset the port itself.
> What hapened is that XP SP2 by default enables built-in firewall blocking
> incoming and outgoing connections
> on all the ports other than the service ones (like http:80)
> What you can do is just disable the firewall - for this you right click on
> your network connection
> and somewhere in properties you will find firewall settings
>
> But frankly, SP2 sucks, half of my apps didn't want to start after i've
> installed the beast, and teh only remedy was to reinstall the OS.
>
> HIH
> Andrey
>
>
> "William F. O'Neill" <wfoneill@bellsouth.net> wrote in message
> news:cj7Zc.936$Np2.234@bignews4.bellsouth.net...[color=green]
>> Am using Powerbuilder 8.0.4 and SQL Server 2000. Have just installed
>> Windows XP SP2, and can no longer connect to my SQL Server db. Someone
>> suggested that I need to reset the port for the db at 1033. Is this the
>> correct port number, and how do I change the port?
>>
>>
>>[/color]
>
>[/color]

re: SQL Server 2000 & MS SP2

Well, first of all, SQL Server by default listens on port 1433, not 1033.
Then, if you have a visual studio.net, you can try to run the following
function:

Public Function IsSQLServerAvailable( _
ByVal ServerAddress _
As String) As Boolean
' Tests an SQL Server connection by
' name or IP address
Try
' Attempt to get server address
Dim objIPHost As New System.Net.IPHostEntry()
objIPHost = _
System.Net.Dns.Resolve(ServerAddress)
Dim objAddress As System.Net.IPAddress
objAddress = objIPHost.AddressList(0)
' Connect to port 1433, most common SQL Server
' port. If your target is different, change here
Dim objTCP As System.Net.Sockets.TcpClient = _
New System.Net.Sockets.TcpClient()
objTCP.Connect(objAddress, 1433)
' No problems (hurrah!)
' Close and cleanup
objTCP.Close()
objTCP = Nothing
objAddress = Nothing
objIPHost = Nothing
' Return success
Return True

Catch ex As Exception
' Server unavailable, return fail value
Return False
End Try
End Function
It basicly tests if theer is a server running at address 'ServerAddress' on
port 1433, or whatever port is setup on your system.Also, if it's not a big
issue for you meaning that it's just a test server, not a production one,
i'd recommend to reinstall SQL Server, because as i've posted earlier,
Service pack 2 SUCKS real bad. I literaly couldn't find half of my programs'
dlls after the beast got it's paws on my CPU :)I wish i was at that
computer, i might figure out something more valuable, but in the meantime if
i was you i'd first reinstall Windows XP to get rid of Service Pack 2, and
then reinstall the rest... Pain in the ass, man, but Microsucks teaches us
patience and respect for repetitive work :)Anyway, can you access your sql
server using Query Analizer or Enterprise Manager? If no, then your database
is not running. period.



"William F. O'Neill" <wfoneill@bellsouth.net> wrote in message
news:E%9Zc.65399$_h.18708@bignews3.bellsouth.net.. .[color=blue]
> I disabled the firewall, and still cannot connect; get error message about
> connect(). Any other suggestions? Should I attempt to reinstall SQL[/color]
Server[color=blue]
> 2000?
>
>
> "Muzzy" <leyandrew@yahoo.com> wrote in message
> news:VD7Zc.78561$9d6.23796@attbi_s54...[color=green]
> > You don't reset the port itself.
> > What hapened is that XP SP2 by default enables built-in firewall[/color][/color]
blocking[color=blue][color=green]
> > incoming and outgoing connections
> > on all the ports other than the service ones (like http:80)
> > What you can do is just disable the firewall - for this you right click[/color][/color]
on[color=blue][color=green]
> > your network connection
> > and somewhere in properties you will find firewall settings
> >
> > But frankly, SP2 sucks, half of my apps didn't want to start after i've
> > installed the beast, and teh only remedy was to reinstall the OS.
> >
> > HIH
> > Andrey
> >
> >
> > "William F. O'Neill" <wfoneill@bellsouth.net> wrote in message
> > news:cj7Zc.936$Np2.234@bignews4.bellsouth.net...[color=darkred]
> >> Am using Powerbuilder 8.0.4 and SQL Server 2000. Have just installed
> >> Windows XP SP2, and can no longer connect to my SQL Server db. Someone
> >> suggested that I need to reset the port for the db at 1033. Is this[/color][/color][/color]
the[color=blue][color=green][color=darkred]
> >> correct port number, and how do I change the port?
> >>
> >>
> >>[/color]
> >
> >[/color]
>
>[/color]

re: SQL Server 2000 & MS SP2

[posted and mailed, pleaes reply in news]

William F. O'Neill (wfoneill@bellsouth.net) writes:[color=blue]
> I disabled the firewall, and still cannot connect; get error message
> about connect(). Any other suggestions? Should I attempt to reinstall
> SQL Server 2000?[/color]

"Muzzy"'s suggestion to turn off the firewall was really bad, and his
suggestion to reinstall Windows XP SP2 is even worse. First of all, if
you really need to go back, just uninstall the service pack. You did
check the option to save backup files didn't you.

For the record, I have had very few problems with Windows XP SP2.

It is difficult to say what the exact problems may be in your case, since
you don't give much details or error messages. Are you running PowerBuilder
and SQL Server on the same machine?

There are means in Windows Firewall to make exceptions so that the firewall
does not block port 1433, and you do this per network. Now, here is a very
important thing: if that network is exposed directly to the Internet, do
not unblock SQL Server! Least of all if you are using SQL Server
authentication. You are only asking for uninvited guests.

This KB article collects a whole set of KB articles on SQL 2000 and XP SP2.
http://support.microsoft.com/?kbid=841249.


--
Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techinf...2000/books.asp

re: SQL Server 2000 & MS SP2

Erland Sommarskog wrote:

[color=blue]
> "Muzzy"'s suggestion to turn off the firewall was really bad,[/color]
Well, it bothers more than helps for me at least. But frankly, i have a
hardware firewall :)
[color=blue]
> and his
> suggestion to reinstall Windows XP SP2 is even worse. First of all, if
> you really need to go back, just uninstall the service pack. You did
> check the option to save backup files didn't you.[/color]
Well, i suggested to reinstall Windows XP, not SP2.
Regarding rolling back the SP2 instalation, it failed for me - it did
complete, killing all my drivers(network, printer, scanner, video) and
also deleted a few dll's which were installed and used by some other
programms, whch was kinda weird.

[color=blue]
>
> For the record, I have had very few problems with Windows XP SP2.
>
> It is difficult to say what the exact problems may be in your case, since
> you don't give much details or error messages. Are you running PowerBuilder
> and SQL Server on the same machine?
>
> There are means in Windows Firewall to make exceptions so that the firewall
> does not block port 1433, and you do this per network. Now, here is a very
> important thing: if that network is exposed directly to the Internet, do
> not unblock SQL Server! Least of all if you are using SQL Server
> authentication. You are only asking for uninvited guests.[/color]

Well, again, check if you can connect to the database thru Query
Analyzer or Enterprise Manager.