RE: LMHOSTS file

["Wilt, Charles" <CWilt@xxxxxxxxxxxx>]

Rick,

Never thought of using nbtstat like that to check nbt connectivity to
another box.

Trying it out here, it didn't work but I can still access my iSeries via
Netserver.

Can you use nbtstat -a to any other Windows server?

If not, it may be that the VPN isn't allowing the traffic.

If so, then check out the WINS settings on the iSeries Netserver.  Those
were incorrect here ( we switched WINS servers ), I corrected them,
stopped and restarted Netserver and the nbtstat -a myas400 name worked.

Also, make sure you are using the right NBT name.  My iSeries is
PROD400, but the nbtstat -a only worked with QPROD400, which is what is
listed in the Netserver configuration as "Server Name".  But I've always
been able to use \\PROD400 or \\QPROD400 in Windows Explorer even though
the "Allow iSeries Netserver access using the system name" is UNCHECKED.

HTH,

Charles Wilt
--
iSeries Systems Administrator / Developer
Mitsubishi Electric Automotive America
ph: 513-573-4343
fax: 513-398-1121
  

> -----Original Message-----
> From: midrange-l-bounces@xxxxxxxxxxxx 
> [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rick baird
> Sent: Wednesday, January 25, 2006 2:21 PM
> To: Midrange Systems Technical Discussion
> Subject: Re: LMHOSTS file
> 
> Charles,
> 
> > AFAIK, nbtstat isn't a "ping" type utility.  How are you 
> trying to use
> > it?
> 
> NBTSTAT -a as400name
> 
> found it on an ibm infocenter page describing setting up netserver. 
> it said to try it before ping to check if netserver can be accessed. 
> i've since lost the page.
> 
> > What happens when you key \\as400name into Windows Explorer?
> 
> network path not found.
> 
> Rick
> 
> -- 
> 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.
> 
>