RE: SNA configuration

"IF" the SNA Server is cfg'd correctly and nothing is in the way... The 400 
should at least be getting errors when the SNA Server try's to attach. Have the 
SNA Server try to connect to the 400. Then go into the history log and see what 
you can see.

If nothing is there then something besides the 400 is broken...

__________________________________________________
Kirk Goins
IBM Certified iSeries Technical Solutions Expert
Pacific Information Systems - An IBM Premier Business Partner
503-674-2985           kirkg@pacinfosys.com


-----Original Message-----
From: Carley, Neil [mailto:neil.carley@misys.com]
Sent: Friday, June 28, 2002 6:38 AM
To: 'MIDRANGE-L@midrange.com'
Subject: SNA configuration


Hi,

We have a situation where we have 3 seperate AS/400's which we are trying to
connect to with a PC runnig misrosoft SNA Server 4.4. Two if the 400's work
just fine and auto create the ctld and devd once SNA server is started up
however the other 400 doesn't create the ctld and devd under the ethernet
line as on the other two systems.
I have checked all the config areas I can think of, ie qautocfg, autocfg
parm on the line, network attributes etc and still can't get it to work. The
only difference with machine C is that its netid is GBIBM100 whereas the
others are appn, however this has been noted in the SNA server config so it
shouldn't matter.
Is there any other areas that govern wheather things are auto created or can
anyone suggest somthing I may be over looking on system C ?

Thanks
Neil


_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
or email: MIDRANGE-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.