Client could launch normally but failed to connect to Server when

[Mills]

Hi, everyone. Did anybody encounter this problem? I can connect the Project
2003 Pro to Project Server 2003 when in LAN. But when the client is not in
LAN, it can launch properly when logon but will fail when access to server
such as open a project which stored in server.

For instance, in LAN, I have an account with the access address
http://10.x.x.x/projectserver. And the Project 2003 Pro works perfectly.

But out of LAN, I have another account with the access address
http://211.x.x.x/projectserver. (It pass the test in the account creating)
The Project 2003 Pro works properly in the initial logon procedure but always
fails when I try to open a project in server or any other access to the
server. And have an error message below


Connection failed:
SQLState: '01000'
SQL Server Error: 53
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (Connect())
Connection failed:
SQLState '08001'
SQL Server Error: 17
[Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or
access denied.

I tried to solve this problem by change some parameters，and after that
error: 53 may change to error: 10060 in some cases but generally it's 53.

Is this related to the parameters in IIS setting? Which IP should I fill in
the properties in the web server in IIS? 10.x.x.x or 211.x.x.x?

I also tried the tools such as ConInfo and EditSite that downloaded from MS
website. When I fill the IP 10.x.x.x to the EditSite, the test works
properly. If the address is 211.x.x.x, the test fail. Which IP is right in
EditSite?


Now I can use Web Access from both inside LAN and outside LAN. The Project
2003 Pro also works perfectly in LAN. Outside LAN, the Project 2003 Pro can
only launch properly but will pop the error infomation above when access to
server.

Any one can help on this? Thanks in advance.

 

[Gary L. Chefetz [MVP]]

Mills:

The Project client makes a direct ODBC connection to the database through
port 1433. This is no doubt closed to the Internet in your system and
something you don't want to expose unless you open it to a VPN tunnel. this
version does not perform well across the Internet unless your projects are
small and your bandwidth is fairly decent.

 

[Mills]

Thanks Gary. It looks like I need to do some compromise between security and
application.

Further questions. And I have used those commands below outside the LAN to
test the port 1433:
1, Click Start
2, Run
3, Enter cmd
4, Enter telnet 211.x.x.x 1433
The response told me the connection failed as you told me(Thanks again .
If this 1433 port in Project Server is closed, how could I connect to it
succesfully when I was in the same LAN with the server? Should it be not
connected from the client Project 2003 Pro neither I was inside nor outside
the LAN? Does it mean if I am in the same LAN of the server, I will be able
to connect to it form the client no matter the port 1433 is closed? I am a
little confused.

(By the way, I also test those commands to port 80 for http and 21 for ftp
services. They both passed. And I can be sure of that there is no problem
with 80 cuz I can use the web access from both outside and inside. I may have
a look on the ftp tomorrow because I remembered I have closed the Serv-U in
the server. How could I still received the connecting response? Maybe the
Serv-U is closed but port 21 is still open. Is it possible?)

Another possibility is that there is a firewall between the server and I
when I am outside? It filters the request from outside access to 1433 even
the server 1433 port is open , so I receive a failed reponse. When I am
inside, there is no bar between server and I, so I can connect to server
perfectly.

Finally, What shall I do now? Open the 1433 port in the server (if it is not
open) must be the first step. And set the firewall do nothing to access to
1433 if the firewall does exist?

Thanks in advance, Gary.

Mills:

The Project client makes a direct ODBC connection to the database through
port 1433. This is no doubt closed to the Internet in your system and
something you don't want to expose unless you open it to a VPN tunnel. this
version does not perform well across the Internet unless your projects are
small and your bandwidth is fairly decent.

Hi, everyone. Did anybody encounter this problem? I can connect the
Project
2003 Pro to Project Server 2003 when in LAN. But when the client is not in
LAN, it can launch properly when logon but will fail when access to server
such as open a project which stored in server.

For instance, in LAN, I have an account with the access address
http://10.x.x.x/projectserver. And the Project 2003 Pro works perfectly.

But out of LAN, I have another account with the access address
http://211.x.x.x/projectserver. (It pass the test in the account creating)
The Project 2003 Pro works properly in the initial logon procedure but
always
fails when I try to open a project in server or any other access to the
server. And have an error message below


Connection failed:
SQLState: '01000'
SQL Server Error: 53
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (Connect())
Connection failed:
SQLState '08001'
SQL Server Error: 17
[Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or
access denied.

I tried to solve this problem by change some parameters,and after that
error: 53 may change to error: 10060 in some cases but generally it's 53.

Is this related to the parameters in IIS setting? Which IP should I fill
in
the properties in the web server in IIS? 10.x.x.x or 211.x.x.x?

I also tried the tools such as ConInfo and EditSite that downloaded from
MS
website. When I fill the IP 10.x.x.x to the EditSite, the test works
properly. If the address is 211.x.x.x, the test fail. Which IP is right in
EditSite?


Now I can use Web Access from both inside LAN and outside LAN. The Project
2003 Pro also works perfectly in LAN. Outside LAN, the Project 2003 Pro
can
only launch properly but will pop the error infomation above when access
to
server.

Any one can help on this? Thanks in advance.

 

[Gary L. Chefetz [MVP]]

Mills:

Most lan managers close this port facing the Internet, but not facing the
Intranet, although that happens from time to time, too! Your next step is to
architect a secure approach for external access. Consider using a remote
desktop connection.

Thanks Gary. It looks like I need to do some compromise between security
and
application.

Further questions. And I have used those commands below outside the LAN
to
test the port 1433:
1, Click Start
2, Run
3, Enter cmd
4, Enter telnet 211.x.x.x 1433
The response told me the connection failed as you told me(Thanks again .
If this 1433 port in Project Server is closed, how could I connect to it
succesfully when I was in the same LAN with the server? Should it be not
connected from the client Project 2003 Pro neither I was inside nor
outside
the LAN? Does it mean if I am in the same LAN of the server, I will be
able
to connect to it form the client no matter the port 1433 is closed? I am a
little confused.

(By the way, I also test those commands to port 80 for http and 21 for ftp
services. They both passed. And I can be sure of that there is no problem
with 80 cuz I can use the web access from both outside and inside. I may
have
a look on the ftp tomorrow because I remembered I have closed the Serv-U
in
the server. How could I still received the connecting response? Maybe the
Serv-U is closed but port 21 is still open. Is it possible?)

Another possibility is that there is a firewall between the server and I
when I am outside? It filters the request from outside access to 1433 even
the server 1433 port is open , so I receive a failed reponse. When I am
inside, there is no bar between server and I, so I can connect to server
perfectly.

Finally, What shall I do now? Open the 1433 port in the server (if it is
not
open) must be the first step. And set the firewall do nothing to access to
1433 if the firewall does exist?

Thanks in advance, Gary.

Mills:

The Project client makes a direct ODBC connection to the database through
port 1433. This is no doubt closed to the Internet in your system and
something you don't want to expose unless you open it to a VPN tunnel.
this
version does not perform well across the Internet unless your projects
are
small and your bandwidth is fairly decent.

Hi, everyone. Did anybody encounter this problem? I can connect the
Project
2003 Pro to Project Server 2003 when in LAN. But when the client is not
in
LAN, it can launch properly when logon but will fail when access to
server
such as open a project which stored in server.

For instance, in LAN, I have an account with the access address
http://10.x.x.x/projectserver. And the Project 2003 Pro works
perfectly.

But out of LAN, I have another account with the access address
http://211.x.x.x/projectserver. (It pass the test in the account
creating)
The Project 2003 Pro works properly in the initial logon procedure but
always
fails when I try to open a project in server or any other access to the
server. And have an error message below


Connection failed:
SQLState: '01000'
SQL Server Error: 53
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (Connect())
Connection failed:
SQLState '08001'
SQL Server Error: 17
[Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist
or
access denied.

I tried to solve this problem by change some parameters,and after that
error: 53 may change to error: 10060 in some cases but generally it's
53.

Is this related to the parameters in IIS setting? Which IP should I
fill
in
the properties in the web server in IIS? 10.x.x.x or 211.x.x.x?

I also tried the tools such as ConInfo and EditSite that downloaded
from
MS
website. When I fill the IP 10.x.x.x to the EditSite, the test works
properly. If the address is 211.x.x.x, the test fail. Which IP is right
in
EditSite?


Now I can use Web Access from both inside LAN and outside LAN. The
Project
2003 Pro also works perfectly in LAN. Outside LAN, the Project 2003 Pro
can
only launch properly but will pop the error infomation above when
access
to
server.

Any one can help on this? Thanks in advance.