×
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.
We recently converted our NT4 networking environment to Server 2003. While
perusing the Event Viewer of the PDC, I'm noticing a number of 4319's each
day.
The help for this even says the IP address is contained in the Error's
data. I believe I've located the appropriate data and converted the hex to
decimal and transposed them. It seems to be pointing to the iSeries (730
running V5R2) as the reporting machine.
Help for 4319 says to run NBTSTAT -n to find the name in conflict. When I
do this on the PDC, nothing shows as in conflict. So, I come here
wondering if anyone has had something similar happen and the resolution?
Bill
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.
midrange.com
