I am trying to reregister an existing server that we've been able to
register previously.
I can successfully register it inside the network, i.e., from another
workstation on the network, but when I try to register via a gateway, i.e.,
over the internet I can't. I can ping the server, and the router has port
forwarding setup correctly (port 1433), I've turned off the firewall, and
nothing else has changed that I am aware of, but it just won't respond. I
am confident that the SA password is correct.
I'm stumped. I have remote users who need to access this server, but can't
get in.
Can anyone give me any suggestions. I've tried everything I can imagine.
The one change on this system is that we had to reinstall the Server, and
we've installed CA Antivirus. But I've uninstalled the CA firewall
software, and turned off the Windows Firewall (just to get this up...we had
it running before with SQL traffic allowed).
Any Ideas are welcome!!
Bob
Hi Bob
"Bob Bartel" wrote:
> I am trying to reregister an existing server that we've been able to
> register previously.
> I can successfully register it inside the network, i.e., from another
> workstation on the network, but when I try to register via a gateway, i.e.,
> over the internet I can't. I can ping the server, and the router has port
> forwarding setup correctly (port 1433), I've turned off the firewall, and
> nothing else has changed that I am aware of, but it just won't respond. I
> am confident that the SA password is correct.
> I'm stumped. I have remote users who need to access this server, but can't
> get in.
> Can anyone give me any suggestions. I've tried everything I can imagine.
> The one change on this system is that we had to reinstall the Server, and
> we've installed CA Antivirus. But I've uninstalled the CA firewall
> software, and turned off the Windows Firewall (just to get this up...we had
> it running before with SQL traffic allowed).
> Any Ideas are welcome!!
> Bob
>
It would be safer to use a VPN for this rather than leaving the server open.
http://support.microsoft.com/kb/287932 describes the communication between
the client and server, make sure you are using TCP/IP protcols and the client
is not blocking the returning traffic. If you have set up this correctly you
should be in-undated with people trying to hack in.
John
|||As I mentioned, I have already had this working before. And only shut down
my firewall for this test. I agree a VPN is a good choice and I'll probably
turn it on, but...
But the real problem is that even with the router correctly forwarding 1433
and the firewall configured to allow the traffic, I can't register the
server remotely.
The only thing I can think of that may be effecting it is that I had to
reinstall the server. Can anyone think of anything that would keep remote
users from registering with a new install? Is there some setting on the
server that I neglected to turn back on?
Bob
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:5E55FAA1-601D-4DED-8E5C-0324E2ED46B6@.microsoft.com...
> Hi Bob
> "Bob Bartel" wrote:
> It would be safer to use a VPN for this rather than leaving the server
> open.
> http://support.microsoft.com/kb/287932 describes the communication between
> the client and server, make sure you are using TCP/IP protcols and the
> client
> is not blocking the returning traffic. If you have set up this correctly
> you
> should be in-undated with people trying to hack in.
> John
|||Hi
"Bob Bartel" wrote:
> As I mentioned, I have already had this working before. And only shut down
> my firewall for this test. I agree a VPN is a good choice and I'll probably
> turn it on, but...
> But the real problem is that even with the router correctly forwarding 1433
> and the firewall configured to allow the traffic, I can't register the
> server remotely.
> The only thing I can think of that may be effecting it is that I had to
> reinstall the server. Can anyone think of anything that would keep remote
> users from registering with a new install? Is there some setting on the
> server that I neglected to turn back on?
> Bob
>
If this is SQL Express you may not have turned on remote access. If this is
a named instance then it would not be using the default ports.
John
|||Its a named instance...where to I specify the port?
bob
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:1B0EB2A5-8E12-41C2-9D87-5C38176D1783@.microsoft.com...
> Hi
> "Bob Bartel" wrote:
> If this is SQL Express you may not have turned on remote access. If this
> is
> a named instance then it would not be using the default ports.
> John
|||Hi Bob
"Bob Bartel" wrote:
> Its a named instance...where to I specify the port?
> bob
In the SQL Server Configuration manager there will be an entry in the SQL
Server 2005 Network Configuration branch for your instance. This will shows
which protocols are installed and enabled. Right clicking TCP/IP and choosing
properties and on the IP Address tab you can set the protocol to be enabled
and also set the port. You will need to make sure that there are no other
instances using this port.
John
Showing posts with label network. Show all posts
Showing posts with label network. Show all posts
Monday, March 26, 2012
Problem Registering Existing Server
I am trying to reregister an existing server that we've been able to
register previously.
I can successfully register it inside the network, i.e., from another
workstation on the network, but when I try to register via a gateway, i.e.,
over the internet I can't. I can ping the server, and the router has port
forwarding setup correctly (port 1433), I've turned off the firewall, and
nothing else has changed that I am aware of, but it just won't respond. I
am confident that the SA password is correct.
I'm stumped. I have remote users who need to access this server, but can't
get in.
Can anyone give me any suggestions. I've tried everything I can imagine.
The one change on this system is that we had to reinstall the Server, and
we've installed CA Antivirus. But I've uninstalled the CA firewall
software, and turned off the Windows Firewall (just to get this up...we had
it running before with SQL traffic allowed).
Any Ideas are welcome!!
BobHi Bob
"Bob Bartel" wrote:
> I am trying to reregister an existing server that we've been able to
> register previously.
> I can successfully register it inside the network, i.e., from another
> workstation on the network, but when I try to register via a gateway, i.e.,
> over the internet I can't. I can ping the server, and the router has port
> forwarding setup correctly (port 1433), I've turned off the firewall, and
> nothing else has changed that I am aware of, but it just won't respond. I
> am confident that the SA password is correct.
> I'm stumped. I have remote users who need to access this server, but can't
> get in.
> Can anyone give me any suggestions. I've tried everything I can imagine.
> The one change on this system is that we had to reinstall the Server, and
> we've installed CA Antivirus. But I've uninstalled the CA firewall
> software, and turned off the Windows Firewall (just to get this up...we had
> it running before with SQL traffic allowed).
> Any Ideas are welcome!!
> Bob
>
It would be safer to use a VPN for this rather than leaving the server open.
http://support.microsoft.com/kb/287932 describes the communication between
the client and server, make sure you are using TCP/IP protcols and the client
is not blocking the returning traffic. If you have set up this correctly you
should be in-undated with people trying to hack in.
John|||As I mentioned, I have already had this working before. And only shut down
my firewall for this test. I agree a VPN is a good choice and I'll probably
turn it on, but...
But the real problem is that even with the router correctly forwarding 1433
and the firewall configured to allow the traffic, I can't register the
server remotely.
The only thing I can think of that may be effecting it is that I had to
reinstall the server. Can anyone think of anything that would keep remote
users from registering with a new install? Is there some setting on the
server that I neglected to turn back on?
Bob
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:5E55FAA1-601D-4DED-8E5C-0324E2ED46B6@.microsoft.com...
> Hi Bob
> "Bob Bartel" wrote:
>> I am trying to reregister an existing server that we've been able to
>> register previously.
>> I can successfully register it inside the network, i.e., from another
>> workstation on the network, but when I try to register via a gateway,
>> i.e.,
>> over the internet I can't. I can ping the server, and the router has
>> port
>> forwarding setup correctly (port 1433), I've turned off the firewall,
>> and
>> nothing else has changed that I am aware of, but it just won't respond.
>> I
>> am confident that the SA password is correct.
>> I'm stumped. I have remote users who need to access this server, but
>> can't
>> get in.
>> Can anyone give me any suggestions. I've tried everything I can imagine.
>> The one change on this system is that we had to reinstall the Server, and
>> we've installed CA Antivirus. But I've uninstalled the CA firewall
>> software, and turned off the Windows Firewall (just to get this up...we
>> had
>> it running before with SQL traffic allowed).
>> Any Ideas are welcome!!
>> Bob
> It would be safer to use a VPN for this rather than leaving the server
> open.
> http://support.microsoft.com/kb/287932 describes the communication between
> the client and server, make sure you are using TCP/IP protcols and the
> client
> is not blocking the returning traffic. If you have set up this correctly
> you
> should be in-undated with people trying to hack in.
> John|||Hi
"Bob Bartel" wrote:
> As I mentioned, I have already had this working before. And only shut down
> my firewall for this test. I agree a VPN is a good choice and I'll probably
> turn it on, but...
> But the real problem is that even with the router correctly forwarding 1433
> and the firewall configured to allow the traffic, I can't register the
> server remotely.
> The only thing I can think of that may be effecting it is that I had to
> reinstall the server. Can anyone think of anything that would keep remote
> users from registering with a new install? Is there some setting on the
> server that I neglected to turn back on?
> Bob
>
If this is SQL Express you may not have turned on remote access. If this is
a named instance then it would not be using the default ports.
John|||Its a named instance...where to I specify the port?
bob
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:1B0EB2A5-8E12-41C2-9D87-5C38176D1783@.microsoft.com...
> Hi
> "Bob Bartel" wrote:
>> As I mentioned, I have already had this working before. And only shut
>> down
>> my firewall for this test. I agree a VPN is a good choice and I'll
>> probably
>> turn it on, but...
>> But the real problem is that even with the router correctly forwarding
>> 1433
>> and the firewall configured to allow the traffic, I can't register the
>> server remotely.
>> The only thing I can think of that may be effecting it is that I had to
>> reinstall the server. Can anyone think of anything that would keep
>> remote
>> users from registering with a new install? Is there some setting on the
>> server that I neglected to turn back on?
>> Bob
>>
> If this is SQL Express you may not have turned on remote access. If this
> is
> a named instance then it would not be using the default ports.
> John|||Hi Bob
"Bob Bartel" wrote:
> Its a named instance...where to I specify the port?
> bob
In the SQL Server Configuration manager there will be an entry in the SQL
Server 2005 Network Configuration branch for your instance. This will shows
which protocols are installed and enabled. Right clicking TCP/IP and choosing
properties and on the IP Address tab you can set the protocol to be enabled
and also set the port. You will need to make sure that there are no other
instances using this port.
John
register previously.
I can successfully register it inside the network, i.e., from another
workstation on the network, but when I try to register via a gateway, i.e.,
over the internet I can't. I can ping the server, and the router has port
forwarding setup correctly (port 1433), I've turned off the firewall, and
nothing else has changed that I am aware of, but it just won't respond. I
am confident that the SA password is correct.
I'm stumped. I have remote users who need to access this server, but can't
get in.
Can anyone give me any suggestions. I've tried everything I can imagine.
The one change on this system is that we had to reinstall the Server, and
we've installed CA Antivirus. But I've uninstalled the CA firewall
software, and turned off the Windows Firewall (just to get this up...we had
it running before with SQL traffic allowed).
Any Ideas are welcome!!
BobHi Bob
"Bob Bartel" wrote:
> I am trying to reregister an existing server that we've been able to
> register previously.
> I can successfully register it inside the network, i.e., from another
> workstation on the network, but when I try to register via a gateway, i.e.,
> over the internet I can't. I can ping the server, and the router has port
> forwarding setup correctly (port 1433), I've turned off the firewall, and
> nothing else has changed that I am aware of, but it just won't respond. I
> am confident that the SA password is correct.
> I'm stumped. I have remote users who need to access this server, but can't
> get in.
> Can anyone give me any suggestions. I've tried everything I can imagine.
> The one change on this system is that we had to reinstall the Server, and
> we've installed CA Antivirus. But I've uninstalled the CA firewall
> software, and turned off the Windows Firewall (just to get this up...we had
> it running before with SQL traffic allowed).
> Any Ideas are welcome!!
> Bob
>
It would be safer to use a VPN for this rather than leaving the server open.
http://support.microsoft.com/kb/287932 describes the communication between
the client and server, make sure you are using TCP/IP protcols and the client
is not blocking the returning traffic. If you have set up this correctly you
should be in-undated with people trying to hack in.
John|||As I mentioned, I have already had this working before. And only shut down
my firewall for this test. I agree a VPN is a good choice and I'll probably
turn it on, but...
But the real problem is that even with the router correctly forwarding 1433
and the firewall configured to allow the traffic, I can't register the
server remotely.
The only thing I can think of that may be effecting it is that I had to
reinstall the server. Can anyone think of anything that would keep remote
users from registering with a new install? Is there some setting on the
server that I neglected to turn back on?
Bob
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:5E55FAA1-601D-4DED-8E5C-0324E2ED46B6@.microsoft.com...
> Hi Bob
> "Bob Bartel" wrote:
>> I am trying to reregister an existing server that we've been able to
>> register previously.
>> I can successfully register it inside the network, i.e., from another
>> workstation on the network, but when I try to register via a gateway,
>> i.e.,
>> over the internet I can't. I can ping the server, and the router has
>> port
>> forwarding setup correctly (port 1433), I've turned off the firewall,
>> and
>> nothing else has changed that I am aware of, but it just won't respond.
>> I
>> am confident that the SA password is correct.
>> I'm stumped. I have remote users who need to access this server, but
>> can't
>> get in.
>> Can anyone give me any suggestions. I've tried everything I can imagine.
>> The one change on this system is that we had to reinstall the Server, and
>> we've installed CA Antivirus. But I've uninstalled the CA firewall
>> software, and turned off the Windows Firewall (just to get this up...we
>> had
>> it running before with SQL traffic allowed).
>> Any Ideas are welcome!!
>> Bob
> It would be safer to use a VPN for this rather than leaving the server
> open.
> http://support.microsoft.com/kb/287932 describes the communication between
> the client and server, make sure you are using TCP/IP protcols and the
> client
> is not blocking the returning traffic. If you have set up this correctly
> you
> should be in-undated with people trying to hack in.
> John|||Hi
"Bob Bartel" wrote:
> As I mentioned, I have already had this working before. And only shut down
> my firewall for this test. I agree a VPN is a good choice and I'll probably
> turn it on, but...
> But the real problem is that even with the router correctly forwarding 1433
> and the firewall configured to allow the traffic, I can't register the
> server remotely.
> The only thing I can think of that may be effecting it is that I had to
> reinstall the server. Can anyone think of anything that would keep remote
> users from registering with a new install? Is there some setting on the
> server that I neglected to turn back on?
> Bob
>
If this is SQL Express you may not have turned on remote access. If this is
a named instance then it would not be using the default ports.
John|||Its a named instance...where to I specify the port?
bob
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:1B0EB2A5-8E12-41C2-9D87-5C38176D1783@.microsoft.com...
> Hi
> "Bob Bartel" wrote:
>> As I mentioned, I have already had this working before. And only shut
>> down
>> my firewall for this test. I agree a VPN is a good choice and I'll
>> probably
>> turn it on, but...
>> But the real problem is that even with the router correctly forwarding
>> 1433
>> and the firewall configured to allow the traffic, I can't register the
>> server remotely.
>> The only thing I can think of that may be effecting it is that I had to
>> reinstall the server. Can anyone think of anything that would keep
>> remote
>> users from registering with a new install? Is there some setting on the
>> server that I neglected to turn back on?
>> Bob
>>
> If this is SQL Express you may not have turned on remote access. If this
> is
> a named instance then it would not be using the default ports.
> John|||Hi Bob
"Bob Bartel" wrote:
> Its a named instance...where to I specify the port?
> bob
In the SQL Server Configuration manager there will be an entry in the SQL
Server 2005 Network Configuration branch for your instance. This will shows
which protocols are installed and enabled. Right clicking TCP/IP and choosing
properties and on the IP Address tab you can set the protocol to be enabled
and also set the port. You will need to make sure that there are no other
instances using this port.
John
Problem Registering Existing Server
I am trying to reregister an existing server that we've been able to
register previously.
I can successfully register it inside the network, i.e., from another
workstation on the network, but when I try to register via a gateway, i.e.,
over the internet I can't. I can ping the server, and the router has port
forwarding setup correctly (port 1433), I've turned off the firewall, and
nothing else has changed that I am aware of, but it just won't respond. I
am confident that the SA password is correct.
I'm stumped. I have remote users who need to access this server, but can't
get in.
Can anyone give me any suggestions. I've tried everything I can imagine.
The one change on this system is that we had to reinstall the Server, and
we've installed CA Antivirus. But I've uninstalled the CA firewall
software, and turned off the Windows Firewall (just to get this up...we had
it running before with SQL traffic allowed).
Any Ideas are welcome!!
BobHi Bob
"Bob Bartel" wrote:
> I am trying to reregister an existing server that we've been able to
> register previously.
> I can successfully register it inside the network, i.e., from another
> workstation on the network, but when I try to register via a gateway, i.e.
,
> over the internet I can't. I can ping the server, and the router has port
> forwarding setup correctly (port 1433), I've turned off the firewall, and
> nothing else has changed that I am aware of, but it just won't respond. I
> am confident that the SA password is correct.
> I'm stumped. I have remote users who need to access this server, but can'
t
> get in.
> Can anyone give me any suggestions. I've tried everything I can imagine.
> The one change on this system is that we had to reinstall the Server, and
> we've installed CA Antivirus. But I've uninstalled the CA firewall
> software, and turned off the Windows Firewall (just to get this up...we ha
d
> it running before with SQL traffic allowed).
> Any Ideas are welcome!!
> Bob
>
It would be safer to use a VPN for this rather than leaving the server open.
http://support.microsoft.com/kb/287932 describes the communication between
the client and server, make sure you are using TCP/IP protcols and the clien
t
is not blocking the returning traffic. If you have set up this correctly you
should be in-undated with people trying to hack in.
John|||As I mentioned, I have already had this working before. And only shut down
my firewall for this test. I agree a VPN is a good choice and I'll probably
turn it on, but...
But the real problem is that even with the router correctly forwarding 1433
and the firewall configured to allow the traffic, I can't register the
server remotely.
The only thing I can think of that may be effecting it is that I had to
reinstall the server. Can anyone think of anything that would keep remote
users from registering with a new install? Is there some setting on the
server that I neglected to turn back on?
Bob
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:5E55FAA1-601D-4DED-8E5C-0324E2ED46B6@.microsoft.com...
> Hi Bob
> "Bob Bartel" wrote:
>
> It would be safer to use a VPN for this rather than leaving the server
> open.
> http://support.microsoft.com/kb/287932 describes the communication between
> the client and server, make sure you are using TCP/IP protcols and the
> client
> is not blocking the returning traffic. If you have set up this correctly
> you
> should be in-undated with people trying to hack in.
> John|||Hi
"Bob Bartel" wrote:
> As I mentioned, I have already had this working before. And only shut dow
n
> my firewall for this test. I agree a VPN is a good choice and I'll probab
ly
> turn it on, but...
> But the real problem is that even with the router correctly forwarding 143
3
> and the firewall configured to allow the traffic, I can't register the
> server remotely.
> The only thing I can think of that may be effecting it is that I had to
> reinstall the server. Can anyone think of anything that would keep remote
> users from registering with a new install? Is there some setting on the
> server that I neglected to turn back on?
> Bob
>
If this is SQL Express you may not have turned on remote access. If this is
a named instance then it would not be using the default ports.
John|||Its a named instance...where to I specify the port?
bob
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:1B0EB2A5-8E12-41C2-9D87-5C38176D1783@.microsoft.com...
> Hi
> "Bob Bartel" wrote:
>
> If this is SQL Express you may not have turned on remote access. If this
> is
> a named instance then it would not be using the default ports.
> John|||Hi Bob
"Bob Bartel" wrote:
> Its a named instance...where to I specify the port?
> bob
In the SQL Server Configuration manager there will be an entry in the SQL
Server 2005 Network Configuration branch for your instance. This will shows
which protocols are installed and enabled. Right clicking TCP/IP and choosin
g
properties and on the IP Address tab you can set the protocol to be enabled
and also set the port. You will need to make sure that there are no other
instances using this port.
John
register previously.
I can successfully register it inside the network, i.e., from another
workstation on the network, but when I try to register via a gateway, i.e.,
over the internet I can't. I can ping the server, and the router has port
forwarding setup correctly (port 1433), I've turned off the firewall, and
nothing else has changed that I am aware of, but it just won't respond. I
am confident that the SA password is correct.
I'm stumped. I have remote users who need to access this server, but can't
get in.
Can anyone give me any suggestions. I've tried everything I can imagine.
The one change on this system is that we had to reinstall the Server, and
we've installed CA Antivirus. But I've uninstalled the CA firewall
software, and turned off the Windows Firewall (just to get this up...we had
it running before with SQL traffic allowed).
Any Ideas are welcome!!
BobHi Bob
"Bob Bartel" wrote:
> I am trying to reregister an existing server that we've been able to
> register previously.
> I can successfully register it inside the network, i.e., from another
> workstation on the network, but when I try to register via a gateway, i.e.
,
> over the internet I can't. I can ping the server, and the router has port
> forwarding setup correctly (port 1433), I've turned off the firewall, and
> nothing else has changed that I am aware of, but it just won't respond. I
> am confident that the SA password is correct.
> I'm stumped. I have remote users who need to access this server, but can'
t
> get in.
> Can anyone give me any suggestions. I've tried everything I can imagine.
> The one change on this system is that we had to reinstall the Server, and
> we've installed CA Antivirus. But I've uninstalled the CA firewall
> software, and turned off the Windows Firewall (just to get this up...we ha
d
> it running before with SQL traffic allowed).
> Any Ideas are welcome!!
> Bob
>
It would be safer to use a VPN for this rather than leaving the server open.
http://support.microsoft.com/kb/287932 describes the communication between
the client and server, make sure you are using TCP/IP protcols and the clien
t
is not blocking the returning traffic. If you have set up this correctly you
should be in-undated with people trying to hack in.
John|||As I mentioned, I have already had this working before. And only shut down
my firewall for this test. I agree a VPN is a good choice and I'll probably
turn it on, but...
But the real problem is that even with the router correctly forwarding 1433
and the firewall configured to allow the traffic, I can't register the
server remotely.
The only thing I can think of that may be effecting it is that I had to
reinstall the server. Can anyone think of anything that would keep remote
users from registering with a new install? Is there some setting on the
server that I neglected to turn back on?
Bob
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:5E55FAA1-601D-4DED-8E5C-0324E2ED46B6@.microsoft.com...
> Hi Bob
> "Bob Bartel" wrote:
>
> It would be safer to use a VPN for this rather than leaving the server
> open.
> http://support.microsoft.com/kb/287932 describes the communication between
> the client and server, make sure you are using TCP/IP protcols and the
> client
> is not blocking the returning traffic. If you have set up this correctly
> you
> should be in-undated with people trying to hack in.
> John|||Hi
"Bob Bartel" wrote:
> As I mentioned, I have already had this working before. And only shut dow
n
> my firewall for this test. I agree a VPN is a good choice and I'll probab
ly
> turn it on, but...
> But the real problem is that even with the router correctly forwarding 143
3
> and the firewall configured to allow the traffic, I can't register the
> server remotely.
> The only thing I can think of that may be effecting it is that I had to
> reinstall the server. Can anyone think of anything that would keep remote
> users from registering with a new install? Is there some setting on the
> server that I neglected to turn back on?
> Bob
>
If this is SQL Express you may not have turned on remote access. If this is
a named instance then it would not be using the default ports.
John|||Its a named instance...where to I specify the port?
bob
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:1B0EB2A5-8E12-41C2-9D87-5C38176D1783@.microsoft.com...
> Hi
> "Bob Bartel" wrote:
>
> If this is SQL Express you may not have turned on remote access. If this
> is
> a named instance then it would not be using the default ports.
> John|||Hi Bob
"Bob Bartel" wrote:
> Its a named instance...where to I specify the port?
> bob
In the SQL Server Configuration manager there will be an entry in the SQL
Server 2005 Network Configuration branch for your instance. This will shows
which protocols are installed and enabled. Right clicking TCP/IP and choosin
g
properties and on the IP Address tab you can set the protocol to be enabled
and also set the port. You will need to make sure that there are no other
instances using this port.
John
Tuesday, March 20, 2012
Problem on Connecting to SQL Server on Network thru ODBC DSN
am using Sql Server 7 as my database and it resides on a server ruinning on
Windows XP.
I have used the ODBC DSN for sql server and it worked on stand alone
perfectly but
when i tried to reconfigure the ODBC DNS for other client syustems to
connect to the SERVer it is giving me this error
Connection Failed:
SQLstate:01000
SQL Server error:10061
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionOpen (Connect())
Connection failed:
SQLstate:08001
SQL Server error: 17
[Microsoft][ODBC SQL Server DriverSQL Server does not exists or access denied.
Pls am highly frustrated and helpless, pls help me i need this thing to work
pls help me i need ur help
I have checked the Windows Firewall seetings and its even off, so what
exactly is blocking the connection or i dont know , pls just help me out.
I will be expecting ur reply earnestly
--
sammy dot comHello sammydotcom,
If you are connectin using the name of the SQL Server, make sure that Named
Pipes is turned on.
If you are connecting using an IP address, then IP access needs to be turned
on.
There should be a client tools in your SQL Server menu (off of All Programs)
that will allow you to configure the connection type. Additionaly, double
check the SQL Server setup itself and make sure that it can accept Remote
Connections.
Chris Anderson VB-MVP
> am using Sql Server 7 as my database and it resides on a server
> ruinning on
> Windows XP.
> I have used the ODBC DSN for sql server and it worked on stand alone
> perfectly but
> when i tried to reconfigure the ODBC DNS for other client syustems to
> connect to the SERVer it is giving me this error
> Connection Failed:
> SQLstate:01000
> SQL Server error:10061
> [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionOpen
> (Connect())
> Connection failed:
> SQLstate:08001
> SQL Server error: 17
> [Microsoft][ODBC SQL Server DriverSQL Server does not exists or access
> denied.
> Pls am highly frustrated and helpless, pls help me i need this thing
> to work
> pls help me i need ur help
> I have checked the Windows Firewall seetings and its even off, so what
> exactly is blocking the connection or i dont know , pls just help me
> out.
> I will be expecting ur reply earnestly
>
Windows XP.
I have used the ODBC DSN for sql server and it worked on stand alone
perfectly but
when i tried to reconfigure the ODBC DNS for other client syustems to
connect to the SERVer it is giving me this error
Connection Failed:
SQLstate:01000
SQL Server error:10061
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionOpen (Connect())
Connection failed:
SQLstate:08001
SQL Server error: 17
[Microsoft][ODBC SQL Server DriverSQL Server does not exists or access denied.
Pls am highly frustrated and helpless, pls help me i need this thing to work
pls help me i need ur help
I have checked the Windows Firewall seetings and its even off, so what
exactly is blocking the connection or i dont know , pls just help me out.
I will be expecting ur reply earnestly
--
sammy dot comHello sammydotcom,
If you are connectin using the name of the SQL Server, make sure that Named
Pipes is turned on.
If you are connecting using an IP address, then IP access needs to be turned
on.
There should be a client tools in your SQL Server menu (off of All Programs)
that will allow you to configure the connection type. Additionaly, double
check the SQL Server setup itself and make sure that it can accept Remote
Connections.
Chris Anderson VB-MVP
> am using Sql Server 7 as my database and it resides on a server
> ruinning on
> Windows XP.
> I have used the ODBC DSN for sql server and it worked on stand alone
> perfectly but
> when i tried to reconfigure the ODBC DNS for other client syustems to
> connect to the SERVer it is giving me this error
> Connection Failed:
> SQLstate:01000
> SQL Server error:10061
> [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionOpen
> (Connect())
> Connection failed:
> SQLstate:08001
> SQL Server error: 17
> [Microsoft][ODBC SQL Server DriverSQL Server does not exists or access
> denied.
> Pls am highly frustrated and helpless, pls help me i need this thing
> to work
> pls help me i need ur help
> I have checked the Windows Firewall seetings and its even off, so what
> exactly is blocking the connection or i dont know , pls just help me
> out.
> I will be expecting ur reply earnestly
>
Problem on Connecting to SQL Server on Network thru ODBC DSN
am using Sql Server 7 as my database and it resides on a server ruinning on
Windows XP.
I have used the ODBC DSN for sql server and it worked on stand alone
perfectly but
when i tried to reconfigure the ODBC DNS for other client syustems to
connect to the SERVer it is giving me this error
Connection Failed:
SQLstate:01000
SQL Server error:10061
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionOpen (Connect())
Connection failed:
SQLstate:08001
SQL Server error: 17
[Microsoft][ODBC SQL Server DriverSQL Server does not exists or access denied.
Pls am highly frustrated and helpless, pls help me i need this thing to work
pls help me i need ur help
I have checked the Windows Firewall seetings and its even off, so what
exactly is blocking the connection or i dont know , pls just help me out.
I will be expecting ur reply earnestly
sammy dot com
Hello sammydotcom,
If you are connectin using the name of the SQL Server, make sure that Named
Pipes is turned on.
If you are connecting using an IP address, then IP access needs to be turned
on.
There should be a client tools in your SQL Server menu (off of All Programs)
that will allow you to configure the connection type. Additionaly, double
check the SQL Server setup itself and make sure that it can accept Remote
Connections.
Chris Anderson VB-MVP
> am using Sql Server 7 as my database and it resides on a server
> ruinning on
> Windows XP.
> I have used the ODBC DSN for sql server and it worked on stand alone
> perfectly but
> when i tried to reconfigure the ODBC DNS for other client syustems to
> connect to the SERVer it is giving me this error
> Connection Failed:
> SQLstate:01000
> SQL Server error:10061
> [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionOpen
> (Connect())
> Connection failed:
> SQLstate:08001
> SQL Server error: 17
> [Microsoft][ODBC SQL Server DriverSQL Server does not exists or access
> denied.
> Pls am highly frustrated and helpless, pls help me i need this thing
> to work
> pls help me i need ur help
> I have checked the Windows Firewall seetings and its even off, so what
> exactly is blocking the connection or i dont know , pls just help me
> out.
> I will be expecting ur reply earnestly
>
Windows XP.
I have used the ODBC DSN for sql server and it worked on stand alone
perfectly but
when i tried to reconfigure the ODBC DNS for other client syustems to
connect to the SERVer it is giving me this error
Connection Failed:
SQLstate:01000
SQL Server error:10061
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionOpen (Connect())
Connection failed:
SQLstate:08001
SQL Server error: 17
[Microsoft][ODBC SQL Server DriverSQL Server does not exists or access denied.
Pls am highly frustrated and helpless, pls help me i need this thing to work
pls help me i need ur help
I have checked the Windows Firewall seetings and its even off, so what
exactly is blocking the connection or i dont know , pls just help me out.
I will be expecting ur reply earnestly
sammy dot com
Hello sammydotcom,
If you are connectin using the name of the SQL Server, make sure that Named
Pipes is turned on.
If you are connecting using an IP address, then IP access needs to be turned
on.
There should be a client tools in your SQL Server menu (off of All Programs)
that will allow you to configure the connection type. Additionaly, double
check the SQL Server setup itself and make sure that it can accept Remote
Connections.
Chris Anderson VB-MVP
> am using Sql Server 7 as my database and it resides on a server
> ruinning on
> Windows XP.
> I have used the ODBC DSN for sql server and it worked on stand alone
> perfectly but
> when i tried to reconfigure the ODBC DNS for other client syustems to
> connect to the SERVer it is giving me this error
> Connection Failed:
> SQLstate:01000
> SQL Server error:10061
> [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionOpen
> (Connect())
> Connection failed:
> SQLstate:08001
> SQL Server error: 17
> [Microsoft][ODBC SQL Server DriverSQL Server does not exists or access
> denied.
> Pls am highly frustrated and helpless, pls help me i need this thing
> to work
> pls help me i need ur help
> I have checked the Windows Firewall seetings and its even off, so what
> exactly is blocking the connection or i dont know , pls just help me
> out.
> I will be expecting ur reply earnestly
>
Problem on Connecting to SQL Server on Network thru ODBC DSN
am using Sql Server 7 as my database and it resides on a server ruinning on
Windows XP.
I have used the ODBC DSN for sql server and it worked on stand alone
perfectly but
when i tried to reconfigure the ODBC DNS for other client syustems to
connect to the SERVer it is giving me this error
Connection Failed:
SQLstate:01000
SQL Server error:10061
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionOpe
n (Connect())
Connection failed:
SQLstate:08001
SQL Server error: 17
[Microsoft][ODBC SQL Server DriverSQL Server does not exists or acce
ss denied.
Pls am highly frustrated and helpless, pls help me i need this thing to work
pls help me i need ur help
I have checked the Windows Firewall seetings and its even off, so what
exactly is blocking the connection or i dont know , pls just help me out.
I will be expecting ur reply earnestly
sammy dot comHello sammydotcom,
If you are connectin using the name of the SQL Server, make sure that Named
Pipes is turned on.
If you are connecting using an IP address, then IP access needs to be turned
on.
There should be a client tools in your SQL Server menu (off of All Programs)
that will allow you to configure the connection type. Additionaly, double
check the SQL Server setup itself and make sure that it can accept Remote
Connections.
Chris Anderson VB-MVP
> am using Sql Server 7 as my database and it resides on a server
> ruinning on
> Windows XP.
> I have used the ODBC DSN for sql server and it worked on stand alone
> perfectly but
> when i tried to reconfigure the ODBC DNS for other client syustems to
> connect to the SERVer it is giving me this error
> Connection Failed:
> SQLstate:01000
> SQL Server error:10061
> [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionO
pen
> (Connect())
> Connection failed:
> SQLstate:08001
> SQL Server error: 17
> [Microsoft][ODBC SQL Server DriverSQL Server does not exists or ac
cess
> denied.
> Pls am highly frustrated and helpless, pls help me i need this thing
> to work
> pls help me i need ur help
> I have checked the Windows Firewall seetings and its even off, so what
> exactly is blocking the connection or i dont know , pls just help me
> out.
> I will be expecting ur reply earnestly
>
Windows XP.
I have used the ODBC DSN for sql server and it worked on stand alone
perfectly but
when i tried to reconfigure the ODBC DNS for other client syustems to
connect to the SERVer it is giving me this error
Connection Failed:
SQLstate:01000
SQL Server error:10061
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionOpe
n (Connect())
Connection failed:
SQLstate:08001
SQL Server error: 17
[Microsoft][ODBC SQL Server DriverSQL Server does not exists or acce
ss denied.
Pls am highly frustrated and helpless, pls help me i need this thing to work
pls help me i need ur help
I have checked the Windows Firewall seetings and its even off, so what
exactly is blocking the connection or i dont know , pls just help me out.
I will be expecting ur reply earnestly
sammy dot comHello sammydotcom,
If you are connectin using the name of the SQL Server, make sure that Named
Pipes is turned on.
If you are connecting using an IP address, then IP access needs to be turned
on.
There should be a client tools in your SQL Server menu (off of All Programs)
that will allow you to configure the connection type. Additionaly, double
check the SQL Server setup itself and make sure that it can accept Remote
Connections.
Chris Anderson VB-MVP
> am using Sql Server 7 as my database and it resides on a server
> ruinning on
> Windows XP.
> I have used the ODBC DSN for sql server and it worked on stand alone
> perfectly but
> when i tried to reconfigure the ODBC DNS for other client syustems to
> connect to the SERVer it is giving me this error
> Connection Failed:
> SQLstate:01000
> SQL Server error:10061
> [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionO
pen
> (Connect())
> Connection failed:
> SQLstate:08001
> SQL Server error: 17
> [Microsoft][ODBC SQL Server DriverSQL Server does not exists or ac
cess
> denied.
> Pls am highly frustrated and helpless, pls help me i need this thing
> to work
> pls help me i need ur help
> I have checked the Windows Firewall seetings and its even off, so what
> exactly is blocking the connection or i dont know , pls just help me
> out.
> I will be expecting ur reply earnestly
>
Saturday, February 25, 2012
Problem Installing AdventureWorksDB.msi
I'm running on a stand alone machine. No network connections. I get the following error message when running this script:
"Error 1316. A network error occurred while attempting to read from the file C:\Program Files\Microsoft SQL Server\AdventureWorksDB[1].msi"
So how do I resolve this problem, so I can get the Adventure Works DB installed?
This often has to do with a failed installation from an earlier attempt. You may have to clean registry entries or edit the .msi file, but try this tool first:
http://support.microsoft.com/default.aspx?scid=kb;en-us;290301
Buck
|||Dan,
Did you get this problem solved?
Regards,
Mike Wachal
SQL Express team
-
Check out my tips for getting your answer faster and how to ask a good question: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=307712&SiteID=1
The inclusion of the [1] in the file name from the error suggests to me that the file was in a temporary directory, which would be the result of clicking Run directly from the Download page.
If this was the case, then I'd suggest trying to Save the file to your local hard drive and then run the saved file. If that is not the case, it would be worth downloading a fresh copy of the sample database from the download center. It is rare, but occationally files can be damaged during the download process.
If neither of those solve the problem, I can get the folks from the Setup group involved to see if they have better ideas than I do.
Regards,
Mike Wachal
SQL Express team
-
Check out my tips for getting your answer faster and how to ask a good question: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=307712&SiteID=1
OK Dan,
Be sure to respond back to the forum with your results as I'm sure others will be interested.
Regards,
Mike Wachal
SQL Express team
-
Check out my tips for getting your answer faster and how to ask a good question: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=307712&SiteID=1
>This often has to do with a failed installation from an earlier attempt. You may have to clean registry entries or edit the .msi file, but try this tool first:
>http://support.microsoft.com/default.aspx?scid=kb;en-us;290301
Thankyou this worked for me winxp sp2 with the error.
Problem Installing AdventureWorksDB.msi
I'm running on a stand alone machine. No network connections. I get the following error message when running this script:
"Error 1316. A network error occurred while attempting to read from the file C:\Program Files\Microsoft SQL Server\AdventureWorksDB[1].msi"
So how do I resolve this problem, so I can get the Adventure Works DB installed?
This often has to do with a failed installation from an earlier attempt. You may have to clean registry entries or edit the .msi file, but try this tool first:
http://support.microsoft.com/default.aspx?scid=kb;en-us;290301
Buck
|||Dan,
Did you get this problem solved?
Regards,
Mike Wachal
SQL Express team
-
Check out my tips for getting your answer faster and how to ask a good question: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=307712&SiteID=1
The inclusion of the [1] in the file name from the error suggests to me that the file was in a temporary directory, which would be the result of clicking Run directly from the Download page.
If this was the case, then I'd suggest trying to Save the file to your local hard drive and then run the saved file. If that is not the case, it would be worth downloading a fresh copy of the sample database from the download center. It is rare, but occationally files can be damaged during the download process.
If neither of those solve the problem, I can get the folks from the Setup group involved to see if they have better ideas than I do.
Regards,
Mike Wachal
SQL Express team
-
Check out my tips for getting your answer faster and how to ask a good question: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=307712&SiteID=1
OK Dan,
Be sure to respond back to the forum with your results as I'm sure others will be interested.
Regards,
Mike Wachal
SQL Express team
-
Check out my tips for getting your answer faster and how to ask a good question: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=307712&SiteID=1
>This often has to do with a failed installation from an earlier attempt. You may have to clean registry entries or edit the .msi file, but try this tool first:
>http://support.microsoft.com/default.aspx?scid=kb;en-us;290301
Thankyou this worked for me winxp sp2 with the error.
Subscribe to:
Posts (Atom)