3Com Version 4.3 Appendix B. Troubleshooting

Appendix B. Troubleshooting

Troubleshootingthe Telecommuting Module largely consists of checking the hardware (the Telecommuting

Module,the network connectors, ...) and checking the Telecommuting Module log. The log is usually an excellent

toolin ﬁnding out why the Telecommuting Module does not do what you wanted it to do.

Belowis some general advice to help you troubleshoot, almost regardless of which problem you have.

•Checkthat the events you look for are really logged (on the Logging Conﬁguration page).

•Checkthat the conﬁguration has been applied properly, either by applying it (on the Save/Load Conﬁguration

page)or by checking the Permanent Conﬁguration (on the Show Conﬁguration page).

•Checkthat you display the log you want to look for. The correct date and time (or no date or time) should be

ﬁlledin, the desired log entries should be checked on the righthand side of the page, and the three boxes

concerningwhich IP packets to show should be ﬁlled in accordingly.

•Checkthat the interface is turned on on the corresponding interface page.

•Checkthat the Telecommuting Module has a correct default gateway (on the Basic Conﬁguration page).

•Checkthat the client computer has a correct default gateway.

Whentrafﬁc is blocked and the reason given is Spoofed, there is a mismatch between the network that the

TelecommutingModule is conﬁgured for and the network that the client is conﬁgured for. The Telecommuting

Moduleregards an IP address as spoofed if it detects trafﬁc from that IP address on an interface where the IP

addressshould not be.

Anexample of a situation where this occurs is when you move a computer from one Telecommuting Module

interfaceto another without changing its IP address and netmask.

Beforegoing into the different error descriptions below, check that the SIP module is turned on and the

conﬁgurationapplied.

•Checkthat the SIP domain that the users try to register on is listed in the Local SIP Domains table.

•Ifyou do not use RADIUS authentication, check that the SIP user which tries to register is listed in the Local SIP

UserDatabase table.

•Ifyou do not use RADIUS authentication, check in the Local SIP User Database table that the SIP user which

triesto register is allowed to register from the network where the SIP client is located.

•Iflocal SIP authentication is used, check that the SIP user uses the correct password.

•Checkthat the SIP domain that the users try to register on is not listed in the Local SIP Domains table.

•Checkthat SIP authentication is not used. If you want the Telecommuting Module to perform SIP authentication,

makesure that the Telecommuting Module and the SIP registrar uses the same SIP realm.

•Ifthe client sends the REGISTER request to the Telecommuting Module itself and the Telecommuting Module is

supposedto redirect it to the registrar, check on the Routing page that this is conﬁgured correctly.

127