RE: Novice AS400 -- MIDRANGE-L

Hi Pete,

Thanx for the suggestion.

as-mgtc entries exist.

Can't understand how having those ports blocked on the Linux box
would make any difference. Anyway, tried unblocking and it did
not make any difference. ;-P

Cheers,
Mark

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Pete Helgren
Sent: Friday, 21 January 2005 11:24 AM
To: 'Midrange Systems Technical Discussion'
Subject: RE: Novice AS400

Ok.

Wild guesses at this point...

If you use the command NETSTAT *CNN do you see the as-mgtc > entries ?  They
should be listening for connections.  They listen on ports 5544 and 5555.
Any chance these ports are blocked by your Linux server?

Pete

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Mark Bailey
Sent: Thursday, January 20, 2005 3:55 PM
To: 'Midrange Systems Technical Discussion'
Subject: RE: Novice AS400

Hi Peter and Scott,

Thanx for your suggestions. 
I have tested all of your comments and made a few changes still to no avail.
Here are notes regarding both of you suggestions

I should have said that this machine is NOT directly connected to the
internet. It is connected to my network. 192.168.1.1 in a Linux box the
internet server and manages mydomain.com.au.

I had mydomain.com.au as the domain name on the AS400 with Host name search
priority set to *REMOTE and Internet address set to the address of my
mydomain.com.au on the internet. I suspected that this would probably
conflict with itself so on the AS400 I have set the following...

Hostname     'HO400M'
Domainname   'MYDOMAIN.AS400'
Domain Search   *DFT
Host name search        *LOCAL
Internet address        *NONE

In the host table entries I have the following

127.0.0.1               LOOPBACK
                        LOCALHOST
192.168.1.1             GENIUS          (the Linux box and outside world)
192.168.1.2             MERLIN          (Windows XP Pro machine)
192.168.1.99    HO400M
                        HO400M.MYDOMAIN.AS400

On the Windows machine in the hosts file I have
127.0.0.1               localhost
192.168.1.99    HO400M.MYDOMAIN.AS400 HO400M
192.168.1.1             genius


I can successfully CWBPING the AS400 with the host name , qualified host
name and the IP address.

The above was unsuccessful.

Regards,
Mark






-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Pete Helgren
Sent: Thursday, 20 January 2005 11:55 PM
To: 'Midrange Systems Technical Discussion'
Subject: RE: Novice AS400

Mark,

I suspect a name resolution problem.  I have always been most successful in
OpsNav connections, at least initially, when I use the IP address of the
iSeries. Next, I make sure that the host file has the entry that resolves
the address.

I'd try the IP address as the System name and, if that works, then I would
add:

myservername.mydomainname.com.au  XXX.XXX.XXX.XXX (your IP address) to the
host file on your PC running Ops Nav and see if that works...


Pete Helgren
Value Added Software, Inc
801.581.1154 x202

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of mbailey@xxxxxxxxxxxx
Sent: Thursday, January 20, 2005 7:44 AM
To: midrange-l@xxxxxxxxxxxx
Subject: Novice AS400

Hi,

 

I have recently purchased a second hand AS400 do use as an

experimental development machine using Magic.

 

I am a complete novice when in comes to this machine and this is the

first time I had ever actually laid a hand on one.

 

Very exciting learning curve. I have poured over Red Books and the net

and slowly making headway. I suppose I should do a course but the cost would

be way out of my league. 

 

Anyway, 

I have come up against a problem and I am now at a loss.

 

The machine is a 170 / 2290 running V5R1.

 

After a lot of experimentation, reading, purchase of book (from the USA as I
could not find on

here in Perth) etc I am stumped.

 

I am trying to get the Operations Navigator working. 

 

I have worked through numerous problems wit respect to TCP/IP, hosts just to
be able to ping into

and out of the machine. Finally got all that working.

 

I initially was running QCTL and although I could ping in and out I could
not get a screen displayed

when using Personal Communications AS/400 Client Access Express for Windows.
Also, I could not

get a screen displayed when telneting into the machine.

 

I was suggest that I should try QBase instead of QCTL.. This solved the
problem to a point.

 

I can now happily telnet into the machine and actually get a screen to work
with.

I can use the client terminal Personal Communications AS/400 Client Access
Express for Windows

and get a screen to work with and that all seems fine.

 

However, there is still a problem with the Operations Navigator.

If I Verify Connection. on the My Connections server name everything
verifies ok.

But when I click on Management Central, it tries to connect but then gives
the following error.

"Unable to complete the connection to central system
"myservername.mydomainname.com.au"

 

I have MGTC started

I have the host file on the Win machine ok and host in the AS400 configured.

I can expand the server branch on the Operations Navigator tree but it only
displays Basic Operations.

 

I don't suppose anyone might be able to suggest (speak slowly please step by
step and assume I am a child ;- ) )

any ideas of what might be the problem and how to fix this please

 

Kind Regards

Mark Bailey

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Cheers,
Mark Bailey
Perth, Western Australia

tagline

 


--
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.300 / Virus Database: 265.7.1 - Release Date: 19/01/2005


--
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.


-- 
No virus found in this incoming message.
Checked by AVG Anti-Virus.
Version: 7.0.300 / Virus Database: 265.7.1 - Release Date: 19/01/2005
 

-- 
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.300 / Virus Database: 265.7.1 - Release Date: 19/01/2005
 

-- 
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.


-- 
No virus found in this incoming message.
Checked by AVG Anti-Virus.
Version: 7.0.300 / Virus Database: 265.7.1 - Release Date: 19/01/2005
 

-- 
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.300 / Virus Database: 265.7.1 - Release Date: 19/01/2005