Strange DNS issue

[Nuke]

Weird one - any suggestions would be appreciated:
- Server 2003, running DNS
- Workstation 1 (wks1), PIII/700, XP Pro(SP1), 3com NIC
- Workstation 2 (wks2), PIV/2.5, XP Pro(SP1), Leadtec NIC

All works fine - name resultion - internal and external.
When I browse the (internal) network (for example
\\server\data) with wks1 - things are nice and dandy.
When I browse the same resource with wks2 it takes three
seconds to open each file tree, and browsing the network
is very slow.
Now, when I access the share as 192.168.x.x on wks2 -
things are flying.

The internal network runs on 100mb, DNS is setup
correctly (since it works fine on all other workstations).
IP configuration is same as the others (server DNS first,
no second dns) - this is same setup as others.
Since when using the IP address all works fine, I am
assuming something weird on the WKS2 DNS setup. Maybe a
registry thing.
Anybody have any suggestion - I'm out of them ;-)
Thanks for any replies.....

 

[Quaoar]

Weird one - any suggestions would be appreciated:
- Server 2003, running DNS
- Workstation 1 (wks1), PIII/700, XP Pro(SP1), 3com NIC
- Workstation 2 (wks2), PIV/2.5, XP Pro(SP1), Leadtec NIC

All works fine - name resultion - internal and external.
When I browse the (internal) network (for example
\\server\data) with wks1 - things are nice and dandy.
When I browse the same resource with wks2 it takes three
seconds to open each file tree, and browsing the network
is very slow.
Now, when I access the share as 192.168.x.x on wks2 -
things are flying.

The internal network runs on 100mb, DNS is setup
correctly (since it works fine on all other workstations).
IP configuration is same as the others (server DNS first,
no second dns) - this is same setup as others.
Since when using the IP address all works fine, I am
assuming something weird on the WKS2 DNS setup. Maybe a
registry thing.
Anybody have any suggestion - I'm out of them ;-)
Thanks for any replies.....

The first thing to check is your main assumption: network runs on
100Mb/s. Check the wiring on the problem computer. Reset the NIC to
10M and see if things improve. Bad wiring (improper RJ45 assembly,
broken, bent, or frayed wires) will do strange things much like you
describe.

Q

 

[Nuke]

Thanks Q,
you think this could be the case, even when it works fine
if I browse op IP iso DNS name?
Thanks again,
Nuke

 

[CZ]

Weird one - any suggestions would be appreciated:
- Server 2003, running DNS
- Workstation 1 (wks1), PIII/700, XP Pro(SP1), 3com NIC
- Workstation 2 (wks2), PIV/2.5, XP Pro(SP1), Leadtec NIC

All works fine - name resolution - internal and external.
When I browse the (internal) network (for example
\\server\data) with wks1 - things are nice and dandy.
When I browse the same resource with wks2 it takes three
seconds to open each file tree, and browsing the network
is very slow.
Now, when I access the share as 192.168.x.x on wks2 -
things are flying.


Nuke:

Look at your NetBIOS configuration on the problem ws.
Per packet sniffing, NetBIOS ports are used for Start: Run: \\server\data