RE: Changed our IP address now SMTP is broken

["Wilt, Charles" <WiltC@xxxxxxxxxx>]

Allen,

You might want to double check this.

The errno 3421 - Address not found is the error you'd see if there was an issue.

http://www-912.ibm.com/s_dir/slkbase.nsf/1ac66549a21402188625680b0002037e/ef21aaaa623ca1498625664f004d
97ea?OpenDocument&Highlight=2,SMTP,fails

Document Description
Problem: Message TCP2074 message in posted in the QTSMTPSRVR joblog when trying to start SMTP, and
SMTP then ends abnormally.

Action Taken: Check Option 12 (CFGTCP), and record the host and domain names. Also ensure that the
host name search priority is set to *local. Then, check Option 10 (Host table) to see if the
host.domain name is defined for the IP address for the system. Modify the host table entry adding the
host.domain name, and then start SMTP (using the STRTCPSVR *SMTP command).

Also saw a PTF for v5r2....

Good Luck,
Charles


> -----Original Message-----
> From: midrange-l-bounces@xxxxxxxxxxxx 
> [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Allen
> Sent: Thursday, August 02, 2007 9:55 AM
> To: 'Midrange Systems Technical Discussion'
> Subject: RE: Changed our IP address now SMTP is broken
>
> Yes and Yes, but thanks for the suggestion
>
>
>
> -----Original Message-----
> From: midrange-l-bounces@xxxxxxxxxxxx
> [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Wilt, Charles
> Sent: Thursday, August 02, 2007 9:27 AM
> To: Midrange Systems Technical Discussion
> Subject: RE: Changed our IP address now SMTP is broken
>
> Allen,
>
> SMTP expects to be able to do a (reverse?) lookup for the 
> boxes IP address.
>
> When you changed you IP address, did you change the iSeries 
> hosts table?
>
> What about DNS servers?
>
> HTH,
> Charles
>  
>
> > -----Original Message-----
> > From: midrange-l-bounces@xxxxxxxxxxxx 
> > [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
> Allen
> > Sent: Thursday, August 02, 2007 9:13 AM
> > To: MIDRANGE-L@xxxxxxxxxxxx
> > Subject: Changed our IP address now SMTP is broken
> >
> > 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
> >
> >  
> >
> >   
> >
> >  
> >
> >  
> >
> >  
> >
> > --
> > This is the Midrange Systems Technical Discussion
> > (MIDRANGE-L) mailing list To post a message email: 
> > MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or
> change 
> > list options,
> > visit:
> http://lists.midrange.com/mailman/listinfo/midrange-l
> > or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, 
> please take 
> > a moment to review the archives at 
> > http://archive.midrange.com/midrange-l.
>
> This e-mail transmission contains information that is 
> intended to be confidential and privileged.  If you receive 
> this e-mail and you are not a named addressee you are hereby 
> notified that you are not authorized to read, print, retain, 
> copy or disseminate this communication without the consent of 
> the sender and that doing so is prohibited and may be 
> unlawful.  Please reply to the message immediately by 
> informing the sender that the message was misdirected.
> After replying, please delete and otherwise erase it and any 
> attachments from your computer system.  Your assistance in 
> correcting this error is appreciated.
>
> --
> This is the Midrange Systems Technical Discussion
> (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx To 
> subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, 
> please take a moment to review the archives at 
> http://archive.midrange.com/midrange-l.
>
>
>
> -- 
> This is the Midrange Systems Technical Discussion 
> (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.

This e-mail transmission contains information that is intended to be confidential and privileged.  If you receive this e-mail and you are not a named addressee you are hereby notified that you are not authorized to read, print, retain, copy or disseminate this communication without the consent of the sender and that doing so is prohibited and may be unlawful.  Please reply to the message immediately by informing the sender that the message was misdirected.  After replying, please delete and otherwise erase it and any attachments from your computer system.  Your assistance in correcting this error is appreciated.