Re: User can't accept calls - window does not appear on screen

On Tue, 9 Aug 2005 20:51:35 -0600, Robbie wrote:

> Well I appreciate your reponse but I know for a fact it has nothing to do
> with NAT routers or firewall. The reason I know this is because we have over
> 3000 PC's in this company and we've seen this on 4 other PC's. The only way
> we've been able to fix it is to re-image the PC's. We set the PC's back to
> the same location and it works fine again.
>
> The only thing that is consistent with these PC's is that they are all
> laptops. One of the 4 had window 2000 installed. We also disable the
> firewalls on the XP machine.
>
> This is why I know it is PC related and nothing to do with the network.
> Might sound like a network but we've gone through here.

How are the calls being made?

I can only think of these possibilities (assuming NetMeeting is running
waiting for the call on the target machine and there is no interfering
network device):

- you are not calling the machine you think you are (the IP address used to
make the call is not the correct one). You could try a direct call --
determine the IP address of the machine (via the help -> about in
NetMeeting) and call directly to that IP address
- there is something on the machine blocking incoming calls -- tcp 1503 and
tcp 1720 are the two listening ports for NetMeeting - a local firewall,
IPsec setting could block incoming calls


> We've even moved the
> PC to a location where netmeeting is working and once we try calling one of
> these laptops, the caller doesn't see the call come in. He can connect, the
> calling window just doesn't appear.

The physical location of the device is possibly not the determining factor
-- the IP address of the device and default gateway would determine the
virtual location in the network. How are IP addresses assigned in the
network? Are the IP addresses in the problem machine determined using the
correct method.
.

Relevant Pages

  • Re: Setting up H323 IP telephony etc - was Re: [fw-wiz] Apples iSight and Firewalls
    ... > the firewall, or trusting that Checkpoint's protocol handler works nicely.. ... NetMeeting comes from Microsoft. ... neither You must read full of holes documentation or if You have not ... IMHO if You need "secure" network forget about NetMeeting into this ...
    (Firewall-Wizards)
  • Re: Net Meeting Help Please
    ... > I suspect the firewall in my router is blocking the ports needed for ... BTW - were you calling him? ... > To establish outbound NetMeeting connections through a firewall, ... & thus to *Receive* Incoming NetMeeting Calls, ...
    (uk.people.silversurfers)
  • Re: allow access to selected websites
    ... level in a small windows 2003 network? ... A firewall with a single sign-on applet that you install on each ... Calling an illegal alien an "undocumented worker" is like calling a ...
    (microsoft.public.windows.server.sbs)
  • Re: User cant accept calls - window does not appear on screen
    ... with NAT routers or firewall. ... calling window just doesn't appear. ... >> A user is running XP SP2, NetMeeting 3. ...
    (microsoft.public.internet.netmeeting)
  • Re: Remote Users - How do you handle them?
    ... clients can print to network printers without them having to be TS compliant. ... a terminal server for remote locations is the best method ... Once you get a firewall appliance for your main network you can also do ... Calling an illegal alien an "undocumented worker" is like calling a ...
    (microsoft.public.windows.server.sbs)