By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
438,590 Members | 2,174 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 438,590 IT Pros & Developers. It's quick & easy.

Problem connecting from AIX to Windows.

P: n/a
Folks,

I installed DB2 UDB 8.2 FP8 ESE on Win 2K syatem. I cataloged node
and database on AIX system. When I try to connect to the database on
windows system from an AIX system I get following error:

# db2 connect to a2local
SQL30081N A communication error has been detected. Communication protocol
being used: "TCP/IP". Communication API being used: "SOCKETS". Location
where the error was detected: "10.90.10.219". Communication function
detecting the error: "recv". Protocol specific error code(s): "10054", "*",
"0". SQLSTATE=08001

Error 10054 is the code from WSAGetLastError(), which means connection
reset by peer.

How do I connect to the database on windows system from a AIX/Unix system?

I have always worked with DB2 on AIX/Linux systems, this is the first time
I am working with DB2 on windows system.


--
Hemant Shah /"\ ASCII ribbon campaign
E-mail: No************@xnet.com \ / ---------------------
X against HTML mail
TO REPLY, REMOVE NoJunkMail / \ and postings
FROM MY E-MAIL ADDRESS.
-----------------[DO NOT SEND UNSOLICITED BULK E-MAIL]------------------
I haven't lost my mind, Above opinions are mine only.
it's backed up on tape somewhere. Others can have their own.
Nov 12 '05 #1
Share this Question
Share on Google+
14 Replies


P: n/a
Check the configuration of Your DB2 Server on Windows.
What is you Catalog Command from AIX
Communication Error means AIX cannot Reach Windows on DB2 Port

Nov 12 '05 #2

P: n/a
While stranded on information super highway sh*******@gmail.com wrote:
Check the configuration of Your DB2 Server on Windows.
What is you Catalog Command from AIX
Communication Error means AIX cannot Reach Windows on DB2 Port
I am new to windows, how do I check it.

When I get database manager config the service name is db2c_db. How do I fidn
out which port is it using?

I search google and found that it might be 50001, so that is what I used
in to catalog node.

It looks like DB2 on AIX is able to connect to DB2 on windows because the
error code is from WASGetLAstError().


--
Hemant Shah /"\ ASCII ribbon campaign
E-mail: No************@xnet.com \ / ---------------------
X against HTML mail
TO REPLY, REMOVE NoJunkMail / \ and postings
FROM MY E-MAIL ADDRESS.
-----------------[DO NOT SEND UNSOLICITED BULK E-MAIL]------------------
I haven't lost my mind, Above opinions are mine only.
it's backed up on tape somewhere. Others can have their own.
Nov 12 '05 #3

P: n/a
Use netstat -an in the windows machine and see what port the DB2
actually is waiting for. I guess its 50000. You can also see the port
used by db2 in the file C:\WINDOWS\system32\drivers\etc\services
(replace the directory structure accordingly)
Check if there is any firewall protecting ur windows system.
Correct me if iam wrong. Keep posting.

Cheers,
Thiru
WantedToBeDBA
WantedToBeDBA at gmail dot com

Nov 12 '05 #4

P: n/a
While stranded on information super highway Thiru wrote:
Use netstat -an in the windows machine and see what port the DB2
actually is waiting for. I guess its 50000. You can also see the port
used by db2 in the file C:\WINDOWS\system32\drivers\etc\services
Thanks. This is the file I was looking for. I did not know where windows
kept it.
(replace the directory structure accordingly)
Check if there is any firewall protecting ur windows system.
Correct me if iam wrong. Keep posting.

Cheers,
Thiru
WantedToBeDBA
WantedToBeDBA at gmail dot com


--
Hemant Shah /"\ ASCII ribbon campaign
E-mail: No************@xnet.com \ / ---------------------
X against HTML mail
TO REPLY, REMOVE NoJunkMail / \ and postings
FROM MY E-MAIL ADDRESS.
-----------------[DO NOT SEND UNSOLICITED BULK E-MAIL]------------------
I haven't lost my mind, Above opinions are mine only.
it's backed up on tape somewhere. Others can have their own.
Nov 12 '05 #5

P: n/a
What if both aix and windows are using the same port? We have the same
ports(defaults) and unable to catalog win db from aix.

Should we also create an entry in /etc/services in AIX DB2 pointing to
Windows DB2's port?

Nov 12 '05 #6

P: n/a
In article <11**********************@o13g2000cwo.googlegroups .com>,
(hi****@gmail.com) says...
What if both aix and windows are using the same port? We have the same
ports(defaults) and unable to catalog win db from aix.

Should we also create an entry in /etc/services in AIX DB2 pointing to
Windows DB2's port?


You don't need to add entries to the services file. Just use the port
number with the catalog command and it will work also.
Something like:
db2 catalog tcpip node db2node remote remoteserver server 50000

On a lot of servers the port number is never changed. Even if it is
changed you still need to stop/start the instance before the change
is active so changing the dbm cfg is just as easy as changing the
services file.
Nov 12 '05 #7

P: n/a
hi****@gmail.com wrote:
What if both aix and windows are using the same port?


That's no problem because the connection is identified by the IP-address
combined with the port number.

--
Knut Stolze
Information Integration
IBM Germany / University of Jena
Nov 12 '05 #8

P: n/a
On aix server, I get the following error:

I tried 1 or 2 then 3 and 4-still error:
1) db2 catalog tcpip node wnode remote er***@adamserv.com server 50000
remote_instance DB2 system miswin ostype aix
--ostype windows gives an error

2)db2 catalog tcpip node wnode remote er***@adamserv.com server 50000

SQL1336N The remote host "er***@adamserv.com" was not found

Node 2 entry:

Node name = WNODE
Comment =
Directory entry type = LOCAL
Protocol = TCPIP
Hostname = er***@adamserv.com
Service name = 50000

3. db2 catalog database orders as advord at wnode

4. db2 connect to advord

--gives eror : SQL1336N The remote host "SQL1336N The remote host
"er***@adamserv.com" was not found
I am able to ftp to that server er***@adamserv.com

Thanks....

Knut Stolze wrote:
hi****@gmail.com wrote:
What if both aix and windows are using the same port?
That's no problem because the connection is identified by the

IP-address combined with the port number.

--
Knut Stolze
Information Integration
IBM Germany / University of Jena


Nov 12 '05 #9

P: n/a
hi****@gmail.com wrote:
On aix server, I get the following error:

I tried 1 or 2 then 3 and 4-still error:
1) db2 catalog tcpip node wnode remote er***@adamserv.com server 50000
"er***@adamserv.com" is definitively not a correct host name. Maybe you
just meant to say "adamserv.com"?
remote_instance DB2 system miswin ostype aix
--ostype windows gives an error


What kind of error?
If the remote system is Windows, you shouldn't say it's AIX.

I recommend that you try to do those steps via the control center. If the
admin server is running and discovery is not disabled, you simply have to
click your way through...

--
Knut Stolze
Information Integration
IBM Germany / University of Jena
Nov 12 '05 #10

P: n/a
No problems while cataloging with the control center. Only while I do
it with the telnet session on the aix server to windows. If I mention
ostype to be windows, it errors expecting it to be 'aix'.
Wondering why the telnet session does not recognize what
windows/control center could.

Thanks Knut!!

Nov 12 '05 #11

P: n/a
hi****@gmail.com wrote:
No problems while cataloging with the control center. Only while I do
it with the telnet session on the aix server to windows. If I mention
ostype to be windows, it errors expecting it to be 'aix'.
As I said, the exact error message would be helpful.

In any case, you have to specify "OSTYPE WIN" if the remote system is a
Windows server.
Wondering why the telnet session does not recognize what
windows/control center could.


In the Control Center you have usually a button labeled "Show Command".
Clicking on that gives you the exact command that you can also execute from
the command line.

--
Knut Stolze
Information Integration
IBM Germany / University of Jena
Nov 12 '05 #12

P: n/a
Knut Stolze wrote:
In any case, you have to specify "OSTYPE WIN" if the remote system is a
Windows server.


Btw: this is in the docs:
http://publib.boulder.ibm.com/infoce...e/r0001944.htm

--
Knut Stolze
Information Integration
IBM Germany / University of Jena
Nov 12 '05 #13

P: n/a
The error you are getting means that it can't find the hostname (
er***@adamserv.com) specified with the SERVER parm. of your command.
Whatever value you put must resolve to the IP address of the target Win box
where your server is.
Possible entries:
somehostname Make sure you have an entry in your host file (same location
as services but on your system).
somehostname The entry can be resolved by A DNS if you are using one.
126.171.16.112 The actual IP address of the targer server I don't recommend
that as your displays don't look nice.
HTH, Pierre.

--
Pierre Saint-Jacques
SES Consultants Inc.
514-737-4515
<hi****@gmail.com> a écrit dans le message de news:
11*********************@z14g2000cwz.googlegroups.c om...
On aix server, I get the following error:

I tried 1 or 2 then 3 and 4-still error:
1) db2 catalog tcpip node wnode remote er***@adamserv.com server 50000
remote_instance DB2 system miswin ostype aix
--ostype windows gives an error

2)db2 catalog tcpip node wnode remote er***@adamserv.com server 50000

SQL1336N The remote host "er***@adamserv.com" was not found

Node 2 entry:

Node name = WNODE
Comment =
Directory entry type = LOCAL
Protocol = TCPIP
Hostname = er***@adamserv.com
Service name = 50000

3. db2 catalog database orders as advord at wnode

4. db2 connect to advord

--gives eror : SQL1336N The remote host "SQL1336N The remote host
"er***@adamserv.com" was not found
I am able to ftp to that server er***@adamserv.com

Thanks....

Knut Stolze wrote:
hi****@gmail.com wrote:
> What if both aix and windows are using the same port?


That's no problem because the connection is identified by the

IP-address
combined with the port number.

--
Knut Stolze
Information Integration
IBM Germany / University of Jena


Nov 12 '05 #14

P: n/a
On Aix, I typed:

1) db2 catalog tcpip node wnode remote 165.32.4.31 server 50000
remote_instance DB2 ostype win
--success
2)db2 catalog database orders as advord at node wnode authentication
server
--success
3) db2 connect to advord user winuser using winpwd
--success
Thanks to Knut and Pierre.

Nov 12 '05 #15

This discussion thread is closed

Replies have been disabled for this discussion.