Welcome to ISAserver.org

Internal NM can't call out. Ext. NM can call in.

Users viewing this topic: none

Logged in as: Guest

Printable Version

All Forums >> [ISA Server 2000 General] >> H.323 Gatekeeper >> Internal NM can't call out. Ext. NM can call in.

Page: [1]

Message

<< Older Topic Newer Topic >>

Internal NM can't call out. Ext. NM can call in. - 4.Nov.2003 8:39:00 PM

laserind

Posts: 4
Joined: 4.Nov.2003
From: Orange, CA
Status: offline

I wonder if someone can point me in a new direction with this......

I have read all the NM articles here, and configured GateKeeper. External NM client CAN call in when setting the "Use Gateway" and entering my ISA Server external IP. They can connect to me via Phone Number that I registered with in the GateKeeper.

I would like to call out to external NM client using IP, and from what I have read, you should be able to do this without a GateKeeper, but I can't get out regardless.

I tried Steve M. settings, though screens are different, without success. He states that "Internal clients will have to use NAT to the external IP", which is what the routing rule is supposed to do, isnt it?

It appears to me that when I enter an IP address that is registered with the GateKeeper, of course, it is just not doing the NAT to the external IP.

I am using SBS2000 running ISA and all the goodies installed.

TIA,

George L. Hicks

Post #: 1

Featured Links*

RE: Internal NM can't call out. Ext. NM can call in. - 10.Mar.2004 5:42:00 PM

imjack

Posts: 4
Joined: 18.Feb.2004
Status: offline

I have the same problem as this and wonder if anyone has resolved what we are doing wrong. When creating the routing rule, it is asking for an IP address to be added into it (this is not shown in the article By Steve Moffat). The problem I have with this is, the IP is not fixed, I am using dynamic DNS to take care of this.

When calling the FQDN using netmeeting, I am getting the error "bcd.abcd.com"is not registered with the gatekeeper

i would be grateful if someone could point me in the right direction

thanks
Mike

(in reply to laserind)

Post #: 2

RE: Internal NM can't call out. Ext. NM can call in. - 15.Mar.2004 5:51:00 PM

imjack

Posts: 4
Joined: 18.Feb.2004
Status: offline

OK, so I managed to get this working. In the IP part that is not shown in the article, assign a non public IP address, this then becomes the number that you call to initiate the connection. This is the number that is registered with the gatekeeper.

(in reply to laserind)

Post #: 3