RE: TCP/IP and Components -- MIDRANGE-L

× 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: RE: TCP/IP and Components
From: "Fritz Hayes" <fhayes@xxxxxxxxxxxxx>
Date: 2 Jan 2002 19:06:58 -0800
Importance: Normal
List-archive: <http://archive.midrange.com/midrange-l/>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/cgi-bin/listinfo/midrange-l>,<mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/cgi-bin/listinfo/midrange-l>,<mailto:midrange-l-request@midrange.com?subject=unsubscribe>
Organization: Atwater Associates

Hi Dare,

Looks like you have a rather complex network structure!  One thing that
may help the situation with Explorer and shared directories is to
manually put a server entry into the WINS server.  This can help to kick
start the Network Neighborhood stuff.  Also, check to see what workgroup
(NT Domain) that the 400 has been assigned to.

Best Regards

Fritz Hayes
Atwater Associates
<snip>

|
|Yes, I have the QZLSxxxxx jobs but can not find the system
|from windows.
|

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.