× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Double check to see that you changed the CFGTCP option 10 for your system's IP address.

Bryan



Allen said the following on 8/2/2007 9:12 AM:
While setting up VPN on our network we had to change the IP
address of our AS400 (V5R1) from 192.168.1.50 to
192.168.2.50


Everything appears to be back up and working (Users can log
on, map drives etc) except for SMTP

SMTP will start up (jobs QTSMTPBRCL QTSMTPBRSR QTSMTPCLTD
QTSMTPSRVD) they stay running for about 5 minutes


Then they end with the following in the joblog:

TCP206E Diagnostic 40 08/02/07 08:39:56
QTMSCLCD QTCP *STMT QTMSCLCD QTCP
From module . . . . . .
. . : QTMSCLUT
From procedure . . . .
. . : PostTCP206E__FiPc
Statement . . . . . . .
. . : 625
To module . . . . . . .
. . : QTMSCLCD
To procedure . . . . .
. . : main
Statement . . . . . . .
. . : 275
Message . . . . :
SMTP received an error from a sockets function.
Cause . . . . . :
Probable causes are: -- network problem -- remote host
problem Technical
description . . . . . . . . : SMTP received errno 3421
from sockets function
BIND(). To see the meaning of the errno, enter command
DSPMSGD
RANGE(CPEXXXX), where XXXX is the four digit errno value.



TCP2081 Diagnostic 20 08/02/07 08:39:56
QTMSUTL QTCP *STMT QTMSCLCD QTCP
*STMT
From module . . . . .
. . . : QTMSUTIL


From procedure . . .
. . . : qtms_IssueMessage


Statement . . . . . .
. . . : 1747


To module . . . . . .
. . . : QTMSCLCD


To procedure . . . .
. . . : main


Statement . . . . . .
. . . : 276


Message . . . . :
SMTP unable to bind to Internet Protocol interface


192.168.1.50.


Recovery . . . :
Check the status of Internet Protocol interface


192.168.1.50 with
the command NETSTAT *IFC, and start if necessary, or


correct problems.



When I run the command NETSTAT *IFC is shows our new IP
address 192.168.2.50 not the 192.168.1.50 that is shown in
the message above from the joblog

So something somewhere still has our old IP address

Any ideas would be greatly appreciated


John







As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.