You can make sure all the client apps you don't want connecting aren't configured to connect, but that's not really feasible in a large network or with obnoxious users... And anyway if the packets get routed to your ISA (via default route or some other routing mechanism) they'll get there. I suppose you could set up a routing filter to drop the packets. Reconfigure logging not to log the field. If you don't see it it's not connecting, right? :) (ha-ha, that's a joke) GHBN=Get Host By Name maybe? That would be a name resolution request (dns, wins, etc). Never seen it before, just a thought. -Shawn > ____________________ > > Shawn R. Quillman > Robert Bosch Corporation AN-Fh/CIT5 > 38000 Hills Tech Drive > Farmington Hills, MI 48331 > (248) 553-1164 (P) (248) 848-2855 (F) > shawn.quillman@xxxxxxxxxxxx > ____________________ -----Original Message----- From: Ray Dzek [mailto:rdzek@xxxxxxxxxxxxxxx] Sent: Monday, January 14, 2002 3:50 PM To: [ISAserver.org Discussion List] Subject: [isalist] Blocking Applications http://www.ISAserver.org I noticed in my firewall logs that I can see the application connecting. As in realplay.exe, winamp.exe, etc. Is there a way to block the application from connecting to ISA? I also see an entry called GHBN in my firewall logs. Does anybody know what that entry means? Thanks. ------------------------------------------------------ You are currently subscribed to this ISAserver.org Discussion List as: shawn.quillman@xxxxxxxxxxxx To unsubscribe send a blank email to $subst('Email.Unsub')