----------
From:   Curt Brimacomb
DNS in WIN95, the delay went away.
What I do not understand is why when I put in an IP address instead of a name did it still try to use DNS?  Oh, Well.


_________________________________________________________________

I have not located the beginning of this thread but..........I also have been
puzzelled by this stuff.  Our 3000 cares squat about anything not hooked
to it by a termulator or telnet from offsite.  Our T1 got chopped in Houston
and suddenly people were taking minutes (4?5?) to logon or were timing
out.  I didn't much belive them at first as I had no problem.  Ummm...
I have a serial connection to a DTC (which of course is hooked to the
local net backbone) and everyone else has a VT-MGR,  Win95/NT
connection.  The problem most certaily appears to have been one
of address resolution however, all desktops use IP addressing.

Our T1 links us to Dever via San Deigo.  The 3k cares not of them (my
serial connect worked fine).  We use local (the 3k) IP addresses.
So what's to resolve?

The recommendation from upstream is we develop a local DNS server
which we kinda need to do anyhow.  I'm no net guru or even close to
it.  I still don't understand why someone locally using the IP address
of the local 3k needs to go out of the locat LAN to resolve an address.

Jim (maybe I *will* take the anesthetic next time at the dentist) Woreout