|
This is a multipart message in MIME format. -- [ Picked text/plain from multipart/alternative ] host tables are the root of all evil. Barely acceptable for testing and debugging. However you need to use a dns. Rob Berendt -- "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." Benjamin Franklin "Paul Nelson" <p_nelson-br@pop.inil.com> Sent by: midrange-l-admin@midrange.com 04/11/2002 07:43 PM Please respond to midrange-l To: <midrange-l@midrange.com> cc: Fax to: Subject: Re: CAE - Mapping Network Drives Have you set up the Netserver name & IP address in the LMHOSTS file? It looks like the entry in the HOSTS file, plus you need to add the #PRE and #DOM:domain_name parameters. After you modify the LMHOSTS file, get into a DOS command screen and type the following: nbtstat -R and press enter nbtstat -c and press enter Now you should be able to find the server name established in Ops Nav. Make sure it's configured properly per the instructions referenced elsewhere on this list. If you can't find it with the name, try to find it with the IP address. For some reason, this sometimes forces things to wake up. Paul Nelson Braxton-Reed, Inc. 630-327-8665 Cell 708-923-7354 Home pnelson@braxton-reed.com ----- Original Message ----- From: "Dave Snyder" <dsnyder@blcnet.com> To: <midrange-l@midrange.com> Sent: Thursday, April 11, 2002 1:15 PM Subject: CAE - Mapping Network Drives > I recently converted my p/c from Client Access to Client Access Express and am having trouble seeing the AS400 through windows. I have researched and tried and looked up about as much as I can figure out to try, and just can't seem to get to the AS400 via Windows 98. I can ping the netserver on the AS400 from my p/c, but can not find it using the FIND utility in Windows nor can I see it via Windows Explorer/Network Neighborhood. As far as I can tell I have the domain correct in the netserver, but still no go. Any more tips for me to try? > Dave > > _______________________________________________ > 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. > > _______________________________________________ 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.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.