Gerry Voras
June 7th 04, 10:08 PM
Does your DHCP scope also set up the wins server IP? Try this -- manually
set up the WINS server config in your network stack, overriding the DHCP
setup as neccesary.
"Chrisbo" > wrote in message
...
> Grettings,
>
>
> We have about 200 computers and Two NT 4.0 servers running
> WINS. The Clients in question are the 50 Win 98's.
>
> Here's the problem:
>
> When I go to ping a pc by it's name, say DALEH, it takes
> at least 8 to ten seconds to find the host. When I ping a
> pc by it's IP it responds immediately. WINS is set up
> right and all clients are set from DHCP as 0x8 nodes.
>
> After I do an NBTSTAT -c I see the name in the cache and
> ping again but it still takes a long time. So I added the
> name in my host file and same thing. I did an NBTSTAT -r
> and found that the names were resolved by WINS and
> brodcast 5 times each.
>
>
> Can some one help me fix my slow name resolution please?
>
>
> Much Appreciatiion,
>
>
> Chrisbo
set up the WINS server config in your network stack, overriding the DHCP
setup as neccesary.
"Chrisbo" > wrote in message
...
> Grettings,
>
>
> We have about 200 computers and Two NT 4.0 servers running
> WINS. The Clients in question are the 50 Win 98's.
>
> Here's the problem:
>
> When I go to ping a pc by it's name, say DALEH, it takes
> at least 8 to ten seconds to find the host. When I ping a
> pc by it's IP it responds immediately. WINS is set up
> right and all clients are set from DHCP as 0x8 nodes.
>
> After I do an NBTSTAT -c I see the name in the cache and
> ping again but it still takes a long time. So I added the
> name in my host file and same thing. I did an NBTSTAT -r
> and found that the names were resolved by WINS and
> brodcast 5 times each.
>
>
> Can some one help me fix my slow name resolution please?
>
>
> Much Appreciatiion,
>
>
> Chrisbo