Connect to Client SQL

We happily connect to a couple of SQL databases on ISP servers using our
Enterprise Manager. We now have a client who wants us to connect to his
local SQL server in the same manner and I can't make it work.
I have 1433 open all the way through the various firewalls etc. Is there
any other port concerned that I might have to open up on his router as I try
and come in?
Many thanks
AndrewIf it's a default instance, listening on the default port, yes it should
work. Are you sure name resolution is working? In other words, you might
try to connect to his IP Address, i.e. "131.107.x.x,1433" as the
servername...
Richard Waymire, MCSE, MCDBA
This posting is provided "AS IS" with no warranties, and confers no rights.
"Andrew Prior" <andrew@.not-accede.com.au> wrote in message
news:u1QOcCFwDHA.1760@.TK2MSFTNGP10.phx.gbl...

quote:

---

> We happily connect to a couple of SQL databases on ISP servers using our
> Enterprise Manager. We now have a client who wants us to connect to his
> local SQL server in the same manner and I can't make it work.
> I have 1433 open all the way through the various firewalls etc. Is there
> any other port concerned that I might have to open up on his router as I

---

try

quote:

---

> and come in?
> Many thanks
> Andrew
>

---

|||Thankyou Richard. Yes, names are resolved. I have 1433 open all the way...
my port scanner can see it no worries.
I've never set up a server off my own network for an external user to log
into, so I am worried I am missing something here. His server is set up for
mixed mode logon. Is there anything else different that would apply to a
non local user?
Thankyou for your time
Andrew
I'm wondering if the firewall is stopping something else
"Richard Waymire [MSFT]" <rwaymi@.online.microsoft.com> wrote in message
news:Oa1NuxGwDHA.3744@.TK2MSFTNGP11.phx.gbl...

quote:

---

> If it's a default instance, listening on the default port, yes it should
> work. Are you sure name resolution is working? In other words, you might
> try to connect to his IP Address, i.e. "131.107.x.x,1433" as the
> servername...
> --
> Richard Waymire, MCSE, MCDBA
> This posting is provided "AS IS" with no warranties, and confers no

---

rights.

quote:

---

> "Andrew Prior" <andrew@.not-accede.com.au> wrote in message
> news:u1QOcCFwDHA.1760@.TK2MSFTNGP10.phx.gbl...
there[QUOTE]
> try
>

---

|||is the connection they're attempting standard or windows authentication?
Richard Waymire, MCSE, MCDBA
This posting is provided "AS IS" with no warranties, and confers no rights.
"Andrew Prior" <andrew@.not-accede.com.au> wrote in message
news:uk1pfGswDHA.3116@.tk2msftngp13.phx.gbl...

quote:

---

> Thankyou Richard. Yes, names are resolved. I have 1433 open all the

---

way...

quote:

---

> my port scanner can see it no worries.
> I've never set up a server off my own network for an external user to log
> into, so I am worried I am missing something here. His server is set up

---

for

quote:

---

> mixed mode logon. Is there anything else different that would apply to a
> non local user?
> Thankyou for your time
> Andrew
> I'm wondering if the firewall is stopping something else
> "Richard Waymire [MSFT]" <rwaymi@.online.microsoft.com> wrote in message
> news:Oa1NuxGwDHA.3744@.TK2MSFTNGP11.phx.gbl...
might[QUOTE]
> rights.
our[QUOTE]
his[QUOTE]
> there
I[QUOTE]
>

---

Connect to a 2nd instance of SQL server while UDP 1434 is blocked

I have two instances of SQL 2000 on one of our servers. I can connect to the
first instance that has the machine name and port 1434 from anywhere I want.
But when I try to connect to the second instance on the same machine with
then name of machinename\G3 from a server on a second network where UDP 1434
port is blocked by the firewall, the connection fail and the second instance
is not available. I followed this article on Microsoft knowledge base
http://support.microsoft.com/kb/265808/ where I created an alias for the G3
server on the client machine using the IP address and the assigned port
number, but that didnâ't help and I still could not connect to the server. I
basically followed those steps:
2. Configure the server alias on the client computer.
SQL Server 2000a. Start the Client Network Utility.
b. On the General tab, verify that TCP/IP appears in the list under Enabled
protocols by order.
c. Click the Alias tab, and then click Add.
d. Under Network libraries, select TCP/IP.
e. In the Server name text box, type the IP address of the server that is
running SQL Server 2005.
Note The IP address that you type here is the one that is configured to use
the TCP/IP port number.
f. Click to clear the Dynamically determine port check box, and then type
the port number of the instance of SQL Server 2005 in the Port number text
box.
g. Type a name in the Server alias text box, and then click OK.
I asked the IT department to unblock the UDP 1434 temporarily to see if I
can connect to the G3 server, and I was able to connect with no problem.
Unfortunately, they are required to block UDP 1434 so I have to deal with
that.
Does anybody have any idea that could help? Please let me know.
ThanksHi Danny
A named instance will use a dynamic port by default and UDP 1434 is used to
transmit the name of the instance name back to the client. You will need to
make the port fixed on the server and the corresponding port configured on
the client.
Check out http://support.microsoft.com/kb/287932.
John
"Danny Mansour" wrote:
> I have two instances of SQL 2000 on one of our servers. I can connect to the
> first instance that has the machine name and port 1434 from anywhere I want.
> But when I try to connect to the second instance on the same machine with
> then name of machinename\G3 from a server on a second network where UDP 1434
> port is blocked by the firewall, the connection fail and the second instance
> is not available. I followed this article on Microsoft knowledge base
> http://support.microsoft.com/kb/265808/ where I created an alias for the G3
> server on the client machine using the IP address and the assigned port
> number, but that didnâ't help and I still could not connect to the server. I
> basically followed those steps:
> 2. Configure the server alias on the client computer.
> SQL Server 2000a. Start the Client Network Utility.
> b. On the General tab, verify that TCP/IP appears in the list under Enabled
> protocols by order.
> c. Click the Alias tab, and then click Add.
> d. Under Network libraries, select TCP/IP.
> e. In the Server name text box, type the IP address of the server that is
> running SQL Server 2005.
> Note The IP address that you type here is the one that is configured to use
> the TCP/IP port number.
> f. Click to clear the Dynamically determine port check box, and then type
> the port number of the instance of SQL Server 2005 in the Port number text
> box.
> g. Type a name in the Server alias text box, and then click OK.
>
> I asked the IT department to unblock the UDP 1434 temporarily to see if I
> can connect to the G3 server, and I was able to connect with no problem.
> Unfortunately, they are required to block UDP 1434 so I have to deal with
> that.
> Does anybody have any idea that could help? Please let me know.
> Thanks
>|||One way to avoid the dependency on UDP 1434 is to specify the port number
explicitly on the connection string. So assume that the server name is
ServerA, its IP address is A.B.C.D, and the instance listens on TCP port
1234, you connect to the instance as follows:
ServerA,1234
or
A.B.C.D,1234
When you connect to an instance using the ServerName\InstanceName
convention, the client needs to retrieve the port number first, and it talks
to UDP 1434 to get the port number.
Linchi
"Danny Mansour" wrote:
> I have two instances of SQL 2000 on one of our servers. I can connect to the
> first instance that has the machine name and port 1434 from anywhere I want.
> But when I try to connect to the second instance on the same machine with
> then name of machinename\G3 from a server on a second network where UDP 1434
> port is blocked by the firewall, the connection fail and the second instance
> is not available. I followed this article on Microsoft knowledge base
> http://support.microsoft.com/kb/265808/ where I created an alias for the G3
> server on the client machine using the IP address and the assigned port
> number, but that didnâ't help and I still could not connect to the server. I
> basically followed those steps:
> 2. Configure the server alias on the client computer.
> SQL Server 2000a. Start the Client Network Utility.
> b. On the General tab, verify that TCP/IP appears in the list under Enabled
> protocols by order.
> c. Click the Alias tab, and then click Add.
> d. Under Network libraries, select TCP/IP.
> e. In the Server name text box, type the IP address of the server that is
> running SQL Server 2005.
> Note The IP address that you type here is the one that is configured to use
> the TCP/IP port number.
> f. Click to clear the Dynamically determine port check box, and then type
> the port number of the instance of SQL Server 2005 in the Port number text
> box.
> g. Type a name in the Server alias text box, and then click OK.
>
> I asked the IT department to unblock the UDP 1434 temporarily to see if I
> can connect to the G3 server, and I was able to connect with no problem.
> Unfortunately, they are required to block UDP 1434 so I have to deal with
> that.
> Does anybody have any idea that could help? Please let me know.
> Thanks
>|||Thanks a bunch for the reply.
I followed the article you sent me and configured a static port and I
configured the client machine to point to the port. Somehow this still
didn't work for me. The article mentions to set a static Port before
configuring the firewall. I wonder if I need to open the new static port on
the firewall to make it work?
Please let me know what you think.
Thanks,
Danny
"John Bell" wrote:
> Hi Danny
> A named instance will use a dynamic port by default and UDP 1434 is used to
> transmit the name of the instance name back to the client. You will need to
> make the port fixed on the server and the corresponding port configured on
> the client.
> Check out http://support.microsoft.com/kb/287932.
> John
>
> "Danny Mansour" wrote:
> > I have two instances of SQL 2000 on one of our servers. I can connect to the
> > first instance that has the machine name and port 1434 from anywhere I want.
> > But when I try to connect to the second instance on the same machine with
> > then name of machinename\G3 from a server on a second network where UDP 1434
> > port is blocked by the firewall, the connection fail and the second instance
> > is not available. I followed this article on Microsoft knowledge base
> > http://support.microsoft.com/kb/265808/ where I created an alias for the G3
> > server on the client machine using the IP address and the assigned port
> > number, but that didnâ't help and I still could not connect to the server. I
> > basically followed those steps:
> >
> > 2. Configure the server alias on the client computer.
> >
> > SQL Server 2000a. Start the Client Network Utility.
> > b. On the General tab, verify that TCP/IP appears in the list under Enabled
> > protocols by order.
> > c. Click the Alias tab, and then click Add.
> > d. Under Network libraries, select TCP/IP.
> > e. In the Server name text box, type the IP address of the server that is
> > running SQL Server 2005.
> >
> > Note The IP address that you type here is the one that is configured to use
> > the TCP/IP port number.
> > f. Click to clear the Dynamically determine port check box, and then type
> > the port number of the instance of SQL Server 2005 in the Port number text
> > box.
> > g. Type a name in the Server alias text box, and then click OK.
> >
> >
> > I asked the IT department to unblock the UDP 1434 temporarily to see if I
> > can connect to the G3 server, and I was able to connect with no problem.
> > Unfortunately, they are required to block UDP 1434 so I have to deal with
> > that.
> >
> > Does anybody have any idea that could help? Please let me know.
> >
> > Thanks
> >|||thank you for your reply. The intersting thing is that I have been trying to
connect to the second instance through the Enterprise Manager using an alias
name through the Client Network Utility where I specified the IP address and
the static port number, but I was unable to make a connection. On the other
hand, trying to connect using OSQL by doing "OSQL /E servername,port as you
suggeted works fine and I'm able to query the server. I wonder what the
difference is in the way the Enterprise Manger tries to make the connection.
I'm trying to establish replication between servers thus I need the
Enterprise Manager to be able to connect.
Please let me know what you think.
Thanks a million.
Danny
"Linchi Shea" wrote:
> One way to avoid the dependency on UDP 1434 is to specify the port number
> explicitly on the connection string. So assume that the server name is
> ServerA, its IP address is A.B.C.D, and the instance listens on TCP port
> 1234, you connect to the instance as follows:
> ServerA,1234
> or
> A.B.C.D,1234
> When you connect to an instance using the ServerName\InstanceName
> convention, the client needs to retrieve the port number first, and it talks
> to UDP 1434 to get the port number.
> Linchi
> "Danny Mansour" wrote:
> > I have two instances of SQL 2000 on one of our servers. I can connect to the
> > first instance that has the machine name and port 1434 from anywhere I want.
> > But when I try to connect to the second instance on the same machine with
> > then name of machinename\G3 from a server on a second network where UDP 1434
> > port is blocked by the firewall, the connection fail and the second instance
> > is not available. I followed this article on Microsoft knowledge base
> > http://support.microsoft.com/kb/265808/ where I created an alias for the G3
> > server on the client machine using the IP address and the assigned port
> > number, but that didnâ't help and I still could not connect to the server. I
> > basically followed those steps:
> >
> > 2. Configure the server alias on the client computer.
> >
> > SQL Server 2000a. Start the Client Network Utility.
> > b. On the General tab, verify that TCP/IP appears in the list under Enabled
> > protocols by order.
> > c. Click the Alias tab, and then click Add.
> > d. Under Network libraries, select TCP/IP.
> > e. In the Server name text box, type the IP address of the server that is
> > running SQL Server 2005.
> >
> > Note The IP address that you type here is the one that is configured to use
> > the TCP/IP port number.
> > f. Click to clear the Dynamically determine port check box, and then type
> > the port number of the instance of SQL Server 2005 in the Port number text
> > box.
> > g. Type a name in the Server alias text box, and then click OK.
> >
> >
> > I asked the IT department to unblock the UDP 1434 temporarily to see if I
> > can connect to the G3 server, and I was able to connect with no problem.
> > Unfortunately, they are required to block UDP 1434 so I have to deal with
> > that.
> >
> > Does anybody have any idea that could help? Please let me know.
> >
> > Thanks
> >|||I wonder if I need to open the new static port on
> the firewall to make it work?
Yes, whatever port SQL Server is listening on must be open in order for
clients to connect over the network.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Danny Mansour" <DannyMansour@.discussions.microsoft.com> wrote in message
news:6F17AAA9-D82F-41CB-B1DA-2AD431FC86AA@.microsoft.com...
> Thanks a bunch for the reply.
> I followed the article you sent me and configured a static port and I
> configured the client machine to point to the port. Somehow this still
> didn't work for me. The article mentions to set a static Port before
> configuring the firewall. I wonder if I need to open the new static port
> on
> the firewall to make it work?
> Please let me know what you think.
> Thanks,
> Danny
> "John Bell" wrote:
>> Hi Danny
>> A named instance will use a dynamic port by default and UDP 1434 is used
>> to
>> transmit the name of the instance name back to the client. You will need
>> to
>> make the port fixed on the server and the corresponding port configured
>> on
>> the client.
>> Check out http://support.microsoft.com/kb/287932.
>> John
>>
>> "Danny Mansour" wrote:
>> > I have two instances of SQL 2000 on one of our servers. I can connect
>> > to the
>> > first instance that has the machine name and port 1434 from anywhere I
>> > want.
>> > But when I try to connect to the second instance on the same machine
>> > with
>> > then name of machinename\G3 from a server on a second network where UDP
>> > 1434
>> > port is blocked by the firewall, the connection fail and the second
>> > instance
>> > is not available. I followed this article on Microsoft knowledge base
>> > http://support.microsoft.com/kb/265808/ where I created an alias for
>> > the G3
>> > server on the client machine using the IP address and the assigned port
>> > number, but that didn't help and I still could not connect to the
>> > server. I
>> > basically followed those steps:
>> >
>> > 2. Configure the server alias on the client computer.
>> >
>> > SQL Server 2000a. Start the Client Network Utility.
>> > b. On the General tab, verify that TCP/IP appears in the list under
>> > Enabled
>> > protocols by order.
>> > c. Click the Alias tab, and then click Add.
>> > d. Under Network libraries, select TCP/IP.
>> > e. In the Server name text box, type the IP address of the server that
>> > is
>> > running SQL Server 2005.
>> >
>> > Note The IP address that you type here is the one that is configured to
>> > use
>> > the TCP/IP port number.
>> > f. Click to clear the Dynamically determine port check box, and then
>> > type
>> > the port number of the instance of SQL Server 2005 in the Port number
>> > text
>> > box.
>> > g. Type a name in the Server alias text box, and then click OK.
>> >
>> >
>> > I asked the IT department to unblock the UDP 1434 temporarily to see if
>> > I
>> > can connect to the G3 server, and I was able to connect with no
>> > problem.
>> > Unfortunately, they are required to block UDP 1434 so I have to deal
>> > with
>> > that.
>> >
>> > Does anybody have any idea that could help? Please let me know.
>> >
>> > Thanks
>> >

Connect to a 2nd instance of SQL server while UDP 1434 is blocked

I have two instances of SQL 2000 on one of our servers. I can connect to the
first instance that has the machine name and port 1434 from anywhere I want.
But when I try to connect to the second instance on the same machine with
then name of machinename\G3 from a server on a second network where UDP 1434
port is blocked by the firewall, the connection fail and the second instance
is not available. I followed this article on Microsoft knowledge base
http://support.microsoft.com/kb/265808/ where I created an alias for the G3
server on the client machine using the IP address and the assigned port
number, but that didn’t help and I still could not connect to the server.
I
basically followed those steps:
2. Configure the server alias on the client computer.
SQL Server 2000a. Start the Client Network Utility.
b. On the General tab, verify that TCP/IP appears in the list under Enabled
protocols by order.
c. Click the Alias tab, and then click Add.
d. Under Network libraries, select TCP/IP.
e. In the Server name text box, type the IP address of the server that is
running SQL Server 2005.
Note The IP address that you type here is the one that is configured to use
the TCP/IP port number.
f. Click to clear the Dynamically determine port check box, and then type
the port number of the instance of SQL Server 2005 in the Port number text
box.
g. Type a name in the Server alias text box, and then click OK.
I asked the IT department to unblock the UDP 1434 temporarily to see if I
can connect to the G3 server, and I was able to connect with no problem.
Unfortunately, they are required to block UDP 1434 so I have to deal with
that.
Does anybody have any idea that could help? Please let me know.
ThanksHi Danny
A named instance will use a dynamic port by default and UDP 1434 is used to
transmit the name of the instance name back to the client. You will need to
make the port fixed on the server and the corresponding port configured on
the client.
Check out http://support.microsoft.com/kb/287932.
John
"Danny Mansour" wrote:

> I have two instances of SQL 2000 on one of our servers. I can connect to t
he
> first instance that has the machine name and port 1434 from anywhere I wan
t.
> But when I try to connect to the second instance on the same machine with
> then name of machinename\G3 from a server on a second network where UDP 14
34
> port is blocked by the firewall, the connection fail and the second instan
ce
> is not available. I followed this article on Microsoft knowledge base
> http://support.microsoft.com/kb/265808/ where I created an alias for the G
3
> server on the client machine using the IP address and the assigned port
> number, but that didn’t help and I still could not connect to the server
. I
> basically followed those steps:
> 2. Configure the server alias on the client computer.
> SQL Server 2000a. Start the Client Network Utility.
> b. On the General tab, verify that TCP/IP appears in the list under Enabl
ed
> protocols by order.
> c. Click the Alias tab, and then click Add.
> d. Under Network libraries, select TCP/IP.
> e. In the Server name text box, type the IP address of the server that is
> running SQL Server 2005.
> Note The IP address that you type here is the one that is configured to us
e
> the TCP/IP port number.
> f. Click to clear the Dynamically determine port check box, and then type
> the port number of the instance of SQL Server 2005 in the Port number text
> box.
> g. Type a name in the Server alias text box, and then click OK.
>
> I asked the IT department to unblock the UDP 1434 temporarily to see if I
> can connect to the G3 server, and I was able to connect with no problem.
> Unfortunately, they are required to block UDP 1434 so I have to deal with
> that.
> Does anybody have any idea that could help? Please let me know.
> Thanks
>|||One way to avoid the dependency on UDP 1434 is to specify the port number
explicitly on the connection string. So assume that the server name is
ServerA, its IP address is A.B.C.D, and the instance listens on TCP port
1234, you connect to the instance as follows:
ServerA,1234
or
A.B.C.D,1234
When you connect to an instance using the ServerName\InstanceName
convention, the client needs to retrieve the port number first, and it talks
to UDP 1434 to get the port number.
Linchi
"Danny Mansour" wrote:

> I have two instances of SQL 2000 on one of our servers. I can connect to t
he
> first instance that has the machine name and port 1434 from anywhere I wan
t.
> But when I try to connect to the second instance on the same machine with
> then name of machinename\G3 from a server on a second network where UDP 14
34
> port is blocked by the firewall, the connection fail and the second instan
ce
> is not available. I followed this article on Microsoft knowledge base
> http://support.microsoft.com/kb/265808/ where I created an alias for the G
3
> server on the client machine using the IP address and the assigned port
> number, but that didn’t help and I still could not connect to the server
. I
> basically followed those steps:
> 2. Configure the server alias on the client computer.
> SQL Server 2000a. Start the Client Network Utility.
> b. On the General tab, verify that TCP/IP appears in the list under Enabl
ed
> protocols by order.
> c. Click the Alias tab, and then click Add.
> d. Under Network libraries, select TCP/IP.
> e. In the Server name text box, type the IP address of the server that is
> running SQL Server 2005.
> Note The IP address that you type here is the one that is configured to us
e
> the TCP/IP port number.
> f. Click to clear the Dynamically determine port check box, and then type
> the port number of the instance of SQL Server 2005 in the Port number text
> box.
> g. Type a name in the Server alias text box, and then click OK.
>
> I asked the IT department to unblock the UDP 1434 temporarily to see if I
> can connect to the G3 server, and I was able to connect with no problem.
> Unfortunately, they are required to block UDP 1434 so I have to deal with
> that.
> Does anybody have any idea that could help? Please let me know.
> Thanks
>

Connect SQL Server- Network

Hi,

I have 2 SQL 2K Servers set up on my home network. Both PC's are running Windows XP and as far as I can tell are configured identically, however I can connect to the Server A from PC B but not Server B from PC A (both work fine when I am on the same machine I try to connect to). Any ideas anyone, the error message I am getting is attached.Could one server be configured to listen on named pipes, but not the other? Could one client be configured to use Named Pipes as its default client, while the other was configured to use TCP/IP? My guess is that one of the machines has a problem with either the client or the server network configuration.

-PatP|||If I understand you correctly you are able to connect from A to B but not from B to A, both A and B have an installation of SQLServer up and running. From the errormessage attached and the fact that you are able to setup a connection from A to B, I'd look for network issues on B. Are you able to ping A from B? Is A listed in the network neighbourhood on B? On A, is the SQL Agent running?
EDIT: sniped on a friday!|||Ok solved it, A had not had file and print sharing set up, didn't even think to check this as I could see it on the network, so assumed it was setup correctly!

Connect into SSAS from SSMS with diferent user

Hi,

I'm a consultant and I need to connect to differents SSAS Servers using Management Studio.

In each customer I have one different user. I use this user to connect into their network and access servers, drives and SQL Server (using SQL autenticate) from my laptop (without connect into domain from my user).

In some customers, when I've a drive mapped to server I can access SSAS, but I don't know why this happen only in some customers and how do this again.

I'd like if someone can help me.

Thanks.

You can specify User Name and Password connection string properties when connecting to AS, (but it is possible that Management Studio doesn't have UI for them). Mapping drive works sometimes because of how NETBIOS interacts with SSPI, but in general it is not reliable way of piggibacking of establishing credentials.|||

The runas command should do what you want:

http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=1365877&SiteID=17

connect allowed from all except asp ?

I have servers working with that combination
a few serwers IIS 5.0 with asp pages
and one with SQL 2000 sp3
All of them running on Windows 2000 Adv Server sp4
And What I get:
Using Enterprise Manager, query analizer, VB application I can
connect to database with mixed creditenitals or with nt auth
(EntManager and Query analizer).
But when I'm trying from asp - it is not working at all
I have tried these connections strings
CF=" DSN=XXSQL;SERVER=XX;DATABASE=XXX;Network
=DBMSSOCN;Address=10.10.10.10,14
33;UID=XXuser;PWD=xxpass;"
CF="Provider=SQLOLEDB.1;Persist Security Info=False;User
ID=xxuser;Initial Catalog=XXX;Data Source=XX"
CF="Provider=SQLOLEDB;Data Source=XX;Initial Catalog=XXX;Integrated
Security=SSPI"
CF= " dsn=xxsql;uid=xxuser;pwd=xxpass;database
=xxx;app=ASP;Connect
Timeout=60;Network Library=dbmssocn"
And nothing of them works.
I always get
"SQL Server does not exist or access denied"
Any idea what's wrong with connection?
Maybye with sql server something is not configured 'Did you add the IUSR_machine to the list of users that can log int to the
database in question?
Francisco
"ML" <maluleszek@.poczta.onet.pl> wrote in message
news:48fba10e.0407120244.102a5311@.posting.google.com...
> I have servers working with that combination
> a few serwers IIS 5.0 with asp pages
> and one with SQL 2000 sp3
> All of them running on Windows 2000 Adv Server sp4
> And What I get:
> Using Enterprise Manager, query analizer, VB application I can
> connect to database with mixed creditenitals or with nt auth
> (EntManager and Query analizer).
> But when I'm trying from asp - it is not working at all
> I have tried these connections strings
>
CF=" DSN=XXSQL;SERVER=XX;DATABASE=XXX;Network
=DBMSSOCN;Address=10.10.10.10,14
33;UID=XXuser;PWD=xxpass;"
> CF="Provider=SQLOLEDB.1;Persist Security Info=False;User
> ID=xxuser;Initial Catalog=XXX;Data Source=XX"
> CF="Provider=SQLOLEDB;Data Source=XX;Initial Catalog=XXX;Integrated
> Security=SSPI"
> CF= " dsn=xxsql;uid=xxuser;pwd=xxpass;database
=xxx;app=ASP;Connect
> Timeout=60;Network Library=dbmssocn"
> And nothing of them works.
> I always get
> "SQL Server does not exist or access denied"
> Any idea what's wrong with connection?
> Maybye with sql server something is not configured '|||Yes, this user was added, because this connection was working before.
And now I remove it and added it again.
But I found in logs that during weekend, when I lost ability to connect,
the power was goes down for a few second. (I have UPS)
It is possible to lost any login information because of that ?
(ups software or something ?)
"Francisco" <nomail@.baseball.net> wrote in message news:<OgdcL5QaEHA.596@.TK2MSFTNGP11.phx.gb
l>...[vbcol=seagreen]
> Did you add the IUSR_machine to the list of users that can log int to the
> database in question?
> Francisco
>
> "ML" <maluleszek@.poczta.onet.pl> wrote in message
> news:48fba10e.0407120244.102a5311@.posting.google.com...
> CF=" DSN=XXSQL;SERVER=XX;DATABASE=XXX;Network
=DBMSSOCN;Address=10.10.10.10,
14
> 33;UID=XXuser;PWD=xxpass;"

connect allowed from all except asp ?

I have servers working with that combination
a few serwers IIS 5.0 with asp pages
and one with SQL 2000 sp3
All of them running on Windows 2000 Adv Server sp4
And What I get:
Using Enterprise Manager, query analizer, VB application I can
connect to database with mixed creditenitals or with nt auth
(EntManager and Query analizer).
But when I'm trying from asp - it is not working at all
I have tried these connections strings
CF="DSN=XXSQL;SERVER=XX;DATABASE=XXX;Network=DBMSS OCN;Address=10.10.10.10,1433;UID=XXuser;PWD=xxpass ;"
CF="Provider=SQLOLEDB.1;Persist Security Info=False;User
ID=xxuser;Initial Catalog=XXX;Data Source=XX"
CF="Provider=SQLOLEDB;Data Source=XX;Initial Catalog=XXX;Integrated
Security=SSPI"
CF= "dsn=xxsql;uid=xxuser;pwd=xxpass;database=xxx;app= ASP;Connect
Timeout=60;Network Library=dbmssocn"
And nothing of them works.
I always get
"SQL Server does not exist or access denied"
Any idea what's wrong with connection?
Maybye with sql server something is not configured ?
Did you add the IUSR_machine to the list of users that can log int to the
database in question?
Francisco
"ML" <maluleszek@.poczta.onet.pl> wrote in message
news:48fba10e.0407120244.102a5311@.posting.google.c om...
> I have servers working with that combination
> a few serwers IIS 5.0 with asp pages
> and one with SQL 2000 sp3
> All of them running on Windows 2000 Adv Server sp4
> And What I get:
> Using Enterprise Manager, query analizer, VB application I can
> connect to database with mixed creditenitals or with nt auth
> (EntManager and Query analizer).
> But when I'm trying from asp - it is not working at all
> I have tried these connections strings
>
CF="DSN=XXSQL;SERVER=XX;DATABASE=XXX;Network=DBMSS OCN;Address=10.10.10.10,14
33;UID=XXuser;PWD=xxpass;"
> CF="Provider=SQLOLEDB.1;Persist Security Info=False;User
> ID=xxuser;Initial Catalog=XXX;Data Source=XX"
> CF="Provider=SQLOLEDB;Data Source=XX;Initial Catalog=XXX;Integrated
> Security=SSPI"
> CF= "dsn=xxsql;uid=xxuser;pwd=xxpass;database=xxx;app= ASP;Connect
> Timeout=60;Network Library=dbmssocn"
> And nothing of them works.
> I always get
> "SQL Server does not exist or access denied"
> Any idea what's wrong with connection?
> Maybye with sql server something is not configured ?
|||Yes, this user was added, because this connection was working before.
And now I remove it and added it again.
But I found in logs that during weekend, when I lost ability to connect,
the power was goes down for a few second. (I have UPS)
It is possible to lost any login information because of that ?
(ups software or something ?)
"Francisco" <nomail@.baseball.net> wrote in message news:<OgdcL5QaEHA.596@.TK2MSFTNGP11.phx.gbl>...[vbcol=seagreen]
> Did you add the IUSR_machine to the list of users that can log int to the
> database in question?
> Francisco
>
> "ML" <maluleszek@.poczta.onet.pl> wrote in message
> news:48fba10e.0407120244.102a5311@.posting.google.c om...
> CF="DSN=XXSQL;SERVER=XX;DATABASE=XXX;Network=DBMSS OCN;Address=10.10.10.10,14
> 33;UID=XXuser;PWD=xxpass;"

Connect 2 databases on 2 servers ??

Hi,

If you have 2 databases with the exact same table columns, and in the first database in a table column the indentidy seed starts at 1 and finishes at 32,000 can you attatch a second database so that the indentity starts at 32,001and carries on.

What happens if you create a site and run out of disk space and need to attach another database which is located on another server?

I am really confused about this.Hope someone can give some links to some articles about this as I can't find any information about it.

How can this be done?

Thanks

robinwilliams:

If you have 2 databases with the exact same table columns, and in the first database in a table column the indentidy seed starts at 1 and finishes at 32,000 can you attatch a second database so that the indentity starts at 32,001and carries on.

Yes, you can!
Just use DTS (in SQL Server 2000) or SSIS (in SQL Server 2005) and while trasfering the data select the "Append Data" option, but make sure the data type of the identity column in the source table is able to deal with new records (have enough size) [e.g. make it INT].

robinwilliams:

What happens if you create a site and run out of disk space and need to attach another database which is located on another server?

What do you mean by another server? Is it physically another server (e.g. using another disk)? If yes, the database files (.mdf, .ndf, .ldf) will be in that server using its disks which are diffrent than the ones have no enough space.
Once you are runing out of space, you will receive error indicating that (e.g. in Enterpise Manager or Management Studio), So always have more space than you need by 2-4GB at least.

Good luck.

Confusion about dialog security steps.

Hi There

I have done the following.

2 Servers across the net work Server A and Server B.

I have created private keys at each and copied to public keys across.

I create an endpoint at each with validation by the certificates. I then create appropriate users and logins at each and import the public certificates with authorization to the users who have send permission on the endpoints.

That is transport security sorted and it works.

Now from what i have learnt from examples, to setup dialog security i do the following.

create a private key in each DB :

create certificate Store001DialogPri

with subject = 'Store001DialogPri',

start_date = '07/20/2006'

active for begin_dialog = on;

go

I then copy the public key to each server, create a user only in each DB and import the public keys with authorization on the user. And grant send to the appropriate servcies to the user.

I then create appropriate remote service bindings with this user.

Now this works for me. Everythign seems A OK.

However i am going thorugh the Service Broker "bible", and there are a ton of steps i am not doing but my setup works ?

Steps i am not doing for example is when i create the private keys in the DB i should authorize them to a user i create who is then gratnted CONTROL permission on the SERVICES.

Now i do not do this but everything seems to be working. I thought i finally understood dialogs security but now i am totally confused ?

Is what i am doing correct ? If so why are these all these additinal steps mentioned ? WHat am i missing ?

Thanx

The AUTHORIZATION and CONTROL steps in the samples are needed if you are performing these steps for somebody else. You test probably ended up with all the services being owned by [dbo], (you are sysadmin on the test machine, aren't you?), and the certificates with private keys also being owned by [dbo], so it just worked. But in real life, you might have to do this setup steps for a service owned by a different database user, so in that case is important to associate the private key with the service owner.

HTH,
~ Remus

|||

Hi Remus

Yes everything should be owned by dbo, however i do not see any otehr users coming into the SB application, so therefore i shouldnot have to do these steps?

Thanx for the feedback

Confirm new password? Please help.

Hi,
All of sudden, all my SQL 2K servers start to ask "Confirm
new password" when I assign a database access permission
to a local user. Even though I type in the correct
password, it still say "The confirmation password is not
correct". Right now I simply cannot assign any database
access to the local users. But the domain trusted users
don't have this problem. Does anyone know what the problem
is?
Thank you in advance for your help.
David...I'm trying to remember back - I had this occur ages ago. Have you either
service packed the server or switched client workstation? I "think" it was
fixed by service packing my client machine (to get it inline with the server
).
Alicia
Http://www.sqlporn.co.uk|||I applied SQL 2K security patch about a month ago, and
brought the builder version to 8.00.818. I just found the
article that addresses this problem.
http://support.microsoft.com/default.aspx?kbid=826161
Thanks for your information.
David.
>--Original Message--
>...I'm trying to remember back - I had this occur ages
ago. Have you either service packed the server or switched
client workstation? I "think" it was fixed by service
packing my client machine (to get it inline with the
server).
>Alicia
>Http://www.sqlporn.co.uk
>.
>|||This was a bug with the security rollup for SQL. You need to install build
819.
826161 FIX: You Are Prompted for Password Confirmation After You Change a
http://support.microsoft.com/?id=826161
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.|||Hi Kevin,
I downloaded and applied the hotfix. The problem is gone.
But when I check the SQL server product version that is
still showing 8.00.818(SP3). Is that right? I thought it
should show the version # 8.00.819(SP3). Is there
something that I didn't do right?
Thank you for your help.
David.
>--Original Message--
>This was a bug with the security rollup for SQL. You
need to install build
>819.
>826161 FIX: You Are Prompted for Password Confirmation
After You Change a
>http://support.microsoft.com/?id=826161
>Thanks,
>Kevin McDonnell
>Microsoft Corporation
>This posting is provided AS IS with no warranties, and
confers no rights.
>
>.
>|||to dive in, the hotfix just changes a DLL (can't remember which) and doesn't
affect sqlservr.exe so therefore you still see 818. This is expected
behaviour
regards,
Andy.
"David W." <anonymous@.discussions.microsoft.com> wrote in message
news:17d6101c44992$2faee360$a501280a@.phx
.gbl...[vbcol=seagreen]
> Hi Kevin,
> I downloaded and applied the hotfix. The problem is gone.
> But when I check the SQL server product version that is
> still showing 8.00.818(SP3). Is that right? I thought it
> should show the version # 8.00.819(SP3). Is there
> something that I didn't do right?
> Thank you for your help.
> David.
> need to install build
> After You Change a
> confers no rights.|||Hi David,
Sorry. That is correct. SQL Server .exe is still 818.
01-Jun-2003 01:02 2000.80.818.0 7,544,916 bytes Sqlservr.exe
This is the only component stamped 819.
01-Jun-2003 01:01 2000.80.819.0 492,096 bytes Semobj.dll
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.

Configuring SQLAgent for sending email

Hi All,

I need some help in configure our SQL 2K & 2K5 servers to send notification on job failers. Have created operators on SQL 2k but when i try to do a test mail it fails saying mai session is not running. I go to properties of the Sql agent to turn on mail session but it is grayed out. Can someone please direct me to the steps I need to take when setting up sql server with email capability. Do I have to install office (outlook on the sql server box) in order for emailing to work?

Thanks in advance for your help.

Nats

On SQL 2000 servers, you will need a MAPI client installed (e.g., Outlook).

However, I recommend checking out the usage of xp_smtp_sendmail -an alternative to installing Outlook and all of its issues.

Mail –Sending
SQL 2000 - http://www.sqldev.net/xp/xpsmtp.htm
http://www.aspfaq.com/show.asp?id=2403

Configuring SQL to use AWE

I have configured a SQL200 instance to use 5gb of my server's memory.
At startup the log indicates that AWE is being used, and I see
that the memory is being grabbed when the instance starts.
But in the log indicates that the Working Set Size is set to 1 GB.
Does this mean anything when using AWE..
Am I getting full use of AWE on my instance. How can I tell....
Thanks
Paul
Check the Buffer Manager counter in Perfmon. There are a set of
events/classes related to AWE which you can check.
Anith

configuring replication sql 2005 express edition

Hello all,

We have 2 sites . each one has sql 2005 express edition .

is it possible to configure replication between those 2 sql servers for failover purposes ?

ThanksSort of. You should use log shipping for something like this. Note that SQL Server Express does not support replication publishing, ie you can't use merge replication to publish database on a SQL Express installation. You can make them subscribers however.

Nor can you use the log shipping wizard which ships in SQL Server Standard and above.

You will have to roll your own log shipping topology and you will have to do manual failover and redirect your clients to the failover server.

Configuring Peer-to_Peer Merge Replication

We have a situation almost exactly like that in the MS documentation
vis a vis peer-to-peer replication. We have three servers and three
user groups, one each in Chicago, New York, and Bermuda. Because of our
business practices, we are fairly confident that only one group will be
updating a given record at any one time but the users will be updating
their own local database servers and those updates must appear on all
three servers. Reading through the documentation, MS seems to recommend
peer-to-peer merge replication. Unfortunately, the documenation then
goes off and gives an example only of transaction replication without
updating subscriptions. Well, OK I sez, I'll just adpat what the docs
say but select merge replication. Doesn't work that way. Using SQL
studio, I have never been able to get to a peer-to-peer topology option
using anything but transaction replicas without updating subscriptions.
Using T-SQL, it looks like I can brute force peer to peer replication
with updating subscriptions but the sp_addmergedpublication function
does not have any options for peer-to-peer topology.
So, what gives? How do I set up peer-to-peer merge replication? Any
help would be greatly appreciated!
Thanks.
RandyThere did you read about Peer-to_Peer Merge Replication ?
I checked both BOL and the courseware and it only talks about
peer-to-peer transactional.

Markus

Configuring a remote server as a subscription server

I'm trying to do a merge replciation between two servers however the merge
agent fails announcing that: "The remote server is not defined as a
subscription server (The error number is 14010)".
Here are more details:
The first server (publisher & distributor) has SQL Server enterprise edition
installed using SQL Server authentication. The IP address for this server is
192.168.62.2 and the subnet mask is 255.255.255.0
The second server (subscriber) the same as the publisher however the IP
address is 192.168.64.2 with a subnet mask of 255.255.255.0.
Note that there is no domain connectiong the two server!
I have regisrtered the subscriber at the publisher and cretaed the merge
replciation successfully. However the merge agent fails as specified above!
Thanks in advance,
Shehab.
On the publisher go to Tools, Replication, Configure Publisher, Subscribers,
and Distribution, click on the Subscribers tab and add it there.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Shehab Kamal" <ShehabKamal@.discussions.microsoft.com> wrote in message
news:1BB0A342-B704-4222-B617-B6F70638AC3C@.microsoft.com...
> I'm trying to do a merge replciation between two servers however the merge
> agent fails announcing that: "The remote server is not defined as a
> subscription server (The error number is 14010)".
> Here are more details:
> The first server (publisher & distributor) has SQL Server enterprise
> edition
> installed using SQL Server authentication. The IP address for this server
> is
> 192.168.62.2 and the subnet mask is 255.255.255.0
> The second server (subscriber) the same as the publisher however the IP
> address is 192.168.64.2 with a subnet mask of 255.255.255.0.
> Note that there is no domain connectiong the two server!
> I have regisrtered the subscriber at the publisher and cretaed the merge
> replciation successfully. However the merge agent fails as specified
> above!
> Thanks in advance,
> Shehab.

Configuring 2 nodes as failovers for each other

We have a number of databases in our company and we recently had to buy a second SQL server.What I would like to do is have both SQL Servers act as failovers for each other.They both are the exact same hardware configuration (dell blades poweredge 1855) and we have a RAID array with Melio clustered file system for our web servers.I haven’t found any documentation on if this is even possible.Am I completely wrong in thinking this can be done or is there a better solution to spread the load but provide failover support with out buying 2 new machines?

Basic cluster 'failover' schemes require 'shared storage', such as SAN or NAS. If the disk array is dedicated to only one machine, it is not shared storage.

You might be better off examining Server Mirroring (if you are using SQL 2005).