Hope you help me....
Two SBS 2000's (trying to get the damn think to replicate).
BROAD has fixed IP of 81.174.xxx.xxx and CLIFT has 81.174.xxx.xxx
Broad is set as the subscriber, Clift as the distributor
Broad can ping, tracert Clift using IP and Name
ISA firewall ports open to allow traffic in/out of both servers
SQL Protocol mapped to 14446 instead of 1433.
Win XP workstation can connect via ODBC to Clift SQL Database no problems
using user sa.
BROAD cannot make connection to CLIFT via ODBC (server not found).
BROAD cannot connect to CLIFT via Client network tool or SQL Analyser?
BROAD and CLIFT router's completely open, no restrictions (for testing only)
So why can I connect using my XP workstation and not the other server?.
The CLIFT server must be OK for access because I can access the database
remotely and open it.
I cannot see any reason why i am having problems with this...
Ideas.
Many thanks
Ok, so let me get this straight. There are three machines, Broad, Clift and
your workstation.
Broad can ping clift. Your workstation can ping clift (and connect). Broad
cannot connect to clift using ODBC.
Ping means you have network connectivity. I take it you did a ping -a
81.174.xxx.xxx and ping -a clift to ensure that it is resolving to the
correct ip address. Now I think you should use ODBC ping to try to connect
to it. Also use client network utility to set up an alias to clift on broad
using the ip address and instance name, and then try again.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
""confused"" <confused@.discussions.microsoft.com> wrote in message
news:130033D1-DA47-48E6-A984-37080D4FFEBB@.microsoft.com...
> Hope you help me....
> Two SBS 2000's (trying to get the damn think to replicate).
> BROAD has fixed IP of 81.174.xxx.xxx and CLIFT has 81.174.xxx.xxx
> Broad is set as the subscriber, Clift as the distributor
> Broad can ping, tracert Clift using IP and Name
> ISA firewall ports open to allow traffic in/out of both servers
> SQL Protocol mapped to 14446 instead of 1433.
> Win XP workstation can connect via ODBC to Clift SQL Database no problems
> using user sa.
> BROAD cannot make connection to CLIFT via ODBC (server not found).
> BROAD cannot connect to CLIFT via Client network tool or SQL Analyser?
> BROAD and CLIFT router's completely open, no restrictions (for testing
> only)
> So why can I connect using my XP workstation and not the other server?.
> The CLIFT server must be OK for access because I can access the database
> remotely and open it.
> I cannot see any reason why i am having problems with this...
> Ideas.
> Many thanks
|||Hi Hilary,
odbcping works fine from an XP workstation to each server but NOT from
server to server. I can ping between servers and tracert but nothing else.
Have tried setting up alias on each server but odbcping still wont work from
server to server. Now is there any ports that need to be opened on the server
for odbcping to work? I really dont get it....
Thanks
"Hilary Cotter" wrote:
> Ok, so let me get this straight. There are three machines, Broad, Clift and
> your workstation.
> Broad can ping clift. Your workstation can ping clift (and connect). Broad
> cannot connect to clift using ODBC.
> Ping means you have network connectivity. I take it you did a ping -a
> 81.174.xxx.xxx and ping -a clift to ensure that it is resolving to the
> correct ip address. Now I think you should use ODBC ping to try to connect
> to it. Also use client network utility to set up an alias to clift on broad
> using the ip address and instance name, and then try again.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
>
> ""confused"" <confused@.discussions.microsoft.com> wrote in message
> news:130033D1-DA47-48E6-A984-37080D4FFEBB@.microsoft.com...
>
>
|||Yes, you need to open whatever port SQL Server is running on for inbound
communication. So if it is running on 1433 you need to open up port 1433 for
inbound communication.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
""confused"" <confused@.discussions.microsoft.com> wrote in message
news:5524C527-EB97-4423-BA34-6BF5E4F1B199@.microsoft.com...[vbcol=seagreen]
> Hi Hilary,
> odbcping works fine from an XP workstation to each server but NOT from
> server to server. I can ping between servers and tracert but nothing else.
> Have tried setting up alias on each server but odbcping still wont work
> from
> server to server. Now is there any ports that need to be opened on the
> server
> for odbcping to work? I really dont get it....
>
> Thanks
> "Hilary Cotter" wrote:
|||Hi,
I am using 14446 instead of 1433.
I have created packet filters (both ways with fixed IP) on both servers
I have created Protocol rules based upon that Port so there really isnt
anything stopping the comms from working.
However, I looked inside the ISA log (Firewall) and it states that port
14446 from IP 81.174.xxx.xxx is BLOCKED for some reason but I cant find
anything in the ISA console that does block it.
So as far as I can see, ISA is blocking the comms. The 14446 port is OPEN so
I really dont understand.
TIM
"Hilary Cotter" wrote:
> Yes, you need to open whatever port SQL Server is running on for inbound
> communication. So if it is running on 1433 you need to open up port 1433 for
> inbound communication.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
>
> ""confused"" <confused@.discussions.microsoft.com> wrote in message
> news:5524C527-EB97-4423-BA34-6BF5E4F1B199@.microsoft.com...
>
>
|||I think you need a networking specialist to help resolve this.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
""confused"" <confused@.discussions.microsoft.com> wrote in message
news:8B1A0BDE-375C-44EA-A6A2-B31462D028EF@.microsoft.com...[vbcol=seagreen]
> Hi,
> I am using 14446 instead of 1433.
> I have created packet filters (both ways with fixed IP) on both servers
> I have created Protocol rules based upon that Port so there really isnt
> anything stopping the comms from working.
> However, I looked inside the ISA log (Firewall) and it states that port
> 14446 from IP 81.174.xxx.xxx is BLOCKED for some reason but I cant find
> anything in the ISA console that does block it.
> So as far as I can see, ISA is blocking the comms. The 14446 port is OPEN
> so
> I really dont understand.
> TIM
> "Hilary Cotter" wrote:
|||Hip, Hip Horrrray..... I've sorted the problem at last....
As I suspected ISA was blocking the port request inbound!.
All I had to do was to set the IP Packet to accept ALL PORTS inbound. This
may well sound trivial to you all but I had no idea that the inbound call
would use a random port even though I specified a fixed port to use.
I still cant use ODBCPING but what the hell it works...
Thanks for your help Hilary as I'm sure I will need more assitance soon!.
TIM
"Hilary Cotter" wrote:
> I think you need a networking specialist to help resolve this.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
>
> ""confused"" <confused@.discussions.microsoft.com> wrote in message
> news:8B1A0BDE-375C-44EA-A6A2-B31462D028EF@.microsoft.com...
>
>
Showing posts with label sbs. Show all posts
Showing posts with label sbs. Show all posts
Sunday, February 12, 2012
Friday, February 10, 2012
Connection Problem accessing a SQL server
Hello,
I have a PC with an application using SQL on a SBS 2003 server and the SQL
database is on a SBS 2000 server. I get from the SBS 2003 server to the SBS
2000 server through a router. The IP address are non-routable so it does
not go out over the internet. When I execute the application on the SBS
2003 the first couple of screens that access the database work just fine and
the response time is good. I then try another transaction and I get the
Connection failed: SQLState '01000' SQL Server Error: 10060 followed by
Connection failed: SQLState '08001' SQL Server Error: 17. I do not have a
clue what is causing this problem nor can I find a reason. If I reply
'yes' to the connection boxes that come up on the screen eventually the
connection is re-instated and I can do a couple more transactions before the
failure occurs again. I am using ODBC to connect any help would be
appreciated. I am wondering if the topology of the network is an issue.
The sequence of events is PC --> Switch --> SBS 2003 Server --> Router -->
SBS 2000 Server --> SQL 2000. I do not think this is the problem but I
thought I mention it. I also thought about ISA but I can do the
transactions initially that must mean the ports are opened. If I direct
connect the PC to the SBS 2000 server I do not have a problem with the
transactions timing out..
Thank You,
JoeHi
You may want to look at SQL profiler to see what statements are being
executed by the SQL Server and if the statements complete after the client
has timed out. You may also want to look for blocking.
If you are getting timeout errors, have you configured the timeout? What
time does it take to timeout?
You may also want to look at the protocols you are using and try a different
one.
John
"Joe Bucar" <jbucar@.hotmail.com> wrote in message
news:uLVa%234HlFHA.1148@.TK2MSFTNGP12.phx.gbl...
> Hello,
> I have a PC with an application using SQL on a SBS 2003 server and the
> SQL database is on a SBS 2000 server. I get from the SBS 2003 server to
> the SBS 2000 server through a router. The IP address are non-routable so
> it does not go out over the internet. When I execute the application on
> the SBS 2003 the first couple of screens that access the database work
> just fine and the response time is good. I then try another transaction
> and I get the Connection failed: SQLState '01000' SQL Server Error: 10060
> followed by Connection failed: SQLState '08001' SQL Server Error: 17. I
> do not have a clue what is causing this problem nor can I find a reason.
> If I reply 'yes' to the connection boxes that come up on the screen
> eventually the connection is re-instated and I can do a couple more
> transactions before the failure occurs again. I am using ODBC to connect
> any help would be appreciated. I am wondering if the topology of the
> network is an issue. The sequence of events is PC --> Switch --> SBS 2003
> Server --> Router --> SBS 2000 Server --> SQL 2000. I do not think this
> is the problem but I thought I mention it. I also thought about ISA but I
> can do the transactions initially that must mean the ports are opened. If
> I direct connect the PC to the SBS 2000 server I do not have a problem
> with the transactions timing out..
> Thank You,
> Joe
>
I have a PC with an application using SQL on a SBS 2003 server and the SQL
database is on a SBS 2000 server. I get from the SBS 2003 server to the SBS
2000 server through a router. The IP address are non-routable so it does
not go out over the internet. When I execute the application on the SBS
2003 the first couple of screens that access the database work just fine and
the response time is good. I then try another transaction and I get the
Connection failed: SQLState '01000' SQL Server Error: 10060 followed by
Connection failed: SQLState '08001' SQL Server Error: 17. I do not have a
clue what is causing this problem nor can I find a reason. If I reply
'yes' to the connection boxes that come up on the screen eventually the
connection is re-instated and I can do a couple more transactions before the
failure occurs again. I am using ODBC to connect any help would be
appreciated. I am wondering if the topology of the network is an issue.
The sequence of events is PC --> Switch --> SBS 2003 Server --> Router -->
SBS 2000 Server --> SQL 2000. I do not think this is the problem but I
thought I mention it. I also thought about ISA but I can do the
transactions initially that must mean the ports are opened. If I direct
connect the PC to the SBS 2000 server I do not have a problem with the
transactions timing out..
Thank You,
JoeHi
You may want to look at SQL profiler to see what statements are being
executed by the SQL Server and if the statements complete after the client
has timed out. You may also want to look for blocking.
If you are getting timeout errors, have you configured the timeout? What
time does it take to timeout?
You may also want to look at the protocols you are using and try a different
one.
John
"Joe Bucar" <jbucar@.hotmail.com> wrote in message
news:uLVa%234HlFHA.1148@.TK2MSFTNGP12.phx.gbl...
> Hello,
> I have a PC with an application using SQL on a SBS 2003 server and the
> SQL database is on a SBS 2000 server. I get from the SBS 2003 server to
> the SBS 2000 server through a router. The IP address are non-routable so
> it does not go out over the internet. When I execute the application on
> the SBS 2003 the first couple of screens that access the database work
> just fine and the response time is good. I then try another transaction
> and I get the Connection failed: SQLState '01000' SQL Server Error: 10060
> followed by Connection failed: SQLState '08001' SQL Server Error: 17. I
> do not have a clue what is causing this problem nor can I find a reason.
> If I reply 'yes' to the connection boxes that come up on the screen
> eventually the connection is re-instated and I can do a couple more
> transactions before the failure occurs again. I am using ODBC to connect
> any help would be appreciated. I am wondering if the topology of the
> network is an issue. The sequence of events is PC --> Switch --> SBS 2003
> Server --> Router --> SBS 2000 Server --> SQL 2000. I do not think this
> is the problem but I thought I mention it. I also thought about ISA but I
> can do the transactions initially that must mean the ports are opened. If
> I direct connect the PC to the SBS 2000 server I do not have a problem
> with the transactions timing out..
> Thank You,
> Joe
>
Connection Problem accessing a SQL server
Hello,
I have a PC with an application using SQL on a SBS 2003 server and the SQL
database is on a SBS 2000 server. I get from the SBS 2003 server to the SBS
2000 server through a router. The IP address are non-routable so it does
not go out over the internet. When I execute the application on the SBS
2003 the first couple of screens that access the database work just fine and
the response time is good. I then try another transaction and I get the
Connection failed: SQLState '01000' SQL Server Error: 10060 followed by
Connection failed: SQLState '08001' SQL Server Error: 17. I do not have a
clue what is causing this problem nor can I find a reason. If I reply
'yes' to the connection boxes that come up on the screen eventually the
connection is re-instated and I can do a couple more transactions before the
failure occurs again. I am using ODBC to connect any help would be
appreciated. I am wondering if the topology of the network is an issue.
The sequence of events is PC --> Switch --> SBS 2003 Server --> Router -->
SBS 2000 Server --> SQL 2000. I do not think this is the problem but I
thought I mention it. I also thought about ISA but I can do the
transactions initially that must mean the ports are opened. If I direct
connect the PC to the SBS 2000 server I do not have a problem with the
transactions timing out..
Thank You,
Joe
Hi
You may want to look at SQL profiler to see what statements are being
executed by the SQL Server and if the statements complete after the client
has timed out. You may also want to look for blocking.
If you are getting timeout errors, have you configured the timeout? What
time does it take to timeout?
You may also want to look at the protocols you are using and try a different
one.
John
"Joe Bucar" <jbucar@.hotmail.com> wrote in message
news:uLVa%234HlFHA.1148@.TK2MSFTNGP12.phx.gbl...
> Hello,
> I have a PC with an application using SQL on a SBS 2003 server and the
> SQL database is on a SBS 2000 server. I get from the SBS 2003 server to
> the SBS 2000 server through a router. The IP address are non-routable so
> it does not go out over the internet. When I execute the application on
> the SBS 2003 the first couple of screens that access the database work
> just fine and the response time is good. I then try another transaction
> and I get the Connection failed: SQLState '01000' SQL Server Error: 10060
> followed by Connection failed: SQLState '08001' SQL Server Error: 17. I
> do not have a clue what is causing this problem nor can I find a reason.
> If I reply 'yes' to the connection boxes that come up on the screen
> eventually the connection is re-instated and I can do a couple more
> transactions before the failure occurs again. I am using ODBC to connect
> any help would be appreciated. I am wondering if the topology of the
> network is an issue. The sequence of events is PC --> Switch --> SBS 2003
> Server --> Router --> SBS 2000 Server --> SQL 2000. I do not think this
> is the problem but I thought I mention it. I also thought about ISA but I
> can do the transactions initially that must mean the ports are opened. If
> I direct connect the PC to the SBS 2000 server I do not have a problem
> with the transactions timing out..
> Thank You,
> Joe
>
I have a PC with an application using SQL on a SBS 2003 server and the SQL
database is on a SBS 2000 server. I get from the SBS 2003 server to the SBS
2000 server through a router. The IP address are non-routable so it does
not go out over the internet. When I execute the application on the SBS
2003 the first couple of screens that access the database work just fine and
the response time is good. I then try another transaction and I get the
Connection failed: SQLState '01000' SQL Server Error: 10060 followed by
Connection failed: SQLState '08001' SQL Server Error: 17. I do not have a
clue what is causing this problem nor can I find a reason. If I reply
'yes' to the connection boxes that come up on the screen eventually the
connection is re-instated and I can do a couple more transactions before the
failure occurs again. I am using ODBC to connect any help would be
appreciated. I am wondering if the topology of the network is an issue.
The sequence of events is PC --> Switch --> SBS 2003 Server --> Router -->
SBS 2000 Server --> SQL 2000. I do not think this is the problem but I
thought I mention it. I also thought about ISA but I can do the
transactions initially that must mean the ports are opened. If I direct
connect the PC to the SBS 2000 server I do not have a problem with the
transactions timing out..
Thank You,
Joe
Hi
You may want to look at SQL profiler to see what statements are being
executed by the SQL Server and if the statements complete after the client
has timed out. You may also want to look for blocking.
If you are getting timeout errors, have you configured the timeout? What
time does it take to timeout?
You may also want to look at the protocols you are using and try a different
one.
John
"Joe Bucar" <jbucar@.hotmail.com> wrote in message
news:uLVa%234HlFHA.1148@.TK2MSFTNGP12.phx.gbl...
> Hello,
> I have a PC with an application using SQL on a SBS 2003 server and the
> SQL database is on a SBS 2000 server. I get from the SBS 2003 server to
> the SBS 2000 server through a router. The IP address are non-routable so
> it does not go out over the internet. When I execute the application on
> the SBS 2003 the first couple of screens that access the database work
> just fine and the response time is good. I then try another transaction
> and I get the Connection failed: SQLState '01000' SQL Server Error: 10060
> followed by Connection failed: SQLState '08001' SQL Server Error: 17. I
> do not have a clue what is causing this problem nor can I find a reason.
> If I reply 'yes' to the connection boxes that come up on the screen
> eventually the connection is re-instated and I can do a couple more
> transactions before the failure occurs again. I am using ODBC to connect
> any help would be appreciated. I am wondering if the topology of the
> network is an issue. The sequence of events is PC --> Switch --> SBS 2003
> Server --> Router --> SBS 2000 Server --> SQL 2000. I do not think this
> is the problem but I thought I mention it. I also thought about ISA but I
> can do the transactions initially that must mean the ports are opened. If
> I direct connect the PC to the SBS 2000 server I do not have a problem
> with the transactions timing out..
> Thank You,
> Joe
>
Connection Problem accessing a SQL server
Hello,
I have a PC with an application using SQL on a SBS 2003 server and the SQL
database is on a SBS 2000 server. I get from the SBS 2003 server to the SBS
2000 server through a router. The IP address are non-routable so it does
not go out over the internet. When I execute the application on the SBS
2003 the first couple of screens that access the database work just fine and
the response time is good. I then try another transaction and I get the
Connection failed: SQLState '01000' SQL Server Error: 10060 followed by
Connection failed: SQLState '08001' SQL Server Error: 17. I do not have a
clue what is causing this problem nor can I find a reason. If I reply
'yes' to the connection boxes that come up on the screen eventually the
connection is re-instated and I can do a couple more transactions before the
failure occurs again. I am using ODBC to connect any help would be
appreciated. I am wondering if the topology of the network is an issue.
The sequence of events is PC --> Switch --> SBS 2003 Server --> Router -->
SBS 2000 Server --> SQL 2000. I do not think this is the problem but I
thought I mention it. I also thought about ISA but I can do the
transactions initially that must mean the ports are opened. If I direct
connect the PC to the SBS 2000 server I do not have a problem with the
transactions timing out..
Thank You,
JoeHi
You may want to look at SQL profiler to see what statements are being
executed by the SQL Server and if the statements complete after the client
has timed out. You may also want to look for blocking.
If you are getting timeout errors, have you configured the timeout? What
time does it take to timeout?
You may also want to look at the protocols you are using and try a different
one.
John
"Joe Bucar" <jbucar@.hotmail.com> wrote in message
news:uLVa%234HlFHA.1148@.TK2MSFTNGP12.phx.gbl...
> Hello,
> I have a PC with an application using SQL on a SBS 2003 server and the
> SQL database is on a SBS 2000 server. I get from the SBS 2003 server to
> the SBS 2000 server through a router. The IP address are non-routable so
> it does not go out over the internet. When I execute the application on
> the SBS 2003 the first couple of screens that access the database work
> just fine and the response time is good. I then try another transaction
> and I get the Connection failed: SQLState '01000' SQL Server Error: 10060
> followed by Connection failed: SQLState '08001' SQL Server Error: 17. I
> do not have a clue what is causing this problem nor can I find a reason.
> If I reply 'yes' to the connection boxes that come up on the screen
> eventually the connection is re-instated and I can do a couple more
> transactions before the failure occurs again. I am using ODBC to connect
> any help would be appreciated. I am wondering if the topology of the
> network is an issue. The sequence of events is PC --> Switch --> SBS 2003
> Server --> Router --> SBS 2000 Server --> SQL 2000. I do not think this
> is the problem but I thought I mention it. I also thought about ISA but I
> can do the transactions initially that must mean the ports are opened. If
> I direct connect the PC to the SBS 2000 server I do not have a problem
> with the transactions timing out..
> Thank You,
> Joe
>
I have a PC with an application using SQL on a SBS 2003 server and the SQL
database is on a SBS 2000 server. I get from the SBS 2003 server to the SBS
2000 server through a router. The IP address are non-routable so it does
not go out over the internet. When I execute the application on the SBS
2003 the first couple of screens that access the database work just fine and
the response time is good. I then try another transaction and I get the
Connection failed: SQLState '01000' SQL Server Error: 10060 followed by
Connection failed: SQLState '08001' SQL Server Error: 17. I do not have a
clue what is causing this problem nor can I find a reason. If I reply
'yes' to the connection boxes that come up on the screen eventually the
connection is re-instated and I can do a couple more transactions before the
failure occurs again. I am using ODBC to connect any help would be
appreciated. I am wondering if the topology of the network is an issue.
The sequence of events is PC --> Switch --> SBS 2003 Server --> Router -->
SBS 2000 Server --> SQL 2000. I do not think this is the problem but I
thought I mention it. I also thought about ISA but I can do the
transactions initially that must mean the ports are opened. If I direct
connect the PC to the SBS 2000 server I do not have a problem with the
transactions timing out..
Thank You,
JoeHi
You may want to look at SQL profiler to see what statements are being
executed by the SQL Server and if the statements complete after the client
has timed out. You may also want to look for blocking.
If you are getting timeout errors, have you configured the timeout? What
time does it take to timeout?
You may also want to look at the protocols you are using and try a different
one.
John
"Joe Bucar" <jbucar@.hotmail.com> wrote in message
news:uLVa%234HlFHA.1148@.TK2MSFTNGP12.phx.gbl...
> Hello,
> I have a PC with an application using SQL on a SBS 2003 server and the
> SQL database is on a SBS 2000 server. I get from the SBS 2003 server to
> the SBS 2000 server through a router. The IP address are non-routable so
> it does not go out over the internet. When I execute the application on
> the SBS 2003 the first couple of screens that access the database work
> just fine and the response time is good. I then try another transaction
> and I get the Connection failed: SQLState '01000' SQL Server Error: 10060
> followed by Connection failed: SQLState '08001' SQL Server Error: 17. I
> do not have a clue what is causing this problem nor can I find a reason.
> If I reply 'yes' to the connection boxes that come up on the screen
> eventually the connection is re-instated and I can do a couple more
> transactions before the failure occurs again. I am using ODBC to connect
> any help would be appreciated. I am wondering if the topology of the
> network is an issue. The sequence of events is PC --> Switch --> SBS 2003
> Server --> Router --> SBS 2000 Server --> SQL 2000. I do not think this
> is the problem but I thought I mention it. I also thought about ISA but I
> can do the transactions initially that must mean the ports are opened. If
> I direct connect the PC to the SBS 2000 server I do not have a problem
> with the transactions timing out..
> Thank You,
> Joe
>
Subscribe to:
Posts (Atom)