× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  • Subject: Weird Client Access problem
  • From: Tom Hightower/Solutions_Inc<tomh@xxxxxxxxx>
  • Date: Fri, 7 Jan 2000 17:52:24 -0600

Our setup:  V4R4, Client Access V3R2M0 (latest SP installed), Win 98SE.

I've installed CA, connected to the 400 thru TCP/IP, gotten a signon 
session, and logged in.  I'm trying to map \\AS400\QDLS to drive J:, with 
no success.  Whenever I try, I can hear the 400 banging away like it's 
trying to do something, then I get a Windows dialog: \\AS400\QDLS is not 
accessible. I can map other \\AS400\ folders, just not QDLS.  The strange 
thing is I CAN map QDLS on other PCs with no problem.  I've verified the IP 
address and the subnet mask, everything's cool in that respect.  During 
install, I did nothing different than I did on any of the other PCs (other 
than the static PC address, naturally).

I see no messages in DSPLOG, QSECOFR or QSYSOPR job logs.

Any ideas?
+---
| 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
+---

As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.