connect to remote sql server failed

I couldn’t connect to the sql server instance (10.192.130.80\development2 and
10.192.130.80\development3) remotely on enterprise manager and query
analyzer. The error is sql server does not exist or access denied. I setup
well in the client network utility and put sever name and port number in it.
But I still got same error. Could someone give me some tips what reason is?
thanks.
Can you ping those servers?
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
You can't help someone get up a hill without getting a little closer to the
top yourself.
- H. Norman Schwarzkopf
"Iter" <Iter@.discussions.microsoft.com> wrote in message
news:39D7F4E4-6CA8-4588-8FB7-2758A1D4A83F@.microsoft.com...
>I couldn't connect to the sql server instance (10.192.130.80\development2
>and
> 10.192.130.80\development3) remotely on enterprise manager and query
> analyzer. The error is sql server does not exist or access denied. I setup
> well in the client network utility and put sever name and port number in
> it.
> But I still got same error. Could someone give me some tips what reason
> is?
> thanks.
>
|||Yes, I can Ping them.
"Arnie Rowland" wrote:

> Can you ping those servers?
> --
> Arnie Rowland, Ph.D.
> Westwood Consulting, Inc
> Most good judgment comes from experience.
> Most experience comes from bad judgment.
> - Anonymous
> You can't help someone get up a hill without getting a little closer to the
> top yourself.
> - H. Norman Schwarzkopf
>
> "Iter" <Iter@.discussions.microsoft.com> wrote in message
> news:39D7F4E4-6CA8-4588-8FB7-2758A1D4A83F@.microsoft.com...
>
>
|||Is the SQL Server listening on TCP?
Check the SQL ERRORLOG for a line like:
SQL Server listening on tcp, shared memory, named pipes
Kevin Hill
3NF Consulting
http://www.3nf-inc.com/NewsGroups.htm
Real-world stuff I run across with SQL Server:
http://kevin3nf.blogspot.com
"Iter" <Iter@.discussions.microsoft.com> wrote in message
news:39D7F4E4-6CA8-4588-8FB7-2758A1D4A83F@.microsoft.com...
>I couldn't connect to the sql server instance (10.192.130.80\development2
>and
> 10.192.130.80\development3) remotely on enterprise manager and query
> analyzer. The error is sql server does not exist or access denied. I setup
> well in the client network utility and put sever name and port number in
> it.
> But I still got same error. Could someone give me some tips what reason
> is?
> thanks.
>

connect to remote sql server failed

I couldn’t connect to the sql server instance (10.192.130.80\development2
and
10.192.130.80\development3) remotely on enterprise manager and query
analyzer. The error is sql server does not exist or access denied. I setup
well in the client network utility and put sever name and port number in it.
But I still got same error. Could someone give me some tips what reason is?
thanks.Can you ping those servers?
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
You can't help someone get up a hill without getting a little closer to the
top yourself.
- H. Norman Schwarzkopf
"Iter" <Iter@.discussions.microsoft.com> wrote in message
news:39D7F4E4-6CA8-4588-8FB7-2758A1D4A83F@.microsoft.com...
>I couldn't connect to the sql server instance (10.192.130.80\development2
>and
> 10.192.130.80\development3) remotely on enterprise manager and query
> analyzer. The error is sql server does not exist or access denied. I setup
> well in the client network utility and put sever name and port number in
> it.
> But I still got same error. Could someone give me some tips what reason
> is?
> thanks.
>|||Yes, I can Ping them.
"Arnie Rowland" wrote:

> Can you ping those servers?
> --
> Arnie Rowland, Ph.D.
> Westwood Consulting, Inc
> Most good judgment comes from experience.
> Most experience comes from bad judgment.
> - Anonymous
> You can't help someone get up a hill without getting a little closer to th
e
> top yourself.
> - H. Norman Schwarzkopf
>
> "Iter" <Iter@.discussions.microsoft.com> wrote in message
> news:39D7F4E4-6CA8-4588-8FB7-2758A1D4A83F@.microsoft.com...
>
>|||Is the SQL Server listening on TCP?
Check the SQL ERRORLOG for a line like:
SQL Server listening on tcp, shared memory, named pipes
Kevin Hill
3NF Consulting
http://www.3nf-inc.com/NewsGroups.htm
Real-world stuff I run across with SQL Server:
http://kevin3nf.blogspot.com
"Iter" <Iter@.discussions.microsoft.com> wrote in message
news:39D7F4E4-6CA8-4588-8FB7-2758A1D4A83F@.microsoft.com...
>I couldn't connect to the sql server instance (10.192.130.80\development2
>and
> 10.192.130.80\development3) remotely on enterprise manager and query
> analyzer. The error is sql server does not exist or access denied. I setup
> well in the client network utility and put sever name and port number in
> it.
> But I still got same error. Could someone give me some tips what reason
> is?
> thanks.
>sqlsql

Connect to remote server

From Enterprise Manager on my PC, how do I connect to a remote server over
the internet - I have the IP address, User Name and Password.

ThanksWhen creating an SQL connection using SQL Server EM you will need to:

Configure the server alias
Create the SQL connection.

Configure the Server alias

Open SQL Server Client Network Utility.
When Client Network Utility opens, click on the Alias tab.
Click on the Add button.
In the Server Alias text box enter a name for your SQL connection.
Select TCP/IP under Network libraries
Enter the IP address of the Server your SQL database is located on, in
the Server name text box.
Click on the OK button.
Your Server alias will now be configured, click on the Apply button.
Click on the OK button.

Create Connection

Open SQL Server Enterprise Manager
When Enterprise Manager opens, right click SQL Server Group and select
New SQL Server Registration.
The Register SQL Server wizard will now open.
Click on the Next button.
>From the Available Servers drop down menu, select the server alias you
created earlier.
Click on the Add button.
The server should now be listed under Added servers, click on the Next
button.
When the next dialog box appears select 'The SQL Server login
information that was assigned to me by the system administrator' (see
above).
Click on the Next button.
Enter your Login name and Password - this will be used every time you
connect to your SQL server. Click on the Next button.
Ensure that 'Add the SQL Server(s) to an existing SQL Server group' is
selected and 'SQL Server Group' is selected for Group name.

Click on the Next button.
When the next dialog box opens you can click on the Finish button.
Your SQL Connection will now be created.

HTH
Paul|||Paul

That works fine, thanks.

<stpaul_71@.yahoo.com> wrote in message
news:1102537081.548714.60980@.z14g2000cwz.googlegro ups.com...
> When creating an SQL connection using SQL Server EM you will need to:
> Configure the server alias
> Create the SQL connection.
> Configure the Server alias
> Open SQL Server Client Network Utility.
> When Client Network Utility opens, click on the Alias tab.
> Click on the Add button.
> In the Server Alias text box enter a name for your SQL connection.
> Select TCP/IP under Network libraries
> Enter the IP address of the Server your SQL database is located on, in
> the Server name text box.
> Click on the OK button.
> Your Server alias will now be configured, click on the Apply button.
> Click on the OK button.
>
> Create Connection
> Open SQL Server Enterprise Manager
> When Enterprise Manager opens, right click SQL Server Group and select
> New SQL Server Registration.
> The Register SQL Server wizard will now open.
> Click on the Next button.
>>From the Available Servers drop down menu, select the server alias you
> created earlier.
> Click on the Add button.
> The server should now be listed under Added servers, click on the Next
> button.
> When the next dialog box appears select 'The SQL Server login
> information that was assigned to me by the system administrator' (see
> above).
> Click on the Next button.
> Enter your Login name and Password - this will be used every time you
> connect to your SQL server. Click on the Next button.
> Ensure that 'Add the SQL Server(s) to an existing SQL Server group' is
> selected and 'SQL Server Group' is selected for Group name.
> Click on the Next button.
> When the next dialog box opens you can click on the Finish button.
> Your SQL Connection will now be created.
>
> HTH
> Paul

Connect To Oracle 10g 64 Bit using SQL Server Integration Services 2005 64 Bit

I am trying to create a oracle 10g connection in SSIS using connection manager and i am getting the following error,

Test Connection failed because of an error in initializing provider. Oracle client and networking

components were not found. These components are supplied by Oracle corporation and are part of the

Oracle version 7.3.3 or later client software installation.

Provider is unable to function until these components are installed.

Can someone please help.

Thanks.

If your operating System and VS2005 are 32bits then you need to download and install the Oracle 10g client for Windows 32bits, when I last downloaded it was more than 1gig install it and create your connection to the database make sure your TNS ORA works before adding SSIS connection to Oracle. The client tools are free but you need an Oracle Technet account which you can create for free. The Developer is also free it let you see Oracle tables and databases. If you are in an employer's network I find connecting with Named Pipes is easier than TCP/IP. One more thing watch the installer. Hope this helps.

http://www.oracle.com/technology/software/index.html

I forgot to add you must compile your code with AnyCPU.

|||

Thanks for your reply Caddre..

But.. i have MS 2003 64 bit OS.. i have installed oracle 10g 64 bit server.. i can successfully connect thru sqlplus.. no problem...

I am missing something on SQL 2005 and i am not sure what it is...

|||

So you are saying you have installed Oracle 10g 64bits client tools in the box? I know connecting through SQL plus does not solve development connection issue you need the client tools in your box this time 64bits. Another thing you are not missing anything but I think VS2005 unless you buy 64bits full version is 32bits that is not all your setup is 64bits, so you need to either make it all 64bits or develop in 32bits and deploy in 64bits because I read there are issues known issues.

|||

yes - as far as i know all are 64bit

I cannot connect thru both providers - OLEDB and Net Oracle client

|||

Try this recent Microsoft support article steps, I will still look for more info.

http://support.microsoft.com/kb/255084

|||

Hi Caddre,

Either you can have a look at summarized article here. or You may look for "Getting SSIS Packages To Run On A 64 Bit Box" in Sutha Thiru's Blog .

Thanks

Subhash Subramanyam

|||

thanks subash.. awesome..

those articles helped me to fix the issue...

appreciate yours and caddre help on this..

|||I am glad to see your problem is resolved and Subhash thanks for the articles much appreciated.

Connect to MSDE 2000 from SQL 2000 Ent. Manager

With SQL 2000 Ent. Manager I was able to connect to MSDE on another box. I
now have MSDE 2000 installed on the box. When I try to connect with SQL
2000 Ent. Manager I get the error "SQL Server does not exist or access
denied". I get the same error when I created an ODBC connection using the
same settings. I am however able to connect locally on the box using
Microsoft SQL Web Data Administration.
Any thoughts?
have you granted to permissions to the account on the other machine?
"Bishop" <kwayne@.new.rr.com> wrote in message
news:#vzRSOULEHA.2736@.TK2MSFTNGP11.phx.gbl...
> With SQL 2000 Ent. Manager I was able to connect to MSDE on another box.
I
> now have MSDE 2000 installed on the box. When I try to connect with SQL
> 2000 Ent. Manager I get the error "SQL Server does not exist or access
> denied". I get the same error when I created an ODBC connection using the
> same settings. I am however able to connect locally on the box using
> Microsoft SQL Web Data Administration.
> Any thoughts?
>
|||Verify that you have installed the network protocols to enable the remote
access.
To do that, use the tool on the box you installed MSDE2000.
Thierry
"Bishop" <kwayne@.new.rr.com> a crit dans le message de
news:%23vzRSOULEHA.2736@.TK2MSFTNGP11.phx.gbl...
> With SQL 2000 Ent. Manager I was able to connect to MSDE on another box.
I
> now have MSDE 2000 installed on the box. When I try to connect with SQL
> 2000 Ent. Manager I get the error "SQL Server does not exist or access
> denied". I get the same error when I created an ODBC connection using the
> same settings. I am however able to connect locally on the box using
> Microsoft SQL Web Data Administration.
> Any thoughts?
>
|||Hi, Where the tool network protocols?
Thanks, I have the same trouble
|||hi,
"aramgt" <anonymous@.discussions.microsoft.com> ha scritto nel messaggio
news:208EAA99-4E4F-4598-9415-7F443FB13297@.microsoft.com...
> Hi, Where the tool network protocols?
> Thanks, I have the same trouble
locate svrnetcn.exe on the server hosting your MSDE instance and execute
it...
eanble the desired network protocols...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.7.0 - DbaMgr ver 0.53.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Hi,
I completed all these steps and I can't connect using
server IP, just server name like server\machine.
Any ideas?

>--Original Message--
>hi,
>"aramgt" <anonymous@.discussions.microsoft.com> ha scritto
nel messaggio
>news:208EAA99-4E4F-4598-9415-7F443FB13297@.microsoft.com...
>locate svrnetcn.exe on the server hosting your MSDE
instance and execute
>it...
>eanble the desired network protocols...
>--
>Andrea Montanari (Microsoft MVP - SQL Server)
>http://www.asql.biz/DbaMgr.shtm
http://italy.mvps.org
>DbaMgr2k ver 0.7.0 - DbaMgr ver 0.53.0
>(my vb6+sql-dmo little try to provide MS MSDE 1.0 and
MSDE 2000 a visual
>interface)
>-- remove DMO to reply
>.
>
|||To connect with <SERVERNAME>, you need to install MSDE
from the command prompt with the "default" option, rather
than the "instancename" option.
[vbcol=seagreen]
>--Original Message--
>Hi,
>I completed all these steps and I can't connect using
>server IP, just server name like server\machine.
>Any ideas?
>
scritto[vbcol=seagreen]
>nel messaggio
7F443FB13297@.microsoft.com...
>instance and execute
>http://italy.mvps.org
>MSDE 2000 a visual
>.
>
|||Hi,
I'm working on a Windows 2000 Server and can't locate
svrnetcn.exe on it. Is there another way of setting the
required network protocols so that I can connect to MSDE
2000 remotely?
thanks

>--Original Message--
>hi,
>"aramgt" <anonymous@.discussions.microsoft.com> ha scritto
nel messaggio
>news:208EAA99-4E4F-4598-9415-7F443FB13297@.microsoft.com...
>locate svrnetcn.exe on the server hosting your MSDE
instance and execute
>it...
>eanble the desired network protocols...
>--
>Andrea Montanari (Microsoft MVP - SQL Server)
>http://www.asql.biz/DbaMgr.shtm
http://italy.mvps.org
>DbaMgr2k ver 0.7.0 - DbaMgr ver 0.53.0
>(my vb6+sql-dmo little try to provide MS MSDE 1.0 and
MSDE 2000 a visual
>interface)
>-- remove DMO to reply
>.
>
|||hi,
"kman" <anonymous@.discussions.microsoft.com> ha scritto nel messaggio
news:7a4701c43155$c4bf9e90$a401280a@.phx.gbl...
> Hi,
> I'm working on a Windows 2000 Server and can't locate
> svrnetcn.exe on it. Is there another way of setting the
> required network protocols so that I can connect to MSDE
> 2000 remotely?
if you have SQL Server installed on that server, you have to find it.. it's
the Server Network Utility listed in the SQL Server program group...
on client side, it's corresponding tool is the Client Network Utility,
cliconfg.exe
<Only for information>
you coul'd do i t manually editing the registry,
in the HKLM\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\Su perSocketNetLib
ProtocolList = tcp
for TCP/IP network protocol
BUT THIS IS NOT THE BEST WAY, please do it with the appropriate tool, the
Server Network Utility, where you can specify all your desired setting...
</Only for information>
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.7.0 - DbaMgr ver 0.53.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
sqlsql

Connect to enterprise manager

WIthin out network were all having issues connecting to SQL server, e.g. it
would allows connection when we can intermitadley connect.
Are the any know firewall issues or other known bugs?Hi,
Might be because of slow network, Try executing the below command from your
cleint PC
Ping <SQL Server IP Address> -t
If you get contineous "Request time out", then inform ur system / network
admin.
Thanks
Hari
MCDBA
"Matthew Burgess" <MatthewBurgess@.discussions.microsoft.com> wrote in
message news:E9A0AF8C-618F-4ECC-9775-0427625883B1@.microsoft.com...
> WIthin out network were all having issues connecting to SQL server, e.g.
> it
> would allows connection when we can intermitadley connect.
> Are the any know firewall issues or other known bugs?|||Hari,
Seems as if it could be that. DB on on internal netowrk are fine. But the
problem db is with our hositng compnay: we have a 2 Meg brodband line
(operating a 1.6mbit/sec).
Any suggest of what I can say to our hositng company? I know our IP are in
there firewall, and thus sometimes we can connect; would a firewall with an
ISP tend to stop ping's?
Other options could be our router or our ISP.
THanks for you help on this!
regards
MAtthew.
"Hari Prasad" wrote:
> Hi,
> Might be because of slow network, Try executing the below command from your
> cleint PC
> Ping <SQL Server IP Address> -t
> If you get contineous "Request time out", then inform ur system / network
> admin.
> Thanks
> Hari
> MCDBA
> "Matthew Burgess" <MatthewBurgess@.discussions.microsoft.com> wrote in
> message news:E9A0AF8C-618F-4ECC-9775-0427625883B1@.microsoft.com...
> > WIthin out network were all having issues connecting to SQL server, e.g.
> > it
> > would allows connection when we can intermitadley connect.
> >
> > Are the any know firewall issues or other known bugs?
>
>|||Hi Matthew
If you're trying to ping a server at your ISP, it can very well be that they
don't allow pinging. In most cases pinging is blocked from outside a
firewall - not only on ISP's but also on most other companies.
I'd suggest that you call your ISP and talk to them about this issue because
you'd need to have the proper ports open to get into your SQL server. I
don't know if they will allow this or not, but if not you might be able to
do it via a VPN connection.
Regards
Steen
Matthew Burgess wrote:
> Hari,
> Seems as if it could be that. DB on on internal netowrk are fine. But
> the problem db is with our hositng compnay: we have a 2 Meg brodband
> line (operating a 1.6mbit/sec).
> Any suggest of what I can say to our hositng company? I know our IP
> are in there firewall, and thus sometimes we can connect; would a
> firewall with an ISP tend to stop ping's?
> Other options could be our router or our ISP.
> THanks for you help on this!
> regards
> MAtthew.
> "Hari Prasad" wrote:
>> Hi,
>> Might be because of slow network, Try executing the below command
>> from your cleint PC
>> Ping <SQL Server IP Address> -t
>> If you get contineous "Request time out", then inform ur system /
>> network admin.
>> Thanks
>> Hari
>> MCDBA
>> "Matthew Burgess" <MatthewBurgess@.discussions.microsoft.com> wrote in
>> message news:E9A0AF8C-618F-4ECC-9775-0427625883B1@.microsoft.com...
>> WIthin out network were all having issues connecting to SQL server,
>> e.g. it
>> would allows connection when we can intermitadley connect.
>> Are the any know firewall issues or other known bugs?|||I got a similar problem in my network but in my case the network connection
goes well until the user opens Enterprise Manager and start working. In some
moment the network connection is lost, PINGing the server will not respond.
My network is not a slow one. This problems occurs for more than one user.
Will you please indicate me how you resolved the problem or any workaround
for this? I am almost decided to format that server with all the work that it
implies and its impact on my users
Thanks
César
> Hi Matthew
> If you're trying to ping a server at your ISP, it can very well be that they
> don't allow pinging. In most cases pinging is blocked from outside a
> firewall - not only on ISP's but also on most other companies.
> I'd suggest that you call your ISP and talk to them about this issue because
> you'd need to have the proper ports open to get into your SQL server. I
> don't know if they will allow this or not, but if not you might be able to
> do it via a VPN connection.
> Regards
> Steen
>
> Matthew Burgess wrote:
> > Hari,
> >
> > Seems as if it could be that. DB on on internal netowrk are fine. But
> > the problem db is with our hositng compnay: we have a 2 Meg brodband
> > line (operating a 1.6mbit/sec).
> >
> > Any suggest of what I can say to our hositng company? I know our IP
> > are in there firewall, and thus sometimes we can connect; would a
> > firewall with an ISP tend to stop ping's?
> >
> > Other options could be our router or our ISP.
> >
> > THanks for you help on this!
> >
> > regards
> >
> > MAtthew.
> >
> > "Hari Prasad" wrote:
> >
> >> Hi,
> >>
> >> Might be because of slow network, Try executing the below command
> >> from your cleint PC
> >>
> >> Ping <SQL Server IP Address> -t
> >>
> >> If you get contineous "Request time out", then inform ur system /
> >> network admin.
> >>
> >> Thanks
> >> Hari
> >> MCDBA
> >>
> >> "Matthew Burgess" <MatthewBurgess@.discussions.microsoft.com> wrote in
> >> message news:E9A0AF8C-618F-4ECC-9775-0427625883B1@.microsoft.com...
> >> WIthin out network were all having issues connecting to SQL server,
> >> e.g. it
> >> would allows connection when we can intermitadley connect.
> >>
> >> Are the any know firewall issues or other known bugs?
>
>|||I have a similar problem. The network connection is OK but when the user
enters Enterprise manager and starts working with some DTS, the connection
with the server is lost. PINGing the server do not respond. It happens in
more than one user. I have changed the redundant NIC but it remains the same.
Will you please give me a hint how did you manage to solve it or if you
tried any workaround for this?
"Steen Persson" wrote:
> Hi Matthew
> If you're trying to ping a server at your ISP, it can very well be that they
> don't allow pinging. In most cases pinging is blocked from outside a
> firewall - not only on ISP's but also on most other companies.
> I'd suggest that you call your ISP and talk to them about this issue because
> you'd need to have the proper ports open to get into your SQL server. I
> don't know if they will allow this or not, but if not you might be able to
> do it via a VPN connection.
> Regards
> Steen
>
> Matthew Burgess wrote:
> > Hari,
> >
> > Seems as if it could be that. DB on on internal netowrk are fine. But
> > the problem db is with our hositng compnay: we have a 2 Meg brodband
> > line (operating a 1.6mbit/sec).
> >
> > Any suggest of what I can say to our hositng company? I know our IP
> > are in there firewall, and thus sometimes we can connect; would a
> > firewall with an ISP tend to stop ping's?
> >
> > Other options could be our router or our ISP.
> >
> > THanks for you help on this!
> >
> > regards
> >
> > MAtthew.
> >
> > "Hari Prasad" wrote:
> >
> >> Hi,
> >>
> >> Might be because of slow network, Try executing the below command
> >> from your cleint PC
> >>
> >> Ping <SQL Server IP Address> -t
> >>
> >> If you get contineous "Request time out", then inform ur system /
> >> network admin.
> >>
> >> Thanks
> >> Hari
> >> MCDBA
> >>
> >> "Matthew Burgess" <MatthewBurgess@.discussions.microsoft.com> wrote in
> >> message news:E9A0AF8C-618F-4ECC-9775-0427625883B1@.microsoft.com...
> >> WIthin out network were all having issues connecting to SQL server,
> >> e.g. it
> >> would allows connection when we can intermitadley connect.
> >>
> >> Are the any know firewall issues or other known bugs?
>
>

Connect to enterprise manager

WIthin out network were all having issues connecting to SQL server, e.g. it
would allows connection when we can intermitadley connect.
Are the any know firewall issues or other known bugs?
Hi,
Might be because of slow network, Try executing the below command from your
cleint PC
Ping <SQL Server IP Address> -t
If you get contineous "Request time out", then inform ur system / network
admin.
Thanks
Hari
MCDBA
"Matthew Burgess" <MatthewBurgess@.discussions.microsoft.com> wrote in
message news:E9A0AF8C-618F-4ECC-9775-0427625883B1@.microsoft.com...
> WIthin out network were all having issues connecting to SQL server, e.g.
> it
> would allows connection when we can intermitadley connect.
> Are the any know firewall issues or other known bugs?
|||Hari,
Seems as if it could be that. DB on on internal netowrk are fine. But the
problem db is with our hositng compnay: we have a 2 Meg brodband line
(operating a 1.6mbit/sec).
Any suggest of what I can say to our hositng company? I know our IP are in
there firewall, and thus sometimes we can connect; would a firewall with an
ISP tend to stop ping's?
Other options could be our router or our ISP.
THanks for you help on this!
regards
MAtthew.
"Hari Prasad" wrote:

> Hi,
> Might be because of slow network, Try executing the below command from your
> cleint PC
> Ping <SQL Server IP Address> -t
> If you get contineous "Request time out", then inform ur system / network
> admin.
> Thanks
> Hari
> MCDBA
> "Matthew Burgess" <MatthewBurgess@.discussions.microsoft.com> wrote in
> message news:E9A0AF8C-618F-4ECC-9775-0427625883B1@.microsoft.com...
>
>
|||Hi Matthew
If you're trying to ping a server at your ISP, it can very well be that they
don't allow pinging. In most cases pinging is blocked from outside a
firewall - not only on ISP's but also on most other companies.
I'd suggest that you call your ISP and talk to them about this issue because
you'd need to have the proper ports open to get into your SQL server. I
don't know if they will allow this or not, but if not you might be able to
do it via a VPN connection.
Regards
Steen
Matthew Burgess wrote:[vbcol=seagreen]
> Hari,
> Seems as if it could be that. DB on on internal netowrk are fine. But
> the problem db is with our hositng compnay: we have a 2 Meg brodband
> line (operating a 1.6mbit/sec).
> Any suggest of what I can say to our hositng company? I know our IP
> are in there firewall, and thus sometimes we can connect; would a
> firewall with an ISP tend to stop ping's?
> Other options could be our router or our ISP.
> THanks for you help on this!
> regards
> MAtthew.
> "Hari Prasad" wrote:
|||I got a similar problem in my network but in my case the network connection
goes well until the user opens Enterprise Manager and start working. In some
moment the network connection is lost, PINGing the server will not respond.
My network is not a slow one. This problems occurs for more than one user.
Will you please indicate me how you resolved the problem or any workaround
for this? I am almost decided to format that server with all the work that it
implies and its impact on my users
Thanks
César
> Hi Matthew
> If you're trying to ping a server at your ISP, it can very well be that they
> don't allow pinging. In most cases pinging is blocked from outside a
> firewall - not only on ISP's but also on most other companies.
> I'd suggest that you call your ISP and talk to them about this issue because
> you'd need to have the proper ports open to get into your SQL server. I
> don't know if they will allow this or not, but if not you might be able to
> do it via a VPN connection.
> Regards
> Steen
>
> Matthew Burgess wrote:
>
>
|||I have a similar problem. The network connection is OK but when the user
enters Enterprise manager and starts working with some DTS, the connection
with the server is lost. PINGing the server do not respond. It happens in
more than one user. I have changed the redundant NIC but it remains the same.
Will you please give me a hint how did you manage to solve it or if you
tried any workaround for this?
"Steen Persson" wrote:

> Hi Matthew
> If you're trying to ping a server at your ISP, it can very well be that they
> don't allow pinging. In most cases pinging is blocked from outside a
> firewall - not only on ISP's but also on most other companies.
> I'd suggest that you call your ISP and talk to them about this issue because
> you'd need to have the proper ports open to get into your SQL server. I
> don't know if they will allow this or not, but if not you might be able to
> do it via a VPN connection.
> Regards
> Steen
>
> Matthew Burgess wrote:
>
>

Connect to database without showing the "Connect to Server" dialog box?

Is it possible to configure the SQL Server Management Studio to behave like good old Enterprise Manager, so that it automatically connects to my configured servers without showing the "Connect to Server" dialog box every time upon startup?

After successlessly searching Google and these forums, I still found no suitable answer to this question (maybe beside this one).

Thanks
Uwe

You ae right this is not possible, perhaps you can suggest that as a feature request on connect.microsoft.com ?

HTH, Jens Suessmeyer.

http://www.sqlserver2005.de|||Done:

http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=180590

Thanks, Jens .|||You got my vote.

-Jens.|||Strange - they marked the ticket as "closed" and "solved", but no further comments.

Anyone knows what this actually means? IS it already present and I did not found it? Or will it be implemented in a further version?

Thanks
Uwe

connect to cluster server issue

Hi,
I had SQL 2000 client, and tried to register to SQL 7 cluster server in Enterprise Manager. But the registering process hang.
Does anyone know the issue? It happen to other users as well.
Thanks.
yuling
Hi,
Acturally, I tried to connect to SQL 2000 cluster server in Enterprise Manager. But, the process hangs. I am able to register this SQL server from any of my sql server machine. BTW, I can connect by using Query Analyzer without any issue as well. What
's the issue?
Thank you if anyone has this issue. Tks.
Yuling
sqlsql

connect to cluster server issue

Hi,
I had SQL 2000 client, and tried to register to SQL 7 cluster server in Ente
rprise Manager. But the registering process hang.
Does anyone know the issue? It happen to other users as well.
Thanks.
yulingHi,
Acturally, I tried to connect to SQL 2000 cluster server in Enterprise Manag
er. But, the process hangs. I am able to register this SQL server from any
of my sql server machine. BTW, I can connect by using Query Analyzer witho
ut any issue as well. What
's the issue?
Thank you if anyone has this issue. Tks.
Yuling

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 Analysis Manager via VB2005

Does anybody know how to use VB2005 or VB.NET to connect to analysis manager to extract the CUBE information?

Can I have a sample program? I'm very stuck.

Thanks in advance :)

Check out AMO for the cubes metadata
or ADOMD.net to query the cube

There are some examples on those pages, and there are more in the sql server samples.

C

Connect to Analysis Manager over HTTPS and non domain account

Please, I need your help... I`m desperate...

I`m trying to connect to the Analysis Services (AS 2000 Enterprise Edition SP4 on Windows Server 2003 EE, respository is in Access DB) throught Analysis Manager over HTTPS(HTTP) connection. I dont want to use domain account.

I need to specify USER_ID and PASSWORD to the Analysis Manager, but in registration of new server is only IP address or HTTP adress (for http://server) - but it doesnt work - it says Unauthorized. But I`ve tried to use Anonymous account and it doesn`t work (client wan`t able to make connection)... I would like to use Basic Authentification... Thise account is member of OLAP_Administrators... but the problem is where should I put USER_ID and PASSWORD?

It works perfect in Excel 2003... MSOLAP.asp work fine in IE...

Thanks very much for your advise

RicmondIs it due to "BUG: Analysis Manager Does Not Support HTTP or HTTPS onnections"

http://support.microsoft.com/default.aspx?scid=kb;en-us;Q311310

Ricmond

Connect to a Novell NDS Datasoource via LDAP

Hi All,

Is there a connector in Connections Manager that can access a Novell NDS tree and help to pull data in an SSIS package?

Thanks,

BIG SYou might be able to use a script component (vb.net) as a source to get at your Novell tree.|||Can't. I run a component in CLR and it craps out.Would SSIS be any different?|||There is a Novell ODBC connector which allows you to do that. Check out Novell's website for "NDK:Novell

ODBC Driver for eDirectory".

You need to have rights to the NDS to get the information and you need to have the Novell CLIENT installed before you install the driver (which they don't tell you).|||Is that a connector that I can add to SSIS?|||

BIG S wrote:

Is that a connector that I can add to SSIS?

Once it's installed, you can use a datareader source against the ODBC driver.|||Would simply like to pull user object data back from eDirectory to MS SQL without having to implement the Novell Client, which I think is needed for the Novell ODBC driver. This can be done with a couple of lines of perl... Isn't there an easy way to make this connection and pull this data from within SQL Server? It's just an ldap query....sqlsql

Connect to a Novell NDS Datasoource via LDAP

Hi All,

Is there a connector in Connections Manager that can access a Novell NDS tree and help to pull data in an SSIS package?

Thanks,

BIG S
You might be able to use a script component (vb.net) as a source to get at your Novell tree.|||Can't. I run a component in CLR and it craps out.Would SSIS be any different?
|||There is a Novell ODBC connector which allows you to do that. Check out Novell's website for "NDK:Novell ODBC Driver for eDirectory".

You need to have rights to the NDS to get the information and you need to have the Novell CLIENT installed before you install the driver (which they don't tell you).

|||Is that a connector that I can add to SSIS?
|||

BIG S wrote:

Is that a connector that I can add to SSIS?

Once it's installed, you can use a datareader source against the ODBC driver.|||Would simply like to pull user object data back from eDirectory to MS SQL without having to implement the Novell Client, which I think is needed for the Novell ODBC driver. This can be done with a couple of lines of perl... Isn't there an easy way to make this connection and pull this data from within SQL Server? It's just an ldap query....

connect the SQL Server in different domains

HI ALL
I have tow domains, in the same forest. From one domain, which has a SQL Ser
ver A , I want to use the Enterprise manager or the Query Analyzer to connec
t the SQL Server B in the other domain and vise versa. Could any one elabora
te all the method to do tha
t.
thank you very much.I'm assuming this is more than just opening Query Analyzer and connecting to
a server name. What you probably want to do is add a linked server -- go to
SQL Enterprise Manager and add a new linked server under the security
section. That will let you run queries such as
select * from serverb.<database>.<owner>.<table>
****************************************
***************************
Andy S.
MCSE NT/2000, MCDBA SQL 7/2000
andymcdba1@.NOMORESPAM.yahoo.com
Please remove NOMORESPAM before replying.
Always keep your antivirus and Microsoft software
up to date with the latest definitions and product updates.
Be suspicious of every email attachment, I will never send
or post anything other than the text of a http:// link nor
post the link directly to a file for downloading.
This posting is provided "as is" with no warranties
and confers no rights.
****************************************
***************************
"ALLEN" <anonymous@.discussions.microsoft.com> wrote in message
news:3F57F4DF-7BB7-4C66-A362-5C112F850ABE@.microsoft.com...
> HI ALL
> I have tow domains, in the same forest. From one domain, which has a SQL
Server A , I want to use the Enterprise manager or the Query Analyzer to
connect the SQL Server B in the other domain and vise versa. Could any one
elaborate all the method to do that.
> thank you very much.|||You should not find any difference in normal connectivity, but there is one
thing that you might want to be aware of in this particular scenario. If you
want to use Kerberos Authenticatin then you will have to register an SPN for
the SQL Server using NETBIOS name.
Generally SPN should be registered in the following format
MSSQLSvc/sqlmachine.domain.net:1433 sqlserviceact
But to enable Kerberos protocol in this inter domain scenario, you will also
need to register an SPN using the NETBIOS name
MSSQLSvc/sqlmachine:1433 sqlserviceact
Thanks,
Bala.
This posting is provided "AS IS" with no warranties, and confers no
rights.
"ALLEN" <anonymous@.discussions.microsoft.com> wrote in message
news:3F57F4DF-7BB7-4C66-A362-5C112F850ABE@.microsoft.com...
> HI ALL
> I have tow domains, in the same forest. From one domain, which has a SQL
Server A , I want to use the Enterprise manager or the Query Analyzer to
connect the SQL Server B in the other domain and vise versa. Could any one
elaborate all the method to do that.
> thank you very much.

Connect at only One port

When connecting to sql 2000 Enterprise manager opens multiple ports.
For example
Proto Local Address Foreign Address State
TCP 192.168.7.12:1433 192.168.7.12:3275 ESTABLISHED
TCP 192.168.7.12:1433 192.168.7.12:3634 ESTABLISHED
TCP 192.168.7.12:3634 192.168.7.12:1433 ESTABLISHED
How can I force sql to connect only at 1433 or other single port. I facts
is there such posibility?
Hi -
If you analyze the entries in the SQL Server error log file, you can verify
that the instance of SQL Server is listening on the correct IP address and on
the correct port. By default, a default instance of SQL Server listens on the
port 1433. You can also use Server Network Utility to verify the protocol
settings for SQL Server and to change the properties in SQL Server, including
the protocols that can connect to SQL Server and the ports that can be used.
For more information about using Server Network Utility, see the "SQL Server
Network Utility" topic in SQL Server Books Online.
Sometimes, SQL Server 2000 may not bind to port 1433 or any other specified
port. This problem may occur if the port is being used by another application
or if you are trying to connect by using an IP address that is not correct.
Therefore, the TCP/IP connections to SQL Server may not be successful and you
may receive the following error message in the SQL Server error log file:
2001-11-14 15:49:14.12 server SuperSocket Info: Bind failed on TCP port 1433.
Please check the below link :
http://support.microsoft.com/default.aspx?kbid=307197
Let me know if it helps you.
"Radin" wrote:

> When connecting to sql 2000 Enterprise manager opens multiple ports.
> For example
> Proto Local Address Foreign Address State
> TCP 192.168.7.12:1433 192.168.7.12:3275 ESTABLISHED
> TCP 192.168.7.12:1433 192.168.7.12:3634 ESTABLISHED
> TCP 192.168.7.12:3634 192.168.7.12:1433 ESTABLISHED
> How can I force sql to connect only at 1433 or other single port. I facts
> is there such posibility?
>

Connect at only One port

When connecting to sql 2000 Enterprise manager opens multiple ports.
For example
Proto Local Address Foreign Address State
TCP 192.168.7.12:1433 192.168.7.12:3275 ESTABLISHED
TCP 192.168.7.12:1433 192.168.7.12:3634 ESTABLISHED
TCP 192.168.7.12:3634 192.168.7.12:1433 ESTABLISHED
How can I force sql to connect only at 1433 or other single port. I facts
is there such posibility?Hi -
If you analyze the entries in the SQL Server error log file, you can verify
that the instance of SQL Server is listening on the correct IP address and o
n
the correct port. By default, a default instance of SQL Server listens on th
e
port 1433. You can also use Server Network Utility to verify the protocol
settings for SQL Server and to change the properties in SQL Server, includin
g
the protocols that can connect to SQL Server and the ports that can be used.
For more information about using Server Network Utility, see the "SQL Server
Network Utility" topic in SQL Server Books Online.
Sometimes, SQL Server 2000 may not bind to port 1433 or any other specified
port. This problem may occur if the port is being used by another applicatio
n
or if you are trying to connect by using an IP address that is not correct.
Therefore, the TCP/IP connections to SQL Server may not be successful and yo
u
may receive the following error message in the SQL Server error log file:
2001-11-14 15:49:14.12 server SuperSocket Info: Bind failed on TCP port 1433
.
Please check the below link :
http://support.microsoft.com/default.aspx?kbid=307197
Let me know if it helps you.
"Radin" wrote:

> When connecting to sql 2000 Enterprise manager opens multiple ports.
> For example
> Proto Local Address Foreign Address State
> TCP 192.168.7.12:1433 192.168.7.12:3275 ESTABLISHED
> TCP 192.168.7.12:1433 192.168.7.12:3634 ESTABLISHED
> TCP 192.168.7.12:3634 192.168.7.12:1433 ESTABLISHED
> How can I force sql to connect only at 1433 or other single port. I facts
> is there such posibility?
>

Connect across Internet through NAT router

I am attempting to use Enterprise Manager to connect to SS 2000 across the
Internet. The machine running SQL Server is behind a NAT router.
Enterprise manager shows that the TCP/IP port that SQL Server is using is
1061. I have forwared port 1061 on the router to the machine running SQL
Server. When I attempt to register the server in Enterprise Manager I use
the WAN IP address of the router as the server name. However, registration
fails with the message "SQL Server does not exist or access denied."
What am I doing wrong?
Bill ToddI found an article in BOL saying that UDP port 1434 must also be
forwarded, however, doing so did not help.
Bill Todd

Connect across Internet through NAT router

I am attempting to use Enterprise Manager to connect to SS 2000 across the
Internet. The machine running SQL Server is behind a NAT router.
Enterprise manager shows that the TCP/IP port that SQL Server is using is
1061. I have forwared port 1061 on the router to the machine running SQL
Server. When I attempt to register the server in Enterprise Manager I use
the WAN IP address of the router as the server name. However, registration
fails with the message "SQL Server does not exist or access denied."
What am I doing wrong?
Bill Todd
I found an article in BOL saying that UDP port 1434 must also be
forwarded, however, doing so did not help.
Bill Todd