I've been following the thread and have not checked the differences.
However, I have two Win2K machines on my home network that experiences no
delay/lag with tinydns on the LEAF box. But my work notebook experiences
some delays when I bring it home and connect up. I assumed that this was a
difference in configurations since at work we use a domain based network
and home uses workgroup. The only way it has worked for me is to call my
home workgroup the same as the work domain. I also have to keep automatic
discovery enabled instead of defining certain TCP/IP parameters.
May not be much help but hope this gives additional clues. I may just
experiment with some of the suggestions given in this thread (ie; suffix,
reg tweaks, etc.) to see if they make any difference.
Cheers,
John
Brad Fritz
[EMAIL PROTECTED] To:
[EMAIL PROTECTED]
Sent by: cc:
[EMAIL PROTECTED]Subject: [leaf-user] Re: [OT]
Win2K DNS Problem.
ceforge.net
01/03/2003 08:36 AM
On Thu, 02 Jan 2003 23:40:35 CST Lynn Avants wrote:
On Thursday 02 January 2003 10:59 pm, you wrote:
While I don't know enough about Win2k to comment for all
configurations of that OS, I can say that I do not have a dns
suffix specified and I don't experience any dns-related hangs
or timeouts (immediately after reboot or otherwise).
Are you using DHCP on the machine(s) w/o a suffix???
No, it uses a static address: 192.168.70.128.
I'll admit
that this problem is not (as) likely to happen on the home releases,
I run Windows 2000 Professional (without any service packs,
IIRC).
the pro/server release of Win2k/XP are set to run within a domain
network and this has tons of compatibility problems with any other
network setup.
That is configurable via the System Properties Network
Identification tab. My computer is part of a workgroup,
not a (MS Windows) domain.
My assumptions is that Mohan is running a non-home
Kory, not Mohan. ;-)
version of Win2K and the non-rfc compliant DNS/WINS implementation
is causing the lag because of the default assumption by Win2k that
he is on a domain Win2K/XP network. The problem this behavior causes
with older M$ networks can be mind-numbing if you haven't worked with
a company adding Win2k/XP workstations w/o upgrading the servers and
other workstations.
I don't deny it might be an improperly configured Win2k setup or
non-RFC behavior triggered by something in his configuration
that is not in mine. I'm just saying there are configurations of
Win2k professional that do not have problems using djbdns dnscache
for name service...even with a static address and without a DNS
suffix.
--Brad
---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
leaf-user mailing list: [EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/leaf-user
SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html
---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
leaf-user mailing list: [EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/leaf-user
SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html
