Re: Spooler subsystem app accessing DNS
From: Boogie Woogie Flu (spam_at_email.sux)
Date: 05/31/03
- Previous message: Paul Lynch: "Re: Configuring web site to require certificates"
- In reply to: Ellie: "Re: Spooler subsystem app accessing DNS"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Sat, 31 May 2003 09:31:47 GMT
> My guess is that ZA is simply alerting you to "conversation" occurring
> between your computer's software and your net bios -- your basic I/O
> system -- in other words internal communication. The programs are
> looking for YOUR computer's DNS name (not your ISP's DNS).
The IP address that's shown in the ZA alert dialog is my ISP's DNS. I've
seen other alerts, like the Generic Host Process for Win32 where the address
referenced is "DNS:127.0.0.1" (My PC) but not when the spooler subsystem
requests access. It's always my ISP's DNS.
(In
> addition to your [unique per session] IP, your computer has its own
> [unique per session] DNS, and that's it's job -- coverts all your
> "connection" decimal names to "short" names for speed.)
>
> You obviously have some software coded to call up a spooler -- and it
> is required to "get" your computer's short name squared away in
> anticipation of a print command.
I thought of this as well, but I have NetBios over TCP/IP disabled and file
and printer sharing is not bound to TCP/IP. I'm using NetBeui exclusively
for file and printer sharing. So why would the print spooler need to access
DNS to resolve a NetBios name to an IP address?
> I'm no expert, but I use ZA and my computer is always talking to
> itself. If you've any doubt -- check out the source DNS port and
> destination info on the "technical" and "details" help screens ZA
> offers for each alert. Check the source/destination sources against
> your computer's current DNS (as listed in ipconfig and other places),
> you'll probably see it starts and ends on your own desktop.
Nope. It's definitely the DNS server assigned by my ISP.
(The
> reason you're not "seeing" it connect or "do anything" is that all
> it's doing is collecting your computer's short name. For instance, my
> computer's "short" name is my first name.)
Shouldn't need access to DNS to resolve a NetBios name if file and printer
sharing uses the NetBeui protocol only.
- Previous message: Paul Lynch: "Re: Configuring web site to require certificates"
- In reply to: Ellie: "Re: Spooler subsystem app accessing DNS"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
|
