|
HELP, I've pulled my hair out over this (:-| and worn the softcopy/infocenter cd to a blob of plastic. I am trying to setup a dial in to an AS/400. The modems connect and the PC indicates it is verifying user and password but then disconnects. The message usually says that the dialed into system could not establish a dial up connection. The printer output for the profile job shows: 0:22:33.522 === Incoming call received. 0:22:33.526 === Establishing point-to-point connection for profile DIAL_IN01. 0:22:36.330 === NOTE: REJECTED LCP OPTION 0D (lcp_rcvreqci) 0:22:40.230 === WARNING: OS/400 REJECTS PEER ADDRESS '0.0.0.0'. (NO ALTERNATE ADDRESS FOR PEER AVAILABLE 0:22:40.244 <== NOTE: NO SUPPORT IN OS/400 FOR PROTOCOL 80FD, STREAM LCP 0:22:44.085 === Status code X'54001490' from device PPPINTCP. 0:22:44.912 === Status code X'54001490' from device PPPINTCP. 0:22:45.656 === WARNING: LINK DOWN] ERRNO ENETDOWN(3433) 0:22:45.659 === NOTE: LCP_ADMIN_CLOSE: REASON 9 CALL ENDED (LINE DROPPED). 0:22:45.660 === WARNING: LCP: IGNORING unexpected RCVTERMREQ event in INITIAL state. 0:22:48.427 === Message received for Point-to-Point Profile DIAL_IN01, Reason Code 1. 0:22:48.557 === Attempting modem dial/answer. 0:22:48.558 ==> ATS0=1 0:22:49.087 <== OK 0:22:49.088 === Waiting for incoming call. or 0:30:29.383 === Incoming call received. 0:30:29.453 === Establishing point-to-point connection for profile DIAL_IN01. 0:30:32.188 === NOTE: REJECTED LCP OPTION 0D (lcp_rcvreqci) 0:30:34.418 === NOTE: CHAP VERIFY failed. *VLDL PPPIN01 ENTRY NOT FOUND. (rc 10) 0:30:34.433 === NOTE: LCP_ADMIN_CLOSE: REASON 2 AS/400 WAS UNABLE TO AUTHENTICATE THE REMOTE PEER. 0:30:35.507 === Status code X'54001490' from device PPPINTCP. 0:30:36.320 === Status code X'54001490' from device PPPINTCP. 0:30:39.946 === Message received for Point-to-Point Profile DIAL_IN01, Reason Code 1. 0:30:40.076 === Attempting modem dial/answer. 0:30:40.077 ==> ATS0=1 0:30:40.606 <== OK 0:30:40.711 === Waiting for incoming call. The only way I've been able to get a connection is to remove the REMOTE REQUIRED SYSTEM IDENTIFICATION. I don't want to run this way without security to restrict who can get access to the line, I know that the rest of the system depends on object/IFS security. BTW. Is there a way to have the validation list automatically updated to be the same as the AS/400 user profiles? Is there a way to have the connection profile automatically started at IPL? Thanks to all and to all a productive new year. Roger Vicker, CCP ******* SETUPS ******* AS/400 is running DHCP 10.0.0.30 to 10.0.0.254 subnet 255.255.255.0 but no DNS Is on an ethernet lan (10.0.0.1 mask 255.255.255.0) @ V4R4M0 AS/400 Connections Profile Setup via OpsNav General Type PPP Line Switched TCP/IP Local IP 10.0.0.1 (same as the Ethernet card for LAN) Remote Dynamically Assign Routing Allow IP Forward Routing Request header compression (VJ) Authentication Remote Require remote sys ID Remote Allow PAP Remote Validation list (has names as PAP only) Local (not checked for enable local sys id) PC Dial up @ Win98 Server types Type of server: PPP: Internet, Windows NT Server, Windows 98 Log on to network Enable software compression Require encrypted password TCP/IP Server assigned IP Server assigned name server addresses use IP header compression use default gaeway on remote network -- *** Vicker Programming and Service *** Have bits will byte *** www.vicker.com *** Fine day for a good workout. Steal something heavy. +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
As an Amazon Associate we earn from qualifying purchases.
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.