Home > Archive > SQL Anywhere database > December 2005 > Connection to ASA 9.02.3131 Problem









You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

 

Author Connection to ASA 9.02.3131 Problem
Ignacio Mateos

2005-12-20, 8:24 pm

HI:

I start a server (with dbsrv9.exe) on a Windows XP professional, it starts,
it opens TCPIP and says it accepts connections, now,

I can connect from the same PC

I cannot connect from another PC on the same Network.

With Tcpview, I see the connection is established, and almost immediately it
goes into Close.

The server window says nothing (even with -z option), the client stops after
2 minutes with the message "server found but communication error..."

DBPING and DBLOCATE don't seem to find the server.

The same behaviour in another PC in the same network

The network is a Workgroup, no domain or domain controller.

WHAT ELSE CAN I DO TO FIGURE OUT WHAT MAY BE HAPPENING?


Joshua Savill

2005-12-20, 8:24 pm

Can you ping the physical machine running the database server? If so, then
try specifying on the connection string HOST=xxx.xxx.xx.xx;PORT=xxxx

Are there any routers that block ports on your network?

--
Joshua Savill
iAnywhere Solutions - Product Support Analyst

"Ignacio Mateos" <imateos@telefonica.net> wrote in message
news:43a86b25@forums
-2-dub...
> HI:
>
> I start a server (with dbsrv9.exe) on a Windows XP professional, it
> starts, it opens TCPIP and says it accepts connections, now,
>
> I can connect from the same PC
>
> I cannot connect from another PC on the same Network.
>
> With Tcpview, I see the connection is established, and almost immediately
> it goes into Close.
>
> The server window says nothing (even with -z option), the client stops
> after 2 minutes with the message "server found but communication error..."
>
> DBPING and DBLOCATE don't seem to find the server.
>
> The same behaviour in another PC in the same network
>
> The network is a Workgroup, no domain or domain controller.
>
> WHAT ELSE CAN I DO TO FIGURE OUT WHAT MAY BE HAPPENING?
>



David Kerber

2005-12-20, 8:24 pm

Is your windows firewall enabled on either the server or the client? If
so, try temporarily disabling it to see if that corrects the problem...



In article <43a86b25@forums-2-dub>, imateos@telefonica.net says...
> HI:
>
> I start a server (with dbsrv9.exe) on a Windows XP professional, it starts,
> it opens TCPIP and says it accepts connections, now,
>
> I can connect from the same PC
>
> I cannot connect from another PC on the same Network.
>
> With Tcpview, I see the connection is established, and almost immediately it
> goes into Close.
>
> The server window says nothing (even with -z option), the client stops after
> 2 minutes with the message "server found but communication error..."
>
> DBPING and DBLOCATE don't seem to find the server.
>
> The same behaviour in another PC in the same network
>
> The network is a Workgroup, no domain or domain controller.
>
> WHAT ELSE CAN I DO TO FIGURE OUT WHAT MAY BE HAPPENING?
>
>
>


--
Remove the ns_ from if replying by e-mail (but keep posts in the
newsgroups if possible).
Ignacio Mateos

2005-12-21, 1:23 pm

Hi, thank you for answering, no, it is not a firewall problem.

I am actually testing it on the same machine and I cannot get a TCP
connection, I can get a shared connection, but not a TCP, not event in the
same machine.

Regards

"David Kerber" < ns_dkerber@ns_wraenv
iro.com> escribió en el mensaje
news:MPG. 1e12368457f1748d9897
c9@forums.sybase.com...
> Is your windows firewall enabled on either the server or the client? If
> so, try temporarily disabling it to see if that corrects the problem...
>
>
>
> In article <43a86b25@forums-2-dub>, imateos@telefonica.net says...
>
> --
> Remove the ns_ from if replying by e-mail (but keep posts in the
> newsgroups if possible).



Pavel Karady

2005-12-22, 9:23 am

Maybe your database is running using dbengX.exe instead of dbsrvX.exe?

Pavel

"Ignacio Mateos" <imateos@telefonica.net> wrote in message
news:43a99079@forums
-2-dub...
> Hi, thank you for answering, no, it is not a firewall problem.
>
> I am actually testing it on the same machine and I cannot get a TCP
> connection, I can get a shared connection, but not a TCP, not event in the
> same machine.
>
> Regards
>
> "David Kerber" < ns_dkerber@ns_wraenv
iro.com> escribió en el mensaje
> news:MPG. 1e12368457f1748d9897
c9@forums.sybase.com...
>
>



Greg Fenton

2005-12-23, 11:23 am

Ignacio Mateos wrote:
>
> I am actually testing it on the same machine and I cannot get a TCP
> connection, I can get a shared connection, but not a TCP, not event in the
> same machine.
>


Show us the startup command line (as Pavel is hinting at).

You might try adding the following:

-o c:/asa_console.txt -z

Then after the server is up and running, take a look at the information
in c:/asa_console.txt. If you aren't sure what is in there, post the file.

You can also get some verbose information on the client attempt to
connect using something like:

dbping -d -c " uid=dba;pwd=sql;eng=
MY_ENGINE;LOG=c:/asa_connect.txt"

and look at c:/asa_connect.txt after the connection attempt.

Hope this helps,
greg.fenton
--
Greg Fenton
Consultant, Solution Services, iAnywhere Solutions
--------
Visit the iAnywhere Solutions Developer Community
Whitepapers, TechDocs, Downloads
http://www.ianywhere.com/developer/
Ignacio Mateos

2005-12-23, 1:23 pm

Great idea the Log in the dbping. I did not know that is available, and the
server was not logging anything.

Anyway, I have found the problem and it has to do with the Personal Firewall
of McAfee.

It took me a lot to figure this one out because I was deactivating the
Firewall, but even then, the mere fact that this personal firewall is
installed, makes it impossible to open a TCP connection to ASA, even in the
same machine.

I had never had any problems with McAfee but I was using Viruscan Enterprise
8.0 until now.

Thanks to all that helped.


"Greg Fenton" <greg. fenton_NOSPAM_@ianyw
here.com> escribió en el mensaje
news:43ac2fc8$1@foru
ms-1-dub...
> Ignacio Mateos wrote:
>
> Show us the startup command line (as Pavel is hinting at).
>
> You might try adding the following:
>
> -o c:/asa_console.txt -z
>
> Then after the server is up and running, take a look at the information in
> c:/asa_console.txt. If you aren't sure what is in there, post the file.
>
> You can also get some verbose information on the client attempt to connect
> using something like:
>
> dbping -d -c " uid=dba;pwd=sql;eng=
MY_ENGINE;LOG=c:/asa_connect.txt"
>
> and look at c:/asa_connect.txt after the connection attempt.
>
> Hope this helps,
> greg.fenton
> --
> Greg Fenton
> Consultant, Solution Services, iAnywhere Solutions
> --------
> Visit the iAnywhere Solutions Developer Community
> Whitepapers, TechDocs, Downloads
> http://www.ianywhere.com/developer/



Sponsored Links





Also available: Server administration forum archive | Web Design forum archive | Software forum archive | Hardware reviews archive | Programming forum archive

Copyright 2008 droptable.com