NBT woes
From: kpg (ipost_at_thereforeiam.com)
Date: 11/12/04
- Next message: Jtyc: "Re: OT: Semper Fidelis"
- Previous message: LnkWizard: "Re: Remembrance Day 11/11/2004"
- Next in thread: Neil: "Re: NBT woes"
- Reply: Neil: "Re: NBT woes"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 12 Nov 2004 09:30:10 -0600
Does anybody really understand how NetBios names are
resolved, cached and used in a peer-to-peer mixed 2000,
XP, 98 network using TCP? I think not. No NetBEUI,
only TCP with NetBios over TCP enabled. 2000 machine
is not active directory, DHCP server is a linksys router.
DNS from ISP. 98 machines lose NetBios name resolution
daily, randomly. Only fix is to hard code LMHosts.
Browser elections seem normal, sometimes 98 machines
are elected sometimes others. Can't get the stupid
browstat utility to work. Nbtstat is useless. Set the
2000 file server to be the master browser, set the other
2000 IIS server to be backup. No help. I think the trouble
started with the introduction of XP machines into the
environment, and it has accelerated after SP2 was applied.
This kind of crap is what gives MS a bad name and what
keeps network guys employed. But I'm just a simple
programmer just trying to do my job and every day it's:I
can't get to the F: drive, please come look at it. And
what's with XP Home? Why is it so hard to make it talk
to other computers? That stupid connect to a network
wizard doesn't work. I'm going to shoot someone.
-- kpg A+ MCP MCNGP 0x22 I'm free of all prejudices. I hate everyone equally." W.C. Fields
- Next message: Jtyc: "Re: OT: Semper Fidelis"
- Previous message: LnkWizard: "Re: Remembrance Day 11/11/2004"
- Next in thread: Neil: "Re: NBT woes"
- Reply: Neil: "Re: NBT woes"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|