DNS/Print Problems

Archived from groups: microsoft.public.windowsnt.registry (More info?)

I have a bizarre print server problem after a Windows
Update reboot. (I don't have good reason to believe that
the updates are the culprit but thought I better mention
it.)
Users send print jobs to the server (NT4, SP6) and they
seem to reach the server but don't get from the server to
the printer using the DNS name of the printer. If I
switch to the IP address instead, it works just fine. To
make things even stranger, someone with Admin rights on
the server doesn't have the problem.

I have posted to other NG's for the exact problem but
wanted to post some registry info here -
I have two other print servers with identical OS, SP and
Win Updates and they aren't having this problem.

Here is a particular TCPIP subkey from the two that are
OK:
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpi
p\Linkage\Disabled]
"Bind"=hex(7):00
"Export"=hex(7):00
"Route"=hex(7):00
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpi
p\Linkage\Disabled]
"Bind"=hex(7):00,00
"Export"=hex(7):00,00
"Route"=hex(7):00,00

Here is the same subkey from the problem server:
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpi
p\Linkage\Disabled]
"Bind"=hex
(7):5c,44,65,76,69,63,65,5c,45,31,30,30,42,31,00,00
"Export"=hex
(7):5c,44,65,76,69,63,65,5c,54,63,70,69,70,5c,45,31,30,30,
42,31,00,\
00
"Route"=hex
(7):22,45,31,30,30,42,22,20,22,45,31,30,30,42,31,22,00,00

My problem appears to be a DNS client issue on the server
that somehow has weird side affects, at least for
printing.
Can someone explain what those keys mean and if they
might cause a DNS client problem?
Thanks