Chupa said:
HM: There is no need for a connection specific suffix when
it is the SAME as the Primary DNS suffix -- but this is NOT
your problem.
:I added specific suffix to be shure workstation correctly ads suffixes..
That won't help if you do the Control Panel primary
name correctly which is the right way.
HM: Double check that ALL machines -- especially
servers have NetBIOS enabled, and use the SAME
WINS Server. Not just the affected clients, but check
them too.
:I checked, NetBios is enabled on all DNS & WINS server.
And they all specify the same WINS server?
HM: So some shares are public.
:yes some are public but behind firewall, so only visible to local domain..
not a mater of priority at this point.
Firewall where precisely? Between the working machines
and the failing machines?
What kind of firewall?
(Domain membership is not specifically required but the
NetBIOS name MUST match.)
Double check the NetBIOS name for each machine in the
System Control panel (this is the name that COUNTS for
browsing.)
are these names case sensitive? /i think not as on every machine my first
leter is upercase and in DNS is lowercase/
No, neither WINS nor DNS is case sensitive.
(Actually the NetBIOS/WINS is case sensitive, but the name
is always uppercased when a machine name is used.)
:I looked and they match but on sys.control panel its Unimatrix and in DNS
is unimatrix..
Not an issue. DNS is not case sensitive.
Also note, the DNS name there (unrelated to browsing)
is the name that REALLY counts for DNS (not the ones
on the NICs.)
Are you using a DC for a router (multiple NICs)?
:No, but I do have multiple NICs on both (DNS&DC and WINS) servers but its
only for IIS to be visible outside firewall.
There are supposed issues with DC, WINS server that
have multiple NICs. Personally I have never run into
that but it is a commonly reported problem, and documented
in some KB article at MS.
Could be your problem.
Also note it is a very poor security practice to
for a DC to be exposed onto the Internet -- but
that isn't your current problem here.
Do any of these machines have multiple NICs?
Are these NICs on the SAME subnet/segment (i.e.,
broadcast domain)?
:afected machines have only one NIC adapter and it works flawlesly.
Ok, some people try to stick two NICs in one machine
on one segment -- NetBIOS doesn't deal with that well.
How about firewalls? Is it possible that one of the
XP machines running SP2 is also getting elected as
Master Browser (check the Event Logs for browser
errors.)
:All machines get out through firewall on xxx.xxx.55.11 (as seen on
ipconfig -all I posted before.)
:Except servers running IIS and having 2 NICs - they go out bypassing
firewall, but with them i dont have any problem.
Can the firewall be blocking the traffic to/from
the WINS server or the Master Browser and
Domain Master Browser.
(NetMon or EtherReal to watch traffic).
Perhaps trying BrowStat.exe (Support Tools)
to identify your Browse Master.
: Im writing this without checking but i beleeve I have seen something about
master browser reelection in eventlogs
An occasional Browser election is expected, look
mostly for errors or repetitive elections that look
to be due to problems.
: but I havent got into this as everithing worked fine.. ill check this
later and post back.. and yes it is xp sp2 machine, the other one is w2k
sp4. Interesting part is that only these two machines see each other but not
any other machine on the same switch, when i use search for computer by name
or IP they find all machines around them, but in no way I cant force them to
list all computers in domain either by net view command or by browsing
network places
Is every machine running IP? (Surely they are, but
I am trying to be complete since the initial checks
have not resolve it.)
yes.
Finally, there have occasionally been nearly impossible
to dianose problems with some Hubs/Switches or
cabling where the broadcasts were not getting properly
distributed even though the net seemed to work -- somehow
-- anyway.
: All domain machines are on same switch and dont have this problem, even
phisicaly same machines (same hardware..)
Some such switches have acted up in the past.
Try swapping cables AND port -- see if the
problem moves around. (Give it an hour or
more for browsing to time out and repopulate.)