BCM400 v4 Remote IP handset issues

[option11newby]

Hi all,

BCM400 v4 (fully patched) . The only connected device on the site is a zyxel router for the vpn. When the engineer was on site and his laptop connected to the vpn he could ping the BCM, the router and all devices at the remote side.

On the remote side, we have again a zyxel router, 3 i2004 handsets, and an engineer with a laptop connection.

The engineer on the remote side can ping everything except the BCM.

From the BCM we can only ping the router and the laptop.

I seem to have missed something, any ideas?

Thanks in advance

NCSS, NCDS, NCTS

 

[MagnaRGP]

Do you have the a default gateway installed. Only pinging a router and laptop on the same LAN says that your gateway is either incorrect or missing.

 

[option11newby]

Thanks Magna.

Default gateway is in place as laptop from remote site can ping laptop on site with BCM and vice-versa.

Could it be a faulty Lan port on the BFT?


NCSS, NCDS, NCTS

 

[MagnaRGP]

So two laptops can ping each other....

If the BCM cannot ping a laptop at the other site, and it does not seem to respond to a ping from the laptop at the other site, this confirms what I have said. The BCM does not know how to find devices on another subnet.

Please post the LAN configuration of the BCM.

As to the LAN port being faulty, if it can talk to a local machine, it is not faulty.

 

[option11newby]

Lan1 192.168.1.100/255.255.255.0
Next hop 192.168.1.2
DHCP Disabled

Is this the information you require?

NCSS, NCDS, NCTS

 

[MagnaRGP]

What is 192.168.1.2? default gateway for the.1 subnet? What would the IP configuration on the laptop at that site be?

 

[option11newby]

192.168.1.2 is the IP address of the Adsl router

NCSS, NCDS, NCTS

 

[MagnaRGP]

So either the router/vpn is blocking the BCM's traffic or the BCM doesn't know how to find the subnet of the other side.

Those are really the only two options to check. Can the BCM ping a public IP? (72.14.205.99 =

http://www.google.com)

If so, it's VPN/firewall blocking. If not, it still could be VPN/firewall, but more likely it's configuration on the BCM.

 

[option11newby]

Magna,

From the BCM we can ping 72.14.205.99

As I am not a data person, the data engineer who attended site insisted it was the BCM at fault, as when he connected his laptop to the adsl router he could ping everything on the other end.

I have checked all the settings within the BCM with sites we have working with a similar scenario.

If it is the BCM, I cant seem to find out what I have missed.

Thanks for your input.


NCSS, NCDS, NCTS

 

[MagnaRGP]

So your BCM can ping the public internet and anything on it's local subnet, but your data guy says that because it can't see across a VPN tunnel that the BCM must be at fault?

Am I missing something? Let's bactrack.

Have you tried to use the remote i2004s? Do they register?

Main site = 192.168.1.0/24. Zyxel is the gateway at .1.2
What is the subnet at the remote site? For that matter what is the zyxel model number. Finally, what has your data guy got for local and remote networks on each of the zyxel routers?

Don't get me wrong, but I'm trying to wrap my head around something that seemingly defies the rules of IP.

 

[option11newby]

Thanks for your time Magna.

The IP handsets were register off the BCM before they were sent out.

They were set for DHCP/Partial to receive the IP address of the zyxel router. The S1 address is the BCM IP address/port 7000.

The subnet mask at the remote end is 255.255.255.0
The IP addresses on the i2004 handsets are 192.168.2.33, 34 and 35

In BCM monitor, it shows that they did not connect since last reboot. The IP handsets are just showing unable to connect to server.

We had an engineer at the remote end re-configure the IP handsets, but it seems they do not even hit the BCM.

As we have a lot of BCMs installed with the same setup, I have double checked the information in the other BCMs and the programming matches what is in this one.

I will be seeing our data guy tomorrow and get him to log into these routers to see if he can see my 'pings' from the BCM.

I will keep you updated on this.

Cheers


NCSS, NCDS, NCTS

 

[option11newby]

Magna,

Here is the update. The data guy disabled the firewalls on both of the adsl routers.

I advised him that from the BCM we could ping sites on the internet. We are both baffled. It looks as though there may be some corruption on the HDD? As it appears that when pinging the outside world it goes via the default gateway, but when trying to ping the other subnet it does not want to know.

We did a hard reboot of the BCM this evening and still the same scenario. We are now left with two options, firstly take a spare BCM with ip licences and connect to the adsl router on site A. If this works, then we may put in a new hard drive.

I will keep you posted on this one as you helped guide me to look at things I would not have thought of.

Thanks

NCSS, NCDS, NCTS

 

[MagnaRGP]

Check to see if there are any static routes configured in the BCM. Also, for grins, check the config on the second LAN port and make sure it's defaulted.

Could also try resetting LAN1 to default and then back to what you want it to be.

Finally, again for grins, remove your BCM from the LAN and ping it's IP address. It could actually be an IP confilct on the LAN. If no response, leave the BCM off the LAN and config your laptop with the same IP config as the BCM and try pinging back and forth across the tunnel.

 

[option11newby]

No static routes configured in BCM.

Lan2 is default at 10.10.11.1

Got a tech guy going out there later today, and will get him to try the options you mentioned.

NCSS, NCDS, NCTS

 

[Frankenherder]

Any update? i am having a similar problem.

Thanks
Matt

 

[option11newby]

Here is the update.

We installed new ADSL routers and connected to another BCM and got the same results. The next step, we disconnected all the IP handsets on the remote site and connected them one at a time.
The first two came up successfully, when we connected the third, it took the other two offline. We replaced the faulty IP handset and all sync'd up ok.


NCSS, NCDS, NCTS

 

[MagnaRGP]

Are you sure that the set is faulty? Maybe it was provisioned with incorrect IP information.

 

[option11newby]

Magna,

It was provisioned with the correct info. We got the engineers to default the handsets after de-registering them, and when this specific handset connected, it took the others off line.

NCSS, NCDS, NCTS