Is it possible the IP numbers in your domain are not unique? When I telnet to the address you provided I get a JetDirect Printer. > Firmware Rev. : G.07.17 MAC Address : 08:00:09:c5:9f:91 Config By : USER SPECIFIED IP Address : 126.96.36.199 Subnet Mask : 255.255.255.0 Default Gateway : 188.8.131.52 Syslog Server : Not Specified Idle Timeout : 90 Seconds Set Cmnty Name : Not Specified Host Name : NPIC59F91 DHCP Config : Disabled Passwd : Disabled IPX/SPX : Enabled DLC/LLC : Enabled Ethertalk : Enabled Banner page : Enabled --------------------------------------------------------- Booth Martin http://www.MartinVT.com Booth@MartinVT.com --------------------------------------------------------- -------Original Message------- From: email@example.com Date: Wednesday, December 05, 2001 08:53:31 AM To: firstname.lastname@example.org Subject: Re: management Central Tom, I hope this comes thru so you can read it. this is a copy of the screen. Change TCP/IP Domain (CHGTCPDMN) Type choices, press Enter. Host name . . . . . . . . . . . 'ISD43750' Domain name . . . . . . . . . . 'INTERBORO.K12.PA.US' Domain search list . . . . . . . *DFT Host name search priority . . . *REMOTE *REMOTE, *LOCAL, *SAME Domain name server: Internet address . . . . . . . '184.108.40.206' More... F3ï4F24Yes, the name of the 400 is ISD43750. The 400 is not "seeable" on the outside, and to connect to it in the district we use 10.60.10.3 . Should I change the *remote to the actual 10.60.10.3 number? >>> email@example.com 12/04/01 07:49PM >>> MaryLou: Management Central (MGTC) seems very touchy about TCP/IP configuration. It apparently wants things to be exactly correct and isn't very forgiving when common variations are used. The single biggest item seems to be the relationship between the iSeries host/domain setting and the entry for the system in the host table (or possibly the appropriate DNS entry). >From option 12 (Change TCP/IP domain information) of the CFGTCP menu, note the fully qualified name of your system (e.g., as400host.domainname.com). Then check option 10 (Work with TCP/IP host table entries) and look at the entry for your system's IP address. The host table entry allows multiple host names to be associated with an IP address. People often put in both as400host and as400host.domainname.com as alternative names. There's nothing exactly wrong with this, but it seems to be a problem for MGTC and maybe one or two other server applications. The problem seems to be that MGTC looks only at the first host name specified for each IP address to see if it's the entry for the configured qualified host name. It doesn't recognize any aliases. So make certain that as400host.domainname.com is the first one for your IP address. If you also want to use as400host, just make sure it comes second or later. The entry would look similar to: 10.0.1.2 as400host.domainname.com as400host I'm not sure if TCP/IP _must_ be ended and restarted before MGTC will see this change, but MGTC won't run without this setting. And note that all of this is guesswork based on general experience from seeing what has worked in the past; I can't point to any explicit documentation. Tom Liotta On Tue, 04 December 2001, "MARYLOU ATWELL" wrote: > This is where it gets tricky for me. Someone else set up the TCP on this for me about 5 years ago, and I sure haven't messed with it. Is there somewhere you can steer to me to get it set right? -- Tom Liotta The PowerTech Group, Inc. 19426 68th Avenue South Kent, WA 98032 Phone 253-872-7788 Fax 253-872-7904 http://www.400Security.com
As an Amazon Associate we earn from qualifying purchases.
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.