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

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

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. 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.

Oh well, once aigains thanks.

Robbie

"Brian Sullivan" <briansullivan@xxxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:108wz72jdhacz.1pjevzu2ovnxc.dlg@xxxxxxxxxxxxx
> On Tue, 9 Aug 2005 07:21:43 -0600, Robbie wrote:
>
>> A user is running XP SP2, NetMeeting 3.
>>
>> When someone tries to call to the user PC, one can see the phone calling
>> (ringing) the user. However, the user on the other end does not see the
>> person dialing in order for him to accept the call. The small window
>> showing
>> the phone ringing in order for him accept does not appear on the screen.
>
> How are you making this call? Are you sure you are calling the correct
> computer?
>
> Is the called computer behind a router or border firewall and the caller
> not?
>
>>
>> I've removed and re-installed netmeeting and that didn't help. I've moved
>> the PC to anonther network port where I know it works and I still have
>> the
>> same problem. I have isolated the problem to the PC.
>
> If the problem is truly the PC (I am guessing though that wherever you
> moved it too is behind a different router so that the problem is still
> that
> the user is behind a NAT and not reachable)-- then the only thing I can
> think that might be an issue is a local software firewall blocking the
> incoming call. Is NetMeeting set as an "exception" in the XP SP2
> firewall(it would have to be to allow incoming calls)?
>
>
>>
>> The user appears on the directory and he can call anyone and the other
>> person accepts calls with no problem.
>>
>> Only when they call him, he can't accept calls. The windows that appears
>> allowing him to accept calls does not appear on the screen.
>>
>>
>
> The most likely cause is that the called computer is behind a NAT router
> or
> firewall of some kind and cannot be called. A local firewall not
> configured
> to allow NetMeeting server or exception access would have a similar
> affect.


.

Relevant Pages

  • Re: User cant accept calls - window does not appear on screen
    ... > with NAT routers or firewall. ... > This is why I know it is PC related and nothing to do with the network. ... I can only think of these possibilities (assuming NetMeeting is running ... - you are not calling the machine you think you are (the IP address used to ...
    (microsoft.public.internet.netmeeting)
  • 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: Should my SBS be behind my firewall or should it function as the f
    ... they make simple NAT routers that I ... you either want a true firewall appliance or I prefer ... In either situation you want SBS to handle DHCP and DNS. ... I need to get the Server on the internet. ...
    (microsoft.public.windows.server.sbs)
  • Re: Server sending spam
    ... Most NAT Routers have a logging function, in case the OP doesn't have a ... The log should shot the TCP 25 connection outbound and then the IP ... A real firewall could also be set to BLOCK outbound SMTP TCP ... Calling an illegal alien an "undocumented worker" is like calling a ...
    (microsoft.public.windows.server.sbs)
  • Re: Norton Internet Security 2005 Personal Firewall slows down Windows XP startup
    ... there's a whole new line of NAT routers on the market ... It doesn't appear that way, in fact, once he learned it wasn't a firewall ... :> I say NAT routers offer some firewall features ... :> have'nt learned a new approach in years and always suggesting the unnessary. ...
    (comp.security.firewalls)