Hi William, as stated in http://www.isaserver.org/pages/article.asp?id=216 did you do the following: "The setup I had on the previous ISA Server incarnation had a Protocol Rule that allowed All IP Traffic to everyone outbound. That worked for us because no one else came into our office, but when our son decided to move home, I figured that a certain level of accountability was required so while all outbound traffic was still allowed, the user still had to authenticate as a domain user (that way I could pin up reports of unsavory activity on the refrigerator door). Apparently, the Gatekeeper doesn't like this configuration. When I changed the access control for the All IP Traffic rule to allow everyone access, the gatekeeper started working again! However, the prospect of allowing all outbound traffic to everyone wasn't very enticing since we have to deal with a college age kid who's traffic I need to easily keep an eye on. The solution was easy. All I need to do was create a Protocol Rule for the H.323 Protocol that allowed outbound access to everyone. That way I could continue to demand authentication for all protocols except for H.323. Since no one but Debi and I would use NetMeeting, I felt this was a safe configuration." Hope this helps. Stefano ----- Original Message ----- From: William England To: [ISAserver.org Discussion List] Sent: Thursday, September 05, 2002 10:01 PM Subject: [isalist] Incoming Netmeeting call http://www.ISAserver.org My internal client receives I call from an external client and accepts it. The Gatekeeper has an active call but then it terminates and the external client receives a message saying that the person called cannot accept netmeeting calls. Can anyone help please. H323 is making me paranoid William ------------------------------------------------------ You are currently subscribed to this ISAserver.org Discussion List as: stefano.peduzzi@xxxxxxxxxxxxx To unsubscribe send a blank email to $subst('Email.Unsub')