Welcome to ISAserver.org
Forums |
Register |
Login |
My Profile |
Inbox |
RSS 
|
My Subscription |
My Forums |
Address Book |
Member List |
Search |
FAQ |
Ticket List |
Log Out
NetMeeting only works when allowing ALL Protocols
|
Users viewing this topic:
none
|
Logged in as: Guest
|
Login  | |
|
NetMeeting only works when allowing ALL Protocols - 15.Apr.2003 11:51:00 PM
|
|
|
weasle
Posts: 11
Joined: 21.Mar.2003
From: Texas
Status: offline
|
I have ISA server in place in integrated mode. I have been trying to get NetMeeting to work from the LAN to an external client with a static IP. I have followed all the white papers and instructions in "Configuring ISA Server 2000". I have a protocol rule set for H.323 to allow any request any time. NetMeeting would not make a connection. I tried it with an internal NetMeeting client using ISA as a gatekeeper and not. Fianlly I got Netmeeting to make a connection by creating a test protocol set to allow All/All/All to the internal client. I don't want to leave it like this just for NetMeeting. What could this be?
|
|
|
|
|
RE: NetMeeting only works when allowing ALL Protocols - 16.Apr.2003 1:20:00 AM
|
|
|
tshinder
Posts: 47490
Joined: 10.Jan.2001
From: Texas
Status: offline
|
Hi Weasle,
You should just need an all open site and content rule, not an all open protocl rule, since you should be using the H.323 gatekeeper.
HTH,
Tom
|
|
|
|
RE: NetMeeting only works when allowing ALL Protocols - 16.Apr.2003 2:41:00 PM
|
|
|
weasle
Posts: 11
Joined: 21.Mar.2003
From: Texas
Status: offline
|
In Site and Content Rules I have only one rule. It is my default rule that is allow all for any request. It has been there from the initial install, but it is only when I enable the allow all rule in the Protocol Rules that NetMeeting will make a connection to an external client.
|
|
|
|
|
RE: NetMeeting only works when allowing ALL Protocols - 16.Apr.2003 7:43:00 PM
|
|
|
weasle
Posts: 11
Joined: 21.Mar.2003
From: Texas
Status: offline
|
I want to try to give a more detailed scenario of my problem (I am getting desparate for a solution)!
I have run a "netstat -na | find '1720'" on the ISA server while my internal client is trying to make a connection to the external client. I get the following results:
TCP 0.0.0.0:1720 0.0.0.0:0 LISTENING
TCP 10.0.0.2:47705 208.197.??.???:1720 SYN_SENT
TCP 192.168.102.1:1720 192.168.102.222:3562 TIME_WAIT
TCP 192.168.102.1:1720 192.168.102.222:3565 ESTABLISHED
The private IP 192.168.102.222 is my internal client and the 208.197.??.???? is an external client with a static IP. Does this tell you anything? It looks to me that the ISA server is sending the call. I performed the netstat on the external client while the internal client was trying to make the call and it showed it was listening, but it never showed to receive any other packets on its IP interface.
I am guessing this has to do with routing on the the ISA server, but I have run out of ideas to try. I have the 3 IP address rules for Class A, B, and C configured to use the IP address of the ISA as a "Gateway or Proxy". I also have a Local route set up for 192.168.*.* addresses.
Help!
|
|
|
|
|
RE: NetMeeting only works when allowing ALL Protocols - 17.Apr.2003 5:16:00 AM
|
|
|
tshinder
Posts: 47490
Joined: 10.Jan.2001
From: Texas
Status: offline
|
Hi Weasle,
You should be able to connect to clients directly connected to the Internet using the H.323 Protocol Definition and the H.323 Gatekeeper. I haven't tested the H.323 components for a long time, and the last few times I did, both myself and the remote hosts were behind H.323 gatekeepers and we had all open Site and Content and Protocol Rules enabled.
HTH,
Tom
|
|
|
|
 New Messages |
 No New Messages |
 Hot Topic w/ New Messages |
 Hot Topic w/o New Messages |
 Locked w/ New Messages |
 Locked w/o New Messages |
|
 Post New Thread
Reply to Message
Post New Poll
Submit Vote
Delete My Own Post
Delete My Own Thread
Rate Posts |
|
Printable Version
