On Friday 03 January 2003 08:52 am, you wrote:

> > The Win2K box is trying to find the domain-name from your DNS
> > server since you have NOT entered one manually (like most of us do).
>
> Actually its trying to do a reverse lookup on 192.168.1.254, but it failed.

Yes, to pull a dns suffix so that the workstation can "create" a FQDN.


> > Win2K is attempting to figure out what your domain-name by DNS records
> > on the internet and broadcast, forcing you to wait until it fails before
> > resolving any DNS information requested by the user (the lag).
>
> Actually, the "broadcast" is the netbios node type. i.e. How does this W2K
> system announce its MS workgroup/domain affiliation on the network...
> broadcast or WINS (Network Neighborhood stuff). This has nothing to do with
> DNS.

True, according to the existing DNS and WINS rfc's. However, M$ has 
combined/overlapped these services in Win2k/XP. Or possibly I am just
out of my mind...... many admins have run into similar problems with legacy
M$ networks when we "just" added a couple of Win2k workstations to the
existing network. Some of the problems have been: failure for Win2k shares
to show to legacy OS boxes and information transfer at snail speed. These
problems were noted as a problem due to the "lack" of the upgraded DNS/
WINS implementation by M$ techs on the legacy boxes and it was 
suggested that we upgrade all machines to Win2K Pro/Server to avoid these
problems. We buy Mac workstations instead now.....much nicer all around!  ;-)


> > If you used DHCP to receive an ip address (per default setup), this
> > information would be received via the DHCP lease.
> >
> > You will have this problem EVERY reboot until you either use
> > DHCP on the Win2k client or enter a domain-name (anything
> > basically) in the IP setup on the Win2k machine.
>
> Although I don't disagree with the above, the DNS suffix is typically
> used/set in the connection specific part of ipconfig. i.e. Each interface
> on W2K can have a DNS suffix.

Agreed.


> Also, this is my personal preference, not a recommended policy. But I
> disable W2K's caching server. This fricken thing has caused me more greif
> than I care to mention. Try and tell a regular how user to flush the cache.
> That will go over real well...

I'll have to try that..... personally, I loved the move to Mac's..... I've
quickly learned to enjoy PPC over Intel and avoid the M$ problems that
I had.

~Lynn Avants


-------------------------------------------------------
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

Reply via email to