We have a small LAN here with NT4/98 clients. I reformated an NT machine and
poped win2k on it, but as soon as I try to access the network, it takes
over. It can access the samba server fine, but none of the 98/NT machines
can see anything.
Tried originally with 2.0.7-pre4, then i installed 2.0.7 final and
experianced the same problem. Win2k has but to touch the network
neighboorhood to wreck havok. If I leave it at the list of computers on the
network, and don't even click on any of them, it has already taken over by
that point.
log.smb shows nothing, heres the relevant cut of log.nmb:
[2000/05/02 17:53:00, 0]
nmbd/nmbd_nameregister.c:register_name_response(111)
register_name_response: server at IP 10.0.0.21 rejected our name
registration of AXISTANGENT<1d> with error code 6.
[2000/05/02 17:53:00, 0]
nmbd/nmbd_become_lmb.c:become_local_master_fail2(426)
become_local_master_fail2: failed to register name AXISTANGENT<1d> on
subnet 10.0.0.65. Failed to become a local master browser.
[2000/05/02 17:53:00, 0] nmbd/nmbd_namelistdb.c:standard_fail_register(294)
standard_fail_register: Failed to register/refresh name AXISTANGENT<1d>
on
subnet 10.0.0.65
[2000/05/02 17:53:00, 0]
nmbd/nmbd_responserecordsdb.c:find_response_record(239)
find_response_record: response packet id 19066 received with no matching
record.
Now, the /really/ looks off to me. AXISTANGENT is our workgroup. 10.0.0.0 is
subneted as a full /24, there's no such thing as "subnet
10.0.0.65". And
10.0.0.21 is a NT4 workstation no one was near at the time. There is no
mention of the 2K machine (10.0.0.99). But this is what appears before the
SMB goes down for everything but the 2K machine.
The fix seems to be powering off the 2K machine, killing [sn]mbd, rebooting
all workstations, then starting [sn]mbd. It's like they've been
brainwashed
and have to totally have their memory of the 2K machine wiped out. A few of
the NT workstaions *STILL* cant see anything but themselves in network
neighborhood, after many reboots/samba restarts. Even tryed adding them to a
differant workgroup, then moving back to AXISTANGENT. They ping fine, and
can cruise the web, etc...
So, heads up all. =) Win2K is hazardous to your LANs health.
--
Jeremy M. Dolan
Systems Administrator
AxisTangent & Technologies
