Good day,
I have recently installed a 2 node cluster server with SQL 2000 SP3 in my
network. and have found out that users connect to the Virtual cluster server
inorder to receive SQL services but they get the replay for the physical
node that holds the SQL.
I was wondering if this configuration can be changed so that the SQL servers
answers back with the IP address of the virtual server and not the physical
cluster.
the problem is that im working with a Firewall and we would like to restrict
the number of IP address that we expose to the world.
Thanks in advance
Oren Zippori
This is one of the wierd but unavoidable artifacts of clustering. You will
have to expose the host computer's IP addresses through the firewall.
Personally, I like to run my database servers on an restricted segment, just
to minimize the impact of stuff like this.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Oren Zippori" <orenzp@.hotmail.com> wrote in message
news:eu17pHbwFHA.3548@.tk2msftngp13.phx.gbl...
> Good day,
> I have recently installed a 2 node cluster server with SQL 2000 SP3 in my
> network. and have found out that users connect to the Virtual cluster
> server inorder to receive SQL services but they get the replay for the
> physical node that holds the SQL.
> I was wondering if this configuration can be changed so that the SQL
> servers answers back with the IP address of the virtual server and not the
> physical cluster.
> the problem is that im working with a Firewall and we would like to
> restrict the number of IP address that we expose to the world.
> Thanks in advance
> Oren Zippori
>
|||Thanks for the information on this Geoff.
"Geoff N. Hiten" <SRDBA@.Careerbuilder.com> wrote in message
news:uNRVXAgwFHA.664@.tk2msftngp13.phx.gbl...
> This is one of the wierd but unavoidable artifacts of clustering. You
> will have to expose the host computer's IP addresses through the firewall.
> Personally, I like to run my database servers on an restricted segment,
> just to minimize the impact of stuff like this.
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
> "Oren Zippori" <orenzp@.hotmail.com> wrote in message
> news:eu17pHbwFHA.3548@.tk2msftngp13.phx.gbl...
>
Showing posts with label connect. Show all posts
Showing posts with label connect. Show all posts
Tuesday, March 27, 2012
Saturday, February 25, 2012
Close connection of SQLExpress!
Hi,
I write a .NET Windows Form that connect to SQLExpress datafile. After updating data, I want to zip the .mdf file and send email. However, I got an exeption that the .mdf file is used by other thread so I cant zip. Even I try to close all connection, I still cant zip.
Is there any way to detach/unlock .mdf file connecting by SQLExpress?
MA.
Hi,
if you are sure you closed down all conenctions, you can use the sp_detach command to detach the database. if you want to close all connection from the server side first you will have to use the ALTER DATABASE command first and change the state of the database to a SINGLe or admin mode.
HTH, Jens K. Suessmeyer.
http://www.sqlserver2005.de
|||Hi,
Unfortunaterly, I dont control the connection but I want to force to close all connection from the client side (using C# code).
MA.
|||Hi MA,
Jens is exactly correct, you'll need to force the database into single user mode:
ALTER DATABASE pubs
SET SINGLE_USER
WITH ROLLBACK IMMEDIATE
This will rollback all transactions and then you can detach the database as you like. I'm not sure what you mean you don't control the connections. If you can not connect to the database, then you can not close it's connections and you will not be able to close the connections.
Mike
Friday, February 24, 2012
Clients not installing
Getting this error...
SMS Client Configuration Manager cannot connect to the machine
"ComputerName". The operating system reported error 1314: A required
privilege is not held by the client.
Possible cause: The client is not accessible.
Solution: Verify that the client is connected to the network and that the
SMS Service account or (if specified) the SMS Client Remote Installation
account have the required privileges, as specified in the SMS documentation.
Does the account I specified in Connection Accounts need to have local admin
perms? How can I double check?
Jason
Crap wrong group...sorry.
"JasonMeyer" <jason.meyer@.nospam.isd623.org> wrote in message
news:euwoiFFPFHA.3072@.TK2MSFTNGP09.phx.gbl...
> Getting this error...
> SMS Client Configuration Manager cannot connect to the machine
> "ComputerName". The operating system reported error 1314: A required
> privilege is not held by the client.
> Possible cause: The client is not accessible.
> Solution: Verify that the client is connected to the network and that the
> SMS Service account or (if specified) the SMS Client Remote Installation
> account have the required privileges, as specified in the SMS
> documentation.
> Does the account I specified in Connection Accounts need to have local
> admin perms? How can I double check?
> Jason
>
SMS Client Configuration Manager cannot connect to the machine
"ComputerName". The operating system reported error 1314: A required
privilege is not held by the client.
Possible cause: The client is not accessible.
Solution: Verify that the client is connected to the network and that the
SMS Service account or (if specified) the SMS Client Remote Installation
account have the required privileges, as specified in the SMS documentation.
Does the account I specified in Connection Accounts need to have local admin
perms? How can I double check?
Jason
Crap wrong group...sorry.
"JasonMeyer" <jason.meyer@.nospam.isd623.org> wrote in message
news:euwoiFFPFHA.3072@.TK2MSFTNGP09.phx.gbl...
> Getting this error...
> SMS Client Configuration Manager cannot connect to the machine
> "ComputerName". The operating system reported error 1314: A required
> privilege is not held by the client.
> Possible cause: The client is not accessible.
> Solution: Verify that the client is connected to the network and that the
> SMS Service account or (if specified) the SMS Client Remote Installation
> account have the required privileges, as specified in the SMS
> documentation.
> Does the account I specified in Connection Accounts need to have local
> admin perms? How can I double check?
> Jason
>
Clients connect via Named Pipes even though its disabled
We've got SQL 2000 clients (standard install, no sp) who are connecting
to our SQL 2000 Servers with Named Pipes even though we've disabled
named pipes in the client network utility. They should be connecting
via tcp/ip. Any ideas on what could be causing this?
Hi Gary,
How are you determining that the client is connecting using named pipes? Is
there a chance that your connection string is prefixed with "np:"? If so,
this will override any client network settings. Otherwise, this is probably
the result of the last connection being cached. One way around this would
be to force the connection to use tcp/ip and this will overwrite the cache.
Il-Sung
Il-Sung Lee
Program Manager -- SQL Server Protocols
Microsoft Corp.
This posting is provided "AS IS" with no warranties, and confers no rights.
"Gary" <gary.noon@.tradeweb.com> wrote in message
news:1118352084.179815.156620@.g14g2000cwa.googlegr oups.com...
> We've got SQL 2000 clients (standard install, no sp) who are connecting
> to our SQL 2000 Servers with Named Pipes even though we've disabled
> named pipes in the client network utility. They should be connecting
> via tcp/ip. Any ideas on what could be causing this?
>
to our SQL 2000 Servers with Named Pipes even though we've disabled
named pipes in the client network utility. They should be connecting
via tcp/ip. Any ideas on what could be causing this?
Hi Gary,
How are you determining that the client is connecting using named pipes? Is
there a chance that your connection string is prefixed with "np:"? If so,
this will override any client network settings. Otherwise, this is probably
the result of the last connection being cached. One way around this would
be to force the connection to use tcp/ip and this will overwrite the cache.
Il-Sung
Il-Sung Lee
Program Manager -- SQL Server Protocols
Microsoft Corp.
This posting is provided "AS IS" with no warranties, and confers no rights.
"Gary" <gary.noon@.tradeweb.com> wrote in message
news:1118352084.179815.156620@.g14g2000cwa.googlegr oups.com...
> We've got SQL 2000 clients (standard install, no sp) who are connecting
> to our SQL 2000 Servers with Named Pipes even though we've disabled
> named pipes in the client network utility. They should be connecting
> via tcp/ip. Any ideas on what could be causing this?
>
Clients connect via Named Pipes even though its disabled
We've got SQL 2000 clients (standard install, no sp) who are connecting
to our SQL 2000 Servers with Named Pipes even though we've disabled
named pipes in the client network utility. They should be connecting
via tcp/ip. Any ideas on what could be causing this?Hi Gary,
How are you determining that the client is connecting using named pipes? Is
there a chance that your connection string is prefixed with "np:"? If so,
this will override any client network settings. Otherwise, this is probably
the result of the last connection being cached. One way around this would
be to force the connection to use tcp/ip and this will overwrite the cache.
Il-Sung
Il-Sung Lee
Program Manager -- SQL Server Protocols
Microsoft Corp.
This posting is provided "AS IS" with no warranties, and confers no rights.
"Gary" <gary.noon@.tradeweb.com> wrote in message
news:1118352084.179815.156620@.g14g2000cwa.googlegroups.com...
> We've got SQL 2000 clients (standard install, no sp) who are connecting
> to our SQL 2000 Servers with Named Pipes even though we've disabled
> named pipes in the client network utility. They should be connecting
> via tcp/ip. Any ideas on what could be causing this?
>
to our SQL 2000 Servers with Named Pipes even though we've disabled
named pipes in the client network utility. They should be connecting
via tcp/ip. Any ideas on what could be causing this?Hi Gary,
How are you determining that the client is connecting using named pipes? Is
there a chance that your connection string is prefixed with "np:"? If so,
this will override any client network settings. Otherwise, this is probably
the result of the last connection being cached. One way around this would
be to force the connection to use tcp/ip and this will overwrite the cache.
Il-Sung
Il-Sung Lee
Program Manager -- SQL Server Protocols
Microsoft Corp.
This posting is provided "AS IS" with no warranties, and confers no rights.
"Gary" <gary.noon@.tradeweb.com> wrote in message
news:1118352084.179815.156620@.g14g2000cwa.googlegroups.com...
> We've got SQL 2000 clients (standard install, no sp) who are connecting
> to our SQL 2000 Servers with Named Pipes even though we've disabled
> named pipes in the client network utility. They should be connecting
> via tcp/ip. Any ideas on what could be causing this?
>
Sunday, February 19, 2012
client to client connection
hi we have a sql 2k installed on one server and 2 clients installed with sql server 2005 express..
clients pc are winxp..is it possible to connect from one client to one client pc using the sql express?
thanksBy default, SQL Server Express is not configured to accept remote connections, which helps reduce the risk of attack via the SQL Server service. If you do need to access your Express server from other machines, you can enable remote connections using the Surface Area Configuration tool.
You will probably need to open the TCP port your Express servers are listening to in your firewall as well. The default port number is 1433.
Thursday, February 16, 2012
Client Network Utility cannot create alias for VPN SQL server connection?
I am trying to connect two SQL servers in different non-trusted domains.
SQLServer11 in Domain A and SQLServer22 in domain B. This is through a VPN
connection. Domain A has the VPN server. On SQLServer22 I could ping
SQLServer11.mydomain.local at IP address 192.168.100.50. On SQLServer22 I
use the client network utility to create an alias for SQLServer11 as
follows:
Network Libraries: TCP/IP
Server name: 192.168.100.50
Port No: 1433
Server alias: SQLServer11
Then I registered the new SQLServer11 in enterprise manager. But I keep
getting the error message "SQL server does not exist or access
denied.ConnectionOpen(Connect())" .
Why is this so? And how can I rectify the problem'If you use ping -a <ip address> does it bring back the correct name for the
server? If you ping SQLServer11 does it return the proper ip address? If
you are using NT authentication to register then try SQL authentication..
Verify that it is using port 1433 and that SQL Server is actually listening
on TCP/IP.
Rand
This posting is provided "as is" with no warranties and confers no rights.
SQLServer11 in Domain A and SQLServer22 in domain B. This is through a VPN
connection. Domain A has the VPN server. On SQLServer22 I could ping
SQLServer11.mydomain.local at IP address 192.168.100.50. On SQLServer22 I
use the client network utility to create an alias for SQLServer11 as
follows:
Network Libraries: TCP/IP
Server name: 192.168.100.50
Port No: 1433
Server alias: SQLServer11
Then I registered the new SQLServer11 in enterprise manager. But I keep
getting the error message "SQL server does not exist or access
denied.ConnectionOpen(Connect())" .
Why is this so? And how can I rectify the problem'If you use ping -a <ip address> does it bring back the correct name for the
server? If you ping SQLServer11 does it return the proper ip address? If
you are using NT authentication to register then try SQL authentication..
Verify that it is using port 1433 and that SQL Server is actually listening
on TCP/IP.
Rand
This posting is provided "as is" with no warranties and confers no rights.
Tuesday, February 14, 2012
Client connectivity to SQL Server 2005
Hello!
I am developing an application that will connect to a SQL Server 2005
(including Analysis Services) database. The SQL database will reside on
a server, not on the client my app will be installed on.
I am creating a setup program and I guess that I need to redistribute
the client connectivity components in mysetup program. The problem is
that I don't know which files contains the client connectivity. As my
software might be downloaded from the internet, I need a fool-prof
solution.
I've searched msdn, but not found any useful info regarding this
delicate matter.
TIA
Clarkieclarkbones@.rocketmail.com schrieb:
> Hello!
> I am developing an application that will connect to a SQL Server 2005
> (including Analysis Services) database. The SQL database will reside on
> a server, not on the client my app will be installed on.
> I am creating a setup program and I guess that I need to redistribute
> the client connectivity components in mysetup program. The problem is
> that I don't know which files contains the client connectivity. As my
> software might be downloaded from the internet, I need a fool-prof
> solution.
> I've searched msdn, but not found any useful info regarding this
> delicate matter.
>
> TIA
> Clarkie
For general SQL Server connectivity (pre Sql Server 2005) you need to
link them to the MDAC Download Site available to the public:
http://www.msdn.microsoft.com/data/mdac/
For SQL Server 2005 Client connectivity you need to link them to the
SQL Native Client
http://www.msdn.microsoft.com/data/...ve/default.aspx
btw: On these sites you may also find information on howto include these
packages direcly into your own software and if its allowed to do so or not.
hth
Stefka
I am developing an application that will connect to a SQL Server 2005
(including Analysis Services) database. The SQL database will reside on
a server, not on the client my app will be installed on.
I am creating a setup program and I guess that I need to redistribute
the client connectivity components in mysetup program. The problem is
that I don't know which files contains the client connectivity. As my
software might be downloaded from the internet, I need a fool-prof
solution.
I've searched msdn, but not found any useful info regarding this
delicate matter.
TIA
Clarkieclarkbones@.rocketmail.com schrieb:
> Hello!
> I am developing an application that will connect to a SQL Server 2005
> (including Analysis Services) database. The SQL database will reside on
> a server, not on the client my app will be installed on.
> I am creating a setup program and I guess that I need to redistribute
> the client connectivity components in mysetup program. The problem is
> that I don't know which files contains the client connectivity. As my
> software might be downloaded from the internet, I need a fool-prof
> solution.
> I've searched msdn, but not found any useful info regarding this
> delicate matter.
>
> TIA
> Clarkie
For general SQL Server connectivity (pre Sql Server 2005) you need to
link them to the MDAC Download Site available to the public:
http://www.msdn.microsoft.com/data/mdac/
For SQL Server 2005 Client connectivity you need to link them to the
SQL Native Client
http://www.msdn.microsoft.com/data/...ve/default.aspx
btw: On these sites you may also find information on howto include these
packages direcly into your own software and if its allowed to do so or not.
hth
Stefka
Client connection
When client side connect to the sql server using sql client tools, they see
that error.
"Warning:The client and server codepages do not match. some ANSI character
mappings may not be possible"
is it the problem on charcter set?
in sql server, it is english OS/sql server
in client side, it maybe chinese/english OSHi,
This warning is raised when comparing the NT ANSI
codepage with the SQL Server codepage. It is not raised
by comparing code pages between SQL installations. You
can ignore this message since it doesn't prevent you
from connecting to it.
Sincerely,
William Wang
Microsoft Online Partner Support
Get Secure! - <www.microsoft.com/security>
========================================
=============
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from your issue.
========================================
=============
This posting is provided "AS IS" with no warranties, and
confers no rights.
--
>From: "Test" <TEst@.test.com>
>Subject: Client connection
>Date: Fri, 31 Dec 2004 09:54:23 +0800
>Lines: 13
>X-Priority: 3
>X-MSMail-Priority: Normal
>X-Newsreader: Microsoft Outlook Express 6.00.2800.1437
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
>Message-ID: <eNYTout7EHA.2552@.TK2MSFTNGP09.phx.gbl>
>Newsgroups: microsoft.public.sqlserver.server
>NNTP-Posting-Host: 210.3.41.157
>Path:
cpmsftngxa10.phx.gbl!TK2MSFTNGXS01.phx.gbl!cpmsftngxa06.p
hx.gbl!TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFT
NGP09.phx.gbl
>Xref: cpmsftngxa10.phx.gbl
microsoft.public.sqlserver.server:372772
>X-Tomcat-NG: microsoft.public.sqlserver.server
>When client side connect to the sql server using sql
client tools, they see
>that error.
>"Warning:The client and server codepages do not match.
some ANSI character
>mappings may not be possible"
>is it the problem on charcter set?
>in sql server, it is english OS/sql server
>in client side, it maybe chinese/english OS
>
>
that error.
"Warning:The client and server codepages do not match. some ANSI character
mappings may not be possible"
is it the problem on charcter set?
in sql server, it is english OS/sql server
in client side, it maybe chinese/english OSHi,
This warning is raised when comparing the NT ANSI
codepage with the SQL Server codepage. It is not raised
by comparing code pages between SQL installations. You
can ignore this message since it doesn't prevent you
from connecting to it.
Sincerely,
William Wang
Microsoft Online Partner Support
Get Secure! - <www.microsoft.com/security>
========================================
=============
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from your issue.
========================================
=============
This posting is provided "AS IS" with no warranties, and
confers no rights.
--
>From: "Test" <TEst@.test.com>
>Subject: Client connection
>Date: Fri, 31 Dec 2004 09:54:23 +0800
>Lines: 13
>X-Priority: 3
>X-MSMail-Priority: Normal
>X-Newsreader: Microsoft Outlook Express 6.00.2800.1437
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
>Message-ID: <eNYTout7EHA.2552@.TK2MSFTNGP09.phx.gbl>
>Newsgroups: microsoft.public.sqlserver.server
>NNTP-Posting-Host: 210.3.41.157
>Path:
cpmsftngxa10.phx.gbl!TK2MSFTNGXS01.phx.gbl!cpmsftngxa06.p
hx.gbl!TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFT
NGP09.phx.gbl
>Xref: cpmsftngxa10.phx.gbl
microsoft.public.sqlserver.server:372772
>X-Tomcat-NG: microsoft.public.sqlserver.server
>When client side connect to the sql server using sql
client tools, they see
>that error.
>"Warning:The client and server codepages do not match.
some ANSI character
>mappings may not be possible"
>is it the problem on charcter set?
>in sql server, it is english OS/sql server
>in client side, it maybe chinese/english OS
>
>
Client connection
When client side connect to the sql server using sql client tools, they see
that error.
"Warning:The client and server codepages do not match. some ANSI character
mappings may not be possible"
is it the problem on charcter set?
in sql server, it is english OS/sql server
in client side, it maybe chinese/english OS
Hi,
This warning is raised when comparing the NT ANSI
codepage with the SQL Server codepage. It is not raised
by comparing code pages between SQL installations. You
can ignore this message since it doesn't prevent you
from connecting to it.
Sincerely,
William Wang
Microsoft Online Partner Support
Get Secure! - <www.microsoft.com/security>
================================================== ===
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and
confers no rights.
--
>From: "Test" <TEst@.test.com>
>Subject: Client connection
>Date: Fri, 31 Dec 2004 09:54:23 +0800
>Lines: 13
>X-Priority: 3
>X-MSMail-Priority: Normal
>X-Newsreader: Microsoft Outlook Express 6.00.2800.1437
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
>Message-ID: <eNYTout7EHA.2552@.TK2MSFTNGP09.phx.gbl>
>Newsgroups: microsoft.public.sqlserver.server
>NNTP-Posting-Host: 210.3.41.157
>Path:
cpmsftngxa10.phx.gbl!TK2MSFTNGXS01.phx.gbl!cpmsftn gxa06.p
hx.gbl!TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl! TK2MSFT
NGP09.phx.gbl
>Xref: cpmsftngxa10.phx.gbl
microsoft.public.sqlserver.server:372772
>X-Tomcat-NG: microsoft.public.sqlserver.server
>When client side connect to the sql server using sql
client tools, they see
>that error.
>"Warning:The client and server codepages do not match.
some ANSI character
>mappings may not be possible"
>is it the problem on charcter set?
>in sql server, it is english OS/sql server
>in client side, it maybe chinese/english OS
>
>
that error.
"Warning:The client and server codepages do not match. some ANSI character
mappings may not be possible"
is it the problem on charcter set?
in sql server, it is english OS/sql server
in client side, it maybe chinese/english OS
Hi,
This warning is raised when comparing the NT ANSI
codepage with the SQL Server codepage. It is not raised
by comparing code pages between SQL installations. You
can ignore this message since it doesn't prevent you
from connecting to it.
Sincerely,
William Wang
Microsoft Online Partner Support
Get Secure! - <www.microsoft.com/security>
================================================== ===
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and
confers no rights.
--
>From: "Test" <TEst@.test.com>
>Subject: Client connection
>Date: Fri, 31 Dec 2004 09:54:23 +0800
>Lines: 13
>X-Priority: 3
>X-MSMail-Priority: Normal
>X-Newsreader: Microsoft Outlook Express 6.00.2800.1437
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
>Message-ID: <eNYTout7EHA.2552@.TK2MSFTNGP09.phx.gbl>
>Newsgroups: microsoft.public.sqlserver.server
>NNTP-Posting-Host: 210.3.41.157
>Path:
cpmsftngxa10.phx.gbl!TK2MSFTNGXS01.phx.gbl!cpmsftn gxa06.p
hx.gbl!TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl! TK2MSFT
NGP09.phx.gbl
>Xref: cpmsftngxa10.phx.gbl
microsoft.public.sqlserver.server:372772
>X-Tomcat-NG: microsoft.public.sqlserver.server
>When client side connect to the sql server using sql
client tools, they see
>that error.
>"Warning:The client and server codepages do not match.
some ANSI character
>mappings may not be possible"
>is it the problem on charcter set?
>in sql server, it is english OS/sql server
>in client side, it maybe chinese/english OS
>
>
Client connection
When client side connect to the sql server using sql client tools, they see
that error.
"Warning:The client and server codepages do not match. some ANSI character
mappings may not be possible"
is it the problem on charcter set?
in sql server, it is english OS/sql server
in client side, it maybe chinese/english OSHi,
This warning is raised when comparing the NT ANSI
codepage with the SQL Server codepage. It is not raised
by comparing code pages between SQL installations. You
can ignore this message since it doesn't prevent you
from connecting to it.
Sincerely,
William Wang
Microsoft Online Partner Support
Get Secure! - <www.microsoft.com/security>
=====================================================When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from your issue.
=====================================================This posting is provided "AS IS" with no warranties, and
confers no rights.
--
>From: "Test" <TEst@.test.com>
>Subject: Client connection
>Date: Fri, 31 Dec 2004 09:54:23 +0800
>Lines: 13
>X-Priority: 3
>X-MSMail-Priority: Normal
>X-Newsreader: Microsoft Outlook Express 6.00.2800.1437
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
>Message-ID: <eNYTout7EHA.2552@.TK2MSFTNGP09.phx.gbl>
>Newsgroups: microsoft.public.sqlserver.server
>NNTP-Posting-Host: 210.3.41.157
>Path:
cpmsftngxa10.phx.gbl!TK2MSFTNGXS01.phx.gbl!cpmsftngxa06.p
hx.gbl!TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFT
NGP09.phx.gbl
>Xref: cpmsftngxa10.phx.gbl
microsoft.public.sqlserver.server:372772
>X-Tomcat-NG: microsoft.public.sqlserver.server
>When client side connect to the sql server using sql
client tools, they see
>that error.
>"Warning:The client and server codepages do not match.
some ANSI character
>mappings may not be possible"
>is it the problem on charcter set?
>in sql server, it is english OS/sql server
>in client side, it maybe chinese/english OS
>
>
that error.
"Warning:The client and server codepages do not match. some ANSI character
mappings may not be possible"
is it the problem on charcter set?
in sql server, it is english OS/sql server
in client side, it maybe chinese/english OSHi,
This warning is raised when comparing the NT ANSI
codepage with the SQL Server codepage. It is not raised
by comparing code pages between SQL installations. You
can ignore this message since it doesn't prevent you
from connecting to it.
Sincerely,
William Wang
Microsoft Online Partner Support
Get Secure! - <www.microsoft.com/security>
=====================================================When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from your issue.
=====================================================This posting is provided "AS IS" with no warranties, and
confers no rights.
--
>From: "Test" <TEst@.test.com>
>Subject: Client connection
>Date: Fri, 31 Dec 2004 09:54:23 +0800
>Lines: 13
>X-Priority: 3
>X-MSMail-Priority: Normal
>X-Newsreader: Microsoft Outlook Express 6.00.2800.1437
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
>Message-ID: <eNYTout7EHA.2552@.TK2MSFTNGP09.phx.gbl>
>Newsgroups: microsoft.public.sqlserver.server
>NNTP-Posting-Host: 210.3.41.157
>Path:
cpmsftngxa10.phx.gbl!TK2MSFTNGXS01.phx.gbl!cpmsftngxa06.p
hx.gbl!TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFT
NGP09.phx.gbl
>Xref: cpmsftngxa10.phx.gbl
microsoft.public.sqlserver.server:372772
>X-Tomcat-NG: microsoft.public.sqlserver.server
>When client side connect to the sql server using sql
client tools, they see
>that error.
>"Warning:The client and server codepages do not match.
some ANSI character
>mappings may not be possible"
>is it the problem on charcter set?
>in sql server, it is english OS/sql server
>in client side, it maybe chinese/english OS
>
>
Client connect with static Port (over Dynamic)
Hi all
We have a server in our DMZ which need to talk (SECURLEY) with SQL 2000 i
have done this...by configuring a really tight rule on our firewall. This
trafic only needs to be inbound to SQL.
However it would appear that though the SQL Server listenes on port the
client 1433 The clien port which is posting the info to SQL is Dynamic.
Can i specify that my Client only connect using a pre specified port which i
can then allow in my Firewall rule...
Kind Regards
Paul
Depends on the client - how the client is connecting, from
where, how many, what app, etc. You can use the client
network utility and create an alias for the server. You can
set the port in the alias you create.
Or you can specify the port in the connection string - set
the data source to the IP or server name followed by a comma
and then the port number:
Data Source=xxx.xxx.xxx.xxx,1433;
-Sue
On Fri, 2 Feb 2007 04:50:00 -0800, PK
<PK@.discussions.microsoft.com> wrote:
>Hi all
>We have a server in our DMZ which need to talk (SECURLEY) with SQL 2000 i
>have done this...by configuring a really tight rule on our firewall. This
>trafic only needs to be inbound to SQL.
>However it would appear that though the SQL Server listenes on port the
>client 1433 The clien port which is posting the info to SQL is Dynamic.
>Can i specify that my Client only connect using a pre specified port which i
>can then allow in my Firewall rule...
>Kind Regards
>Paul
We have a server in our DMZ which need to talk (SECURLEY) with SQL 2000 i
have done this...by configuring a really tight rule on our firewall. This
trafic only needs to be inbound to SQL.
However it would appear that though the SQL Server listenes on port the
client 1433 The clien port which is posting the info to SQL is Dynamic.
Can i specify that my Client only connect using a pre specified port which i
can then allow in my Firewall rule...
Kind Regards
Paul
Depends on the client - how the client is connecting, from
where, how many, what app, etc. You can use the client
network utility and create an alias for the server. You can
set the port in the alias you create.
Or you can specify the port in the connection string - set
the data source to the IP or server name followed by a comma
and then the port number:
Data Source=xxx.xxx.xxx.xxx,1433;
-Sue
On Fri, 2 Feb 2007 04:50:00 -0800, PK
<PK@.discussions.microsoft.com> wrote:
>Hi all
>We have a server in our DMZ which need to talk (SECURLEY) with SQL 2000 i
>have done this...by configuring a really tight rule on our firewall. This
>trafic only needs to be inbound to SQL.
>However it would appear that though the SQL Server listenes on port the
>client 1433 The clien port which is posting the info to SQL is Dynamic.
>Can i specify that my Client only connect using a pre specified port which i
>can then allow in my Firewall rule...
>Kind Regards
>Paul
Client connect to SQL SERVER 2000
Hello,
I have one SQL Server 2000 that has been installed into a domain,
having allowed "Windows and SQL Server" authentication and using as
connectivity options Named Pipes and TCP/ip - 1433
On every client computer that is also a domain member I can set up
without any problems DSNs (data source names), and connect to the SQL Server.
My problem is on another computer that is not a member of this
domain and on which I can not set any kind of connections to SQL Server, I`ve
tried setting up also a DSN (using an SQL Server account)and connect from
Excel and even install the SQL Server Connectivity Tools, and tried with
Query Analyzer but still I wasnt able to connect to the server.
The error I get is: Unable to connect to the SQL Server: The
server doesn't exist or access denied.
It must be some SQL Server specific settings as the network
connectivity is OK
Any ideas ...?
Thank You,
Razvan Dragomir,
MCSA, Exchange & Windows System Administrator
Try connecting to sql from the non-domain box using QA and an explicit
login. If it works, then try same login and password from your app as
opposed to using windows auth.
TheSQLGuru
President
Indicium Resources, Inc.
"Razvan Dragomir" <RazvanDragomir@.discussions.microsoft.com> wrote in
message news:F249BDA3-6D56-41E4-85E0-79110A1A9404@.microsoft.com...
> Hello,
> I have one SQL Server 2000 that has been installed into a domain,
> having allowed "Windows and SQL Server" authentication and using as
> connectivity options Named Pipes and TCP/ip - 1433
> On every client computer that is also a domain member I can set up
> without any problems DSNs (data source names), and connect to the SQL
> Server.
> My problem is on another computer that is not a member of this
> domain and on which I can not set any kind of connections to SQL Server,
> I`ve
> tried setting up also a DSN (using an SQL Server account)and connect from
> Excel and even install the SQL Server Connectivity Tools, and tried with
> Query Analyzer but still I wasnt able to connect to the server.
> The error I get is: Unable to connect to the SQL Server: The
> server doesn't exist or access denied.
> It must be some SQL Server specific settings as the network
> connectivity is OK
> Any ideas ...?
> Thank You,
> --
> Razvan Dragomir,
> MCSA, Exchange & Windows System Administrator
>
|||Hi,
I tried and it doesnt work (i`ve used a valid SQL Login)...there is
another interesting thing..SQL is set to answer on port 1433 (default), but
if I scan this port from the non-domain workstation it`s like it`s not
opened, but it`s the same if i scan it from inside the domain where it also
doesn`t respond but I can Connect though...
Razvan Dragomir,
MCSA, Exchange & Windows System Administrator
"TheSQLGuru" wrote:
> Try connecting to sql from the non-domain box using QA and an explicit
> login. If it works, then try same login and password from your app as
> opposed to using windows auth.
>
> --
> TheSQLGuru
> President
> Indicium Resources, Inc.
> "Razvan Dragomir" <RazvanDragomir@.discussions.microsoft.com> wrote in
> message news:F249BDA3-6D56-41E4-85E0-79110A1A9404@.microsoft.com...
>
>
|||Firewall issue seems most likely culprit. Or TCP/IP isn't enabled as a
network protocol in sql server? Can you connect using QA and explicit ip
address as the server name?
TheSQLGuru
President
Indicium Resources, Inc.
"Razvan Dragomir" <RazvanDragomir@.discussions.microsoft.com> wrote in
message news:FBA2A6A8-90DF-4316-BF0A-B82ECB0D2D9C@.microsoft.com...[vbcol=seagreen]
> Hi,
> I tried and it doesnt work (i`ve used a valid SQL Login)...there is
> another interesting thing..SQL is set to answer on port 1433 (default),
> but
> if I scan this port from the non-domain workstation it`s like it`s not
> opened, but it`s the same if i scan it from inside the domain where it
> also
> doesn`t respond but I can Connect though...
> --
> Razvan Dragomir,
> MCSA, Exchange & Windows System Administrator
>
> "TheSQLGuru" wrote:
|||Hi,
Thx for the answers.....I don`t have any firewall between the
workstations and the server, I`m using TCP/IP and Named Pipes, and it`s
working to connect with IP address from QA, from inside the domain...I also
don`t have any firewall set for non domain clients...I`m just thinking if by
default Win2k3/SQL Server blocks connections from outside the domain...
Razvan Dragomir,
MCSA, Exchange & Windows System Administrator
"TheSQLGuru" wrote:
> Firewall issue seems most likely culprit. Or TCP/IP isn't enabled as a
> network protocol in sql server? Can you connect using QA and explicit ip
> address as the server name?
> --
> TheSQLGuru
> President
> Indicium Resources, Inc.
> "Razvan Dragomir" <RazvanDragomir@.discussions.microsoft.com> wrote in
> message news:FBA2A6A8-90DF-4316-BF0A-B82ECB0D2D9C@.microsoft.com...
>
>
I have one SQL Server 2000 that has been installed into a domain,
having allowed "Windows and SQL Server" authentication and using as
connectivity options Named Pipes and TCP/ip - 1433
On every client computer that is also a domain member I can set up
without any problems DSNs (data source names), and connect to the SQL Server.
My problem is on another computer that is not a member of this
domain and on which I can not set any kind of connections to SQL Server, I`ve
tried setting up also a DSN (using an SQL Server account)and connect from
Excel and even install the SQL Server Connectivity Tools, and tried with
Query Analyzer but still I wasnt able to connect to the server.
The error I get is: Unable to connect to the SQL Server: The
server doesn't exist or access denied.
It must be some SQL Server specific settings as the network
connectivity is OK
Any ideas ...?
Thank You,
Razvan Dragomir,
MCSA, Exchange & Windows System Administrator
Try connecting to sql from the non-domain box using QA and an explicit
login. If it works, then try same login and password from your app as
opposed to using windows auth.
TheSQLGuru
President
Indicium Resources, Inc.
"Razvan Dragomir" <RazvanDragomir@.discussions.microsoft.com> wrote in
message news:F249BDA3-6D56-41E4-85E0-79110A1A9404@.microsoft.com...
> Hello,
> I have one SQL Server 2000 that has been installed into a domain,
> having allowed "Windows and SQL Server" authentication and using as
> connectivity options Named Pipes and TCP/ip - 1433
> On every client computer that is also a domain member I can set up
> without any problems DSNs (data source names), and connect to the SQL
> Server.
> My problem is on another computer that is not a member of this
> domain and on which I can not set any kind of connections to SQL Server,
> I`ve
> tried setting up also a DSN (using an SQL Server account)and connect from
> Excel and even install the SQL Server Connectivity Tools, and tried with
> Query Analyzer but still I wasnt able to connect to the server.
> The error I get is: Unable to connect to the SQL Server: The
> server doesn't exist or access denied.
> It must be some SQL Server specific settings as the network
> connectivity is OK
> Any ideas ...?
> Thank You,
> --
> Razvan Dragomir,
> MCSA, Exchange & Windows System Administrator
>
|||Hi,
I tried and it doesnt work (i`ve used a valid SQL Login)...there is
another interesting thing..SQL is set to answer on port 1433 (default), but
if I scan this port from the non-domain workstation it`s like it`s not
opened, but it`s the same if i scan it from inside the domain where it also
doesn`t respond but I can Connect though...
Razvan Dragomir,
MCSA, Exchange & Windows System Administrator
"TheSQLGuru" wrote:
> Try connecting to sql from the non-domain box using QA and an explicit
> login. If it works, then try same login and password from your app as
> opposed to using windows auth.
>
> --
> TheSQLGuru
> President
> Indicium Resources, Inc.
> "Razvan Dragomir" <RazvanDragomir@.discussions.microsoft.com> wrote in
> message news:F249BDA3-6D56-41E4-85E0-79110A1A9404@.microsoft.com...
>
>
|||Firewall issue seems most likely culprit. Or TCP/IP isn't enabled as a
network protocol in sql server? Can you connect using QA and explicit ip
address as the server name?
TheSQLGuru
President
Indicium Resources, Inc.
"Razvan Dragomir" <RazvanDragomir@.discussions.microsoft.com> wrote in
message news:FBA2A6A8-90DF-4316-BF0A-B82ECB0D2D9C@.microsoft.com...[vbcol=seagreen]
> Hi,
> I tried and it doesnt work (i`ve used a valid SQL Login)...there is
> another interesting thing..SQL is set to answer on port 1433 (default),
> but
> if I scan this port from the non-domain workstation it`s like it`s not
> opened, but it`s the same if i scan it from inside the domain where it
> also
> doesn`t respond but I can Connect though...
> --
> Razvan Dragomir,
> MCSA, Exchange & Windows System Administrator
>
> "TheSQLGuru" wrote:
|||Hi,
Thx for the answers.....I don`t have any firewall between the
workstations and the server, I`m using TCP/IP and Named Pipes, and it`s
working to connect with IP address from QA, from inside the domain...I also
don`t have any firewall set for non domain clients...I`m just thinking if by
default Win2k3/SQL Server blocks connections from outside the domain...
Razvan Dragomir,
MCSA, Exchange & Windows System Administrator
"TheSQLGuru" wrote:
> Firewall issue seems most likely culprit. Or TCP/IP isn't enabled as a
> network protocol in sql server? Can you connect using QA and explicit ip
> address as the server name?
> --
> TheSQLGuru
> President
> Indicium Resources, Inc.
> "Razvan Dragomir" <RazvanDragomir@.discussions.microsoft.com> wrote in
> message news:FBA2A6A8-90DF-4316-BF0A-B82ECB0D2D9C@.microsoft.com...
>
>
Client connect to SQL SERVER 2000
Hello,
I have one SQL Server 2000 that has been installed into a domain,
having allowed "Windows and SQL Server" authentication and using as
connectivity options Named Pipes and TCP/ip - 1433
On every client computer that is also a domain member I can set up
without any problems DSNs (data source names), and connect to the SQL Server
.
My problem is on another computer that is not a member of this
domain and on which I can not set any kind of connections to SQL Server, I`v
e
tried setting up also a DSN (using an SQL Server account)and connect from
Excel and even install the SQL Server Connectivity Tools, and tried with
Query Analyzer but still I wasnt able to connect to the server.
The error I get is: Unable to connect to the SQL Server: The
server doesn't exist or access denied.
It must be some SQL Server specific settings as the network
connectivity is OK
Any ideas ...?
Thank You,
--
Razvan Dragomir,
MCSA, Exchange & Windows System AdministratorTry connecting to sql from the non-domain box using QA and an explicit
login. If it works, then try same login and password from your app as
opposed to using windows auth.
TheSQLGuru
President
Indicium Resources, Inc.
"Razvan Dragomir" <RazvanDragomir@.discussions.microsoft.com> wrote in
message news:F249BDA3-6D56-41E4-85E0-79110A1A9404@.microsoft.com...
> Hello,
> I have one SQL Server 2000 that has been installed into a domain,
> having allowed "Windows and SQL Server" authentication and using as
> connectivity options Named Pipes and TCP/ip - 1433
> On every client computer that is also a domain member I can set up
> without any problems DSNs (data source names), and connect to the SQL
> Server.
> My problem is on another computer that is not a member of this
> domain and on which I can not set any kind of connections to SQL Server,
> I`ve
> tried setting up also a DSN (using an SQL Server account)and connect from
> Excel and even install the SQL Server Connectivity Tools, and tried with
> Query Analyzer but still I wasnt able to connect to the server.
> The error I get is: Unable to connect to the SQL Server: The
> server doesn't exist or access denied.
> It must be some SQL Server specific settings as the network
> connectivity is OK
> Any ideas ...?
> Thank You,
> --
> Razvan Dragomir,
> MCSA, Exchange & Windows System Administrator
>|||Hi,
I tried and it doesnt work (i`ve used a valid SQL Login)...there is
another interesting thing..SQL is set to answer on port 1433 (default), but
if I scan this port from the non-domain workstation it`s like it`s not
opened, but it`s the same if i scan it from inside the domain where it also
doesn`t respond but I can Connect though...
--
Razvan Dragomir,
MCSA, Exchange & Windows System Administrator
"TheSQLGuru" wrote:
> Try connecting to sql from the non-domain box using QA and an explicit
> login. If it works, then try same login and password from your app as
> opposed to using windows auth.
>
> --
> TheSQLGuru
> President
> Indicium Resources, Inc.
> "Razvan Dragomir" <RazvanDragomir@.discussions.microsoft.com> wrote in
> message news:F249BDA3-6D56-41E4-85E0-79110A1A9404@.microsoft.com...
>
>|||Firewall issue seems most likely culprit. Or TCP/IP isn't enabled as a
network protocol in sql server? Can you connect using QA and explicit ip
address as the server name?
TheSQLGuru
President
Indicium Resources, Inc.
"Razvan Dragomir" <RazvanDragomir@.discussions.microsoft.com> wrote in
message news:FBA2A6A8-90DF-4316-BF0A-B82ECB0D2D9C@.microsoft.com...[vbcol=seagreen]
> Hi,
> I tried and it doesnt work (i`ve used a valid SQL Login)...there is
> another interesting thing..SQL is set to answer on port 1433 (default),
> but
> if I scan this port from the non-domain workstation it`s like it`s not
> opened, but it`s the same if i scan it from inside the domain where it
> also
> doesn`t respond but I can Connect though...
> --
> Razvan Dragomir,
> MCSA, Exchange & Windows System Administrator
>
> "TheSQLGuru" wrote:
>|||Hi,
Thx for the answers.....I don`t have any firewall between the
workstations and the server, I`m using TCP/IP and Named Pipes, and it`s
working to connect with IP address from QA, from inside the domain...I also
don`t have any firewall set for non domain clients...I`m just thinking if by
default Win2k3/SQL Server blocks connections from outside the domain...
--
Razvan Dragomir,
MCSA, Exchange & Windows System Administrator
"TheSQLGuru" wrote:
> Firewall issue seems most likely culprit. Or TCP/IP isn't enabled as a
> network protocol in sql server? Can you connect using QA and explicit ip
> address as the server name?
> --
> TheSQLGuru
> President
> Indicium Resources, Inc.
> "Razvan Dragomir" <RazvanDragomir@.discussions.microsoft.com> wrote in
> message news:FBA2A6A8-90DF-4316-BF0A-B82ECB0D2D9C@.microsoft.com...
>
>
I have one SQL Server 2000 that has been installed into a domain,
having allowed "Windows and SQL Server" authentication and using as
connectivity options Named Pipes and TCP/ip - 1433
On every client computer that is also a domain member I can set up
without any problems DSNs (data source names), and connect to the SQL Server
.
My problem is on another computer that is not a member of this
domain and on which I can not set any kind of connections to SQL Server, I`v
e
tried setting up also a DSN (using an SQL Server account)and connect from
Excel and even install the SQL Server Connectivity Tools, and tried with
Query Analyzer but still I wasnt able to connect to the server.
The error I get is: Unable to connect to the SQL Server: The
server doesn't exist or access denied.
It must be some SQL Server specific settings as the network
connectivity is OK
Any ideas ...?
Thank You,
--
Razvan Dragomir,
MCSA, Exchange & Windows System AdministratorTry connecting to sql from the non-domain box using QA and an explicit
login. If it works, then try same login and password from your app as
opposed to using windows auth.
TheSQLGuru
President
Indicium Resources, Inc.
"Razvan Dragomir" <RazvanDragomir@.discussions.microsoft.com> wrote in
message news:F249BDA3-6D56-41E4-85E0-79110A1A9404@.microsoft.com...
> Hello,
> I have one SQL Server 2000 that has been installed into a domain,
> having allowed "Windows and SQL Server" authentication and using as
> connectivity options Named Pipes and TCP/ip - 1433
> On every client computer that is also a domain member I can set up
> without any problems DSNs (data source names), and connect to the SQL
> Server.
> My problem is on another computer that is not a member of this
> domain and on which I can not set any kind of connections to SQL Server,
> I`ve
> tried setting up also a DSN (using an SQL Server account)and connect from
> Excel and even install the SQL Server Connectivity Tools, and tried with
> Query Analyzer but still I wasnt able to connect to the server.
> The error I get is: Unable to connect to the SQL Server: The
> server doesn't exist or access denied.
> It must be some SQL Server specific settings as the network
> connectivity is OK
> Any ideas ...?
> Thank You,
> --
> Razvan Dragomir,
> MCSA, Exchange & Windows System Administrator
>|||Hi,
I tried and it doesnt work (i`ve used a valid SQL Login)...there is
another interesting thing..SQL is set to answer on port 1433 (default), but
if I scan this port from the non-domain workstation it`s like it`s not
opened, but it`s the same if i scan it from inside the domain where it also
doesn`t respond but I can Connect though...
--
Razvan Dragomir,
MCSA, Exchange & Windows System Administrator
"TheSQLGuru" wrote:
> Try connecting to sql from the non-domain box using QA and an explicit
> login. If it works, then try same login and password from your app as
> opposed to using windows auth.
>
> --
> TheSQLGuru
> President
> Indicium Resources, Inc.
> "Razvan Dragomir" <RazvanDragomir@.discussions.microsoft.com> wrote in
> message news:F249BDA3-6D56-41E4-85E0-79110A1A9404@.microsoft.com...
>
>|||Firewall issue seems most likely culprit. Or TCP/IP isn't enabled as a
network protocol in sql server? Can you connect using QA and explicit ip
address as the server name?
TheSQLGuru
President
Indicium Resources, Inc.
"Razvan Dragomir" <RazvanDragomir@.discussions.microsoft.com> wrote in
message news:FBA2A6A8-90DF-4316-BF0A-B82ECB0D2D9C@.microsoft.com...[vbcol=seagreen]
> Hi,
> I tried and it doesnt work (i`ve used a valid SQL Login)...there is
> another interesting thing..SQL is set to answer on port 1433 (default),
> but
> if I scan this port from the non-domain workstation it`s like it`s not
> opened, but it`s the same if i scan it from inside the domain where it
> also
> doesn`t respond but I can Connect though...
> --
> Razvan Dragomir,
> MCSA, Exchange & Windows System Administrator
>
> "TheSQLGuru" wrote:
>|||Hi,
Thx for the answers.....I don`t have any firewall between the
workstations and the server, I`m using TCP/IP and Named Pipes, and it`s
working to connect with IP address from QA, from inside the domain...I also
don`t have any firewall set for non domain clients...I`m just thinking if by
default Win2k3/SQL Server blocks connections from outside the domain...
--
Razvan Dragomir,
MCSA, Exchange & Windows System Administrator
"TheSQLGuru" wrote:
> Firewall issue seems most likely culprit. Or TCP/IP isn't enabled as a
> network protocol in sql server? Can you connect using QA and explicit ip
> address as the server name?
> --
> TheSQLGuru
> President
> Indicium Resources, Inc.
> "Razvan Dragomir" <RazvanDragomir@.discussions.microsoft.com> wrote in
> message news:FBA2A6A8-90DF-4316-BF0A-B82ECB0D2D9C@.microsoft.com...
>
>
Sunday, February 12, 2012
Client cant connect to server
We have installed a SQL 2000 server on a windows xp-pro machine and succesfully installed DotNetNuke. Now is the problem that there is no way we can manage to get a client connected. We have tried everything, changing tcp port, setting permissions, changing registry according to document 307197 in the microsoft database and nothing helps.
The only thing we can see is that in the serverlog we get a message stating that "SuperSocket Info : Bind failed on TCP port 1433". Can anyone help?
Regards Ulla & TomI assume you mean MSDE since SQL Server itself won't run on XP Pro. Have you looked at these yet:
http://support.microsoft.com/kb/293107/EN-US/
http://support.microsoft.com/kb/312935/
Have you checked to see if anything else is listening on port 1433? Have you tried using SQL on another port?
Jeff|||first thanx for yor reply - but no - I do mean Microsoft SQL Server 2000 Enterprise (evaluation version) - and it does run on an XP pro SP2 machine...
I am able to connect to the server locally by eg running my DotNetNuke portal and access it via http, but I cant access the portal from other computers in my home network.
I did have a look at the docs you mention. Regarding doc 293107 I have shot down all other software running on the server and it dosnt help. I checked the TCP ports with TCPVIEW and found nothing utilizing port 1433. I also changed the default TCP port for the server.
Regarding doc 312935: this does not refer to the same error message that I receive, however in lack of other good ideas I will try to get hold of the file from MS containing the fix fo that problem....
I hope you have other good ideas to fix my problem......|||
Are you 100% certain about that? Do you have a reference? Anything I have ever seen (e.g.Choosing an Edition of SQL Server 2000 andA Comparison of SQL Server 2000 with Access 2000) indicates that Windows XP can only run these versions of SQL Server 2000: Personal, Developer, and Desktop.
|||I downloaded the server from MS herehttp://www.microsoft.com/downloads/details.aspx?FamilyID=d20ba6e1-f44c-4781-a6bb-f60e02dc1335&DisplayLang=en , the documentation states that it can run on XP...
the welcome picture in setup states that this is a Windows 2000 server Enterprise edition....
I still havent found a fix for the problem, hope someone can help|||
Jeff|||I am able to open html and aspx pages from the cliens - the only thing I can't do is open DNN - so if the problem is a security policy issue then it should then be within the server (or DNN) -|||
The only thing we can see is that in the serverlog we get a message stating that "SuperSocket Info : Bind failed on TCP port 1433". Can anyone help?
Regards Ulla & TomI assume you mean MSDE since SQL Server itself won't run on XP Pro. Have you looked at these yet:
http://support.microsoft.com/kb/293107/EN-US/
http://support.microsoft.com/kb/312935/
Have you checked to see if anything else is listening on port 1433? Have you tried using SQL on another port?
Jeff|||first thanx for yor reply - but no - I do mean Microsoft SQL Server 2000 Enterprise (evaluation version) - and it does run on an XP pro SP2 machine...
I am able to connect to the server locally by eg running my DotNetNuke portal and access it via http, but I cant access the portal from other computers in my home network.
I did have a look at the docs you mention. Regarding doc 293107 I have shot down all other software running on the server and it dosnt help. I checked the TCP ports with TCPVIEW and found nothing utilizing port 1433. I also changed the default TCP port for the server.
Regarding doc 312935: this does not refer to the same error message that I receive, however in lack of other good ideas I will try to get hold of the file from MS containing the fix fo that problem....
I hope you have other good ideas to fix my problem......|||
ujep wrote:
I do mean Microsoft SQL Server 2000 Enterprise(evaluation version) - and it does run on an XP pro SP2machine...
Are you 100% certain about that? Do you have a reference? Anything I have ever seen (e.g.Choosing an Edition of SQL Server 2000 andA Comparison of SQL Server 2000 with Access 2000) indicates that Windows XP can only run these versions of SQL Server 2000: Personal, Developer, and Desktop.
|||I downloaded the server from MS herehttp://www.microsoft.com/downloads/details.aspx?FamilyID=d20ba6e1-f44c-4781-a6bb-f60e02dc1335&DisplayLang=en , the documentation states that it can run on XP...
the welcome picture in setup states that this is a Windows 2000 server Enterprise edition....
I still havent found a fix for the problem, hope someone can help|||
Most likely a firewall or security policy issue then. Though I wouldn't think you'd get the SQL port error, since DNN doesn't need to cross the network to reach a local SQL server and the clinet systems don't access SQL directly. Try a simple Hello World HTMP and ASPX page from the clients.I am able to connect to the server locally by eg running my DotNetNuke portal and access it via http, but I cant access the portal from other computers in my home network.
Jeff|||I am able to open html and aspx pages from the cliens - the only thing I can't do is open DNN - so if the problem is a security policy issue then it should then be within the server (or DNN) -|||
Yeah, but DNN works on the server itself, so it isn't a DNN or server problem either. When you opne DNN on the server, can you use the FQDN name justa s you would on the client, or are you just able to use "localhost"?
Jeff
Client can't be connected.
Hi,
I want to connect my win-XP client with win-server-2003 SQL Server.
I had done following task-
- I had installed SQL-2000 (Ent. Edition) on Win-Server 2003. And it is
successfully installed.
- In Win-S-2003 with the help of Active Directory I created domain and
created user on it.
- Client computer (Win-XP Prof.) configured with domain system. and I can
successfully login on that computer as a administrator.
- On client computer installed Sql-2000 (Ent. Edition) client tool.
- In Client Network Utility Configured my SQL Server
- In Enterprise Manager I done new registration with following configuration
-- Connect using = window authontication
-- Here I found following error : SQL Server does not exist or
access denied Connection Open(Connect())
Please help me to connect my client.
Hardik.
Hi
Can you connect to SQL Server, though EM, from the SQL Server console?
If not, is SQL Server running?
Can the client ping the SQL Server server?
Regards
Mike
"Hardik Shah" wrote:
> Hi,
> I want to connect my win-XP client with win-server-2003 SQL Server.
> I had done following task-
> - I had installed SQL-2000 (Ent. Edition) on Win-Server 2003. And it is
> successfully installed.
> - In Win-S-2003 with the help of Active Directory I created domain and
> created user on it.
> - Client computer (Win-XP Prof.) configured with domain system. and I can
> successfully login on that computer as a administrator.
> - On client computer installed Sql-2000 (Ent. Edition) client tool.
> - In Client Network Utility Configured my SQL Server
> - In Enterprise Manager I done new registration with following configuration
> -- Connect using = window authontication
> -- Here I found following error : SQL Server does not exist or
> access denied Connection Open(Connect())
> Please help me to connect my client.
>
> Hardik.
>
>
|||Hi,
Thanks for your reply.
I don't know how ping work . Please tell me how can client ping the SQL
Server
Hardik Shah
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:99ED019E-B7C0-473F-90D2-1AB2B7C059FC@.microsoft.com...[vbcol=seagreen]
> Hi
> Can you connect to SQL Server, though EM, from the SQL Server console?
> If not, is SQL Server running?
> Can the client ping the SQL Server server?
> Regards
> Mike
> "Hardik Shah" wrote:
can[vbcol=seagreen]
configuration[vbcol=seagreen]
|||Yes, I tried to ping my server it run successfully..
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:99ED019E-B7C0-473F-90D2-1AB2B7C059FC@.microsoft.com...[vbcol=seagreen]
> Hi
> Can you connect to SQL Server, though EM, from the SQL Server console?
> If not, is SQL Server running?
> Can the client ping the SQL Server server?
> Regards
> Mike
> "Hardik Shah" wrote:
can[vbcol=seagreen]
configuration[vbcol=seagreen]
I want to connect my win-XP client with win-server-2003 SQL Server.
I had done following task-
- I had installed SQL-2000 (Ent. Edition) on Win-Server 2003. And it is
successfully installed.
- In Win-S-2003 with the help of Active Directory I created domain and
created user on it.
- Client computer (Win-XP Prof.) configured with domain system. and I can
successfully login on that computer as a administrator.
- On client computer installed Sql-2000 (Ent. Edition) client tool.
- In Client Network Utility Configured my SQL Server
- In Enterprise Manager I done new registration with following configuration
-- Connect using = window authontication
-- Here I found following error : SQL Server does not exist or
access denied Connection Open(Connect())
Please help me to connect my client.
Hardik.
Hi
Can you connect to SQL Server, though EM, from the SQL Server console?
If not, is SQL Server running?
Can the client ping the SQL Server server?
Regards
Mike
"Hardik Shah" wrote:
> Hi,
> I want to connect my win-XP client with win-server-2003 SQL Server.
> I had done following task-
> - I had installed SQL-2000 (Ent. Edition) on Win-Server 2003. And it is
> successfully installed.
> - In Win-S-2003 with the help of Active Directory I created domain and
> created user on it.
> - Client computer (Win-XP Prof.) configured with domain system. and I can
> successfully login on that computer as a administrator.
> - On client computer installed Sql-2000 (Ent. Edition) client tool.
> - In Client Network Utility Configured my SQL Server
> - In Enterprise Manager I done new registration with following configuration
> -- Connect using = window authontication
> -- Here I found following error : SQL Server does not exist or
> access denied Connection Open(Connect())
> Please help me to connect my client.
>
> Hardik.
>
>
|||Hi,
Thanks for your reply.
I don't know how ping work . Please tell me how can client ping the SQL
Server
Hardik Shah
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:99ED019E-B7C0-473F-90D2-1AB2B7C059FC@.microsoft.com...[vbcol=seagreen]
> Hi
> Can you connect to SQL Server, though EM, from the SQL Server console?
> If not, is SQL Server running?
> Can the client ping the SQL Server server?
> Regards
> Mike
> "Hardik Shah" wrote:
can[vbcol=seagreen]
configuration[vbcol=seagreen]
|||Yes, I tried to ping my server it run successfully..
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:99ED019E-B7C0-473F-90D2-1AB2B7C059FC@.microsoft.com...[vbcol=seagreen]
> Hi
> Can you connect to SQL Server, though EM, from the SQL Server console?
> If not, is SQL Server running?
> Can the client ping the SQL Server server?
> Regards
> Mike
> "Hardik Shah" wrote:
can[vbcol=seagreen]
configuration[vbcol=seagreen]
Client cannot access SQL 2005 Express Server
I've installed SQL 2005 Express, enabled local and Remote connections but my client app cannot connect to the SQL server. I'm getting access denied or SQL does not exists. Any idea's on how to resolve this issue?
Perhaps these articles will help:
Configuration -Configure SQL Server 2005 to allow remote connections
http://support.microsoft.com/default.aspx?scid=kb;EN-US;914277
http://blogs.msdn.com/sqlexpress/archive/2005/05/05/415084.aspx
Configuration -Connect to SQL Express from "downlevel clients"
http://blogs.msdn.com/sqlexpress/archive/2004/07/23/192044.aspx
Configuration -Connect to SQL Express and ‘Stay Connected’
http://betav.com/blog/billva/2006/06/getting_and_staying_connected.html
Client can not connect to SQL Express - The Solution
Hi,
When I try to connect to SQL Express from another computer I get error 26.
The setup is as follows:
Server is Windows XP Pro, Firewall turned off.
Client is Windows XP Pro, Firewall turned off.
Both computers are on the same workgroup, no domain or other servers on the network.
The server is configured for network: protocols enabled, browser running.
The client has MS SQL Server Management Studio Express installed. When I try to connect the SSMSE finds the SQL Express on the server (using the Browse for more – Network server option), but the connection fails with error 26.
When I try to connect from MS Access 2003 I get the same error.
Thank for any help
Amihy
I found this link http://www.datamasker.com/SSE2005_NetworkCfg.htm maybe this will help you out.|||Thanks for the link, it helped me understand that all my SQL settings are OK.
So I started to think about the network and at last found that NetBios over TCP\IT was disabled. It did not bother me before since the local network works with NetBEUI protocol.
Once I enabled TCP\IP over NetBios in Local Area Connection-Properties-TCP\IP properties-General-advanced-wins, The client immediatly connected to the server. 
Client can not connect to SQL Express
Hi,
When I try to connect to SQL Express from another computer I get error 26.
The setup is as follows:
Server is Windows XP Pro, Firewall turned off.
Client is Windows XP Pro, Firewall turned off.
Both computers are on the same workgroup, no domain or other servers on the network.
The server is configured for network: protocols enabled, browser running.
The client has MS SQL Server Management Studio Express installed. When I try to connect the SSMSE finds the SQL Express on the server (using the Browse for more – Network server option), but the connection fails with error 26.
When I try to connect from MS Access 2003 I get the same error.
Thank for any help
Amihy
I found this link http://www.datamasker.com/SSE2005_NetworkCfg.htm maybe this will help you out.|||Thanks for the link, it helped me understand that all my SQL settings are OK.
So I started to think about the network and at last found that NetBios over TCP\IT was disabled. It did not bother me before since the local network works with NetBEUI protocol.
Once I enabled TCP\IP over NetBios in Local Area Connection-Properties-TCP\IP properties-General-advanced-wins, The client immediatly connected to the server.
Subscribe to:
Posts (Atom)