Wierd W2k3/NT4 problems

[Alex Matten]

Hi everyone, a little info first: a client has a nt4.0
domain with a w2k3 member server. PDC is running WINS &
DHCP, and only protocol is TCP/IP (this is according to
the client; PDC is locked down and she didnt have time to
let me in for me to check personally). No local DNS
Server, all DNS entries point to ISP. 3 stacked 24-port
100base switches, both servers patched into bottom
switch. 4 fiber links coming into top switch from
seperate buildings. Mix of 98 & XP workstations.
The problem: Slow network performance between NT/98 &
w2k3. A 2meg directory copied from NT PDC to the w2k3
member server takes over a minute, same with 98 to w2k3.
2meg directory copied from XP workstation in seperate
building to w2k3 takes ~10 seconds.
The first things that pop into my head are the lack of
Netbeui in a NT4 domain, and the lack of local DNS with
the w2k3. But I'm also having problems thinking that
either of those two things would create that much of a
performace issue. Any advice would be highly appreciated,
thanks.

Alex.

 

[Scott Harding - MS MVP]

This is not related to Netbeui. It is not needed or recommended for NT or
any other OS for that matter. Especially when you have a bunch of machines
on the network. This is most likely a name resolution issue or something on
the switches. I would check for 10/100 detection on the cards in question.
Sometimes you have to hard code them instead of having them 'Auto
Negotiate'. Does the Win2k machine point to the correct WINS server?

 

[Alex Matten]

Yea, I checked the ports that both servers were patched
to, both at 100, also double checked the WINS address in
w2k3, and added a static entry since the w2k3 has a static
ip. Any other ideas? It's odd that XPws going through
all 3 uplinked switches and a fiber link to the w2k3 is
just fine. All workstations to NT is also fine, no issues
there, only between the NT/98 & w2k3. Thanks.

Alex