RE: V5R1M0 network being abducted by NT/XP -- 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.

Try  putting a "$" in the scope id field in the NT/XP pc.  You can also go
to services and stop the master browser service then change to manual start
all on the NT/XP system.

-----Original Message-----
From: Roger Vicker, CCP [mailto:rvicker@vicker.com]
Sent: Wednesday, February 27, 2002 8:10 PM
To: Midrange List
Subject: V5R1M0 network being abducted by NT/XP

Hello

Background:
AS/400 model 170
V5R1M0 (since 2/23/2002)
Cum C1302510 (latest cum and all groups on order)
Netserver configured to be the logon server
Network PCs are Win95, Win98se, WinNT4 Workstation (sp6), WinXP Pro
No PC servers involved

The WinXP and one of two WinNT4 PCs keep causing the following
message. Reason code 3 and 4 both show up. If I restart  the named PC
another shows up soon after. The Win9x PCs do not show up in one of
these messages at any time. Also, only the Win9x PCs are logging on to
the AS/400 domain as I haven't been able to confirm if the PLC is
compatible with WinXP yet and haven't gotten to the NT4.

Any ideas on how to prevent these systems from arguing with the AS/400
over being the master browser.

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.