chgtcpdmn -- 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: chgtcpdmn
From: "Troy Dills" <troypmc@xxxxxxxxxxx>
Date: Wed, 18 Dec 2002 11:15:19 -0500
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>

Does anyone know why I would recieve this message in the
qsysopr when I use the command chgtcpdmn. Every thing is
setup right. We can see the 400 on some PC's but not all.
The 2 pc's that we can't see the 400 on is a win98 and a
winXP pro pc, if that helps.

The AS/400 Support for Windows Network Neighborhood
(AS/400 NetServer) was unable to start.

AS/400 Support for Windows Network Neighborhood (AS/400
NetServer)QS10B0379 ended.


Thanks
Troy Dills

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: chgtcpdmn , Scott Klement

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.