Re: NetServer

You still could have a firewall problem, but if that is not it you will 
have to use the LMHOSTS file as mentioned in the below snippet from the 
netserver web site.
Most routers do not forward netbios information so the netbios over tcp/ip 
must be used.

Resolving AS/400 NetServer Name -
 Add an entry for the AS/400 NetServer to a Domain Name Server (DNS), the 
PC's local LMHOSTS, or set up a Windows Internet Name Server (WINS) to 
resolve the AS/400 NetServer server name. The quickest way is to add an 
entry to the LMHOSTS file located in the \Windows directory on a Windows 
95 PC, or the \WINNT\system32\drivers\etc directory on a Windows NT PC. If 
you cannot find an LMHOSTS file in the specified directory it might not 
have been created yet. Rename LMHOSTS.SAM in that same directory to 
LMHOSTS and then add a line with the following format: 

TCP/IP-address AS/400-NetServer-server-name #PRE 

For example: 9.5.10.1 QNETSERVER #PRE 
From:
http://www.iseries.ibm.com/netserver/fastpath.htm


In article <000001c0938b$f54d6080$021414ac@rc5030>, Richard Casey
<casey_r@popmail.firn.edu> writes
>    If my computer is connected to the same LAN as the AS/400, I can
>    connect to Netserver just fine.
>    The problem occurs when I'm trying to connect remotely via the
>    Internet. Are there any additional network protocols I need to
>    configure?
>    I can telnet and ftp just fine remotely; I just can't connect to
>    NetServer.



Bryan Dietz


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