The LAN LED is Off. The OfficeConnect Remote 840 Manager Interface status indicates Ethernet interface is down.

The LAN cable is not connected.

Check that one end of the LAN cable is fully plugged into the LAN port. Check that the other end is fully plugged into the local LAN connection.

The LAN cable has been damaged.

Replace the cable with another LAN cable.

The MDI/X switch on the back of the unit is set for connecting Port 1 to a single workstation but the cable is connected to a hub (or vice versa).

Press the switch in to connect to a hub and out to connect to a workstation.

The IP Wizard does not find the OfficeConnect Remove 840 on the local LAN.

There is a LAN connection problem.

See "LAN Connection Problems".

The OfficeConnect Remove 840 already has an IP address.

Only unconfigured OfficeConnect Remote 840s are detected using the IP Wizard. If your OfficeConnect Remote 840 has a LAN IP address already assigned, it will not appear in the IP Wizard list.

The workstation does not have an IP address.

If the workstation is supposed to learn its address from the OfficeConnect Remote 840, check that the unit is set up in DHCP Smart Mode. If not, set to DHCP Smart Mode and reset.

If the workstation was booted before the OfficeConnect Remote 840, reboot the workstation now. If the workstation is supposed to have a specified address, configure the workstation and run IP Wizard again.

Your Web browser does not find the OfficeConnect Remote 840 using its LAN IP address.

There is a LAN connection problem.

See "LAN Connection Problems".

The OfficeConnect Remote 840 and the workstation are attached to the same LAN, but not assigned IP addresses from the same subnetwork.

Either:

1 . Set up a workstation to be on the same IP subnet as the OfficeConnect Remote 840. Then connect and use the OfficeConnect Remote 840 Manager.

2 . Use CLI to add an IP network over the Ethernet interface using an IP address from the same subnet as the workstation. Then connect and use the OfficeConnect Remote 840 Manager.

3 . Use the factory reset button on the back of the 840 to delete the configuration. For an unconfigured unit, use the IP Wizard to reassign a new IP address. For a unit using DHCP Smart Mode, connect using the IP Address 192.168.200.254.

The OfficeConnect Remote 840 address was entered incorrectly when the IP Wizard was used.

Use the factory reset button on the back of the 840 to delete the configuration. for an unconfigured unit, use the IP Wizard to reassign a new IP address. For a unit using DHCP Smart Mode, connect using the IP Address 192.168.200.254.

The Web browser does not find the OfficeConnect Remote 840 using its DNS name (DHCP Smart Mode in use).

There is a problem with the LAN connection.

See "LAN Connection Problems".

The workstation is on a different IP subnet from the 840's subnet.

Set the workstation IP configuration to automatically learn its IP address from the 840.

The DNS host configuration has been changed.

Connect to the OfficeConnect Remote 840 using the unit's IP address, 192.168.200.254 and correct the DNS information.

DHCP Smart Mode is not really in use.

Press the reset button on the back of the 840 while rebooting to delete the current configuration and select DHCP Smart Mode.

Unable to log in to the OfficeConnect Remote 840.

You did not enter a valid administration login name and password.

Use the system default login name root and password !root.

The unit has no login name or password defined.

Do one of the following:

1 . Use CLI to add an administration login profile.

2 . Restore the system default login by deleting the current configuration using the reset button on the back of the unit. If DHCP Smart Mode is used, the default name root and password !root are set for you.

If resetting to Unconfigured Mode, run the IP Wizard to assign an IP address and configure the default login name and password.

SDSL LED is Off. OfficeConnect Remote 840 Manager Interface Status indicates that interface atm:1/hdlc:1 is down.

WAN (modem) cable is not connected.

Check that one end of the WAN cable is fully plugged into the wall. Check that the other end is fully plugged into the SDSL port in the back of the OfficeConnect Remote 840.

WAN cable has been damaged.

Replace the cable with another DSL cable.

There is a problem at the other end of the SDSL connection that causes the SDSL negotiation to fail.

Contact your service provider.

SDSL LED is Off or goes On briefly then turns Off.

SDSL link is down.

Contact your service provider.

OfficeConnect Remote 840 Manager ATM status cell delineation fails and no idle cells are being received.

SDSL link is down.

Contact your service provider.

There is a problem at the central office equipment (the other end of the SDSL line) such that no idle cells are being transmitted or there is a corrupt line.

Report the problem to your service provider.

Remote network is not responding (e.g. to PINGs or the Web browser connection requests.)

LAN or WAN connection problem.

1 . See "LAN Connection Problems" and "WAN Connection Problems".

2 . Go to Monitor > Networks > Network Status to view more detailed problem, then take corrective action.

Incorrect Virtual Circuit (VC) information has been entered. Use the Monitor > ATM screen to observe ATM error counts. If the BadVPI or VDI error count is incrementing, the problem may be an incorrect VC identifier.

Check the VC information and correct as needed.

Network Service (RFC 1483 or PPP) on OfficeConnect Remote 840 is incompatible with that used on remote site ATM router.

RFC 1483 and PPP network service run above ATM. If you select PPP and RFC 1483 is running on the remote site router, you will not be able to successfully access the remote network. Change the network service to agree with the remote router network service.

The remote site profile may not be enabled. Check the Monitor> Remote Sites > Remote Sites Configured to see if the remote site status is ENABLED.

Enable the remote site profile.

If your Network Service is PPP, the PPP Authentication information may be incorrect. Check connection event log (Monitor > Events > Connection Event Log) to see if the PPP connection could not be established due to a PAP or CHAP mismatch.

Enter the appropriate PPP Username and Password in the remote site profile.

Remote network is not responding (e.g. to PINGs or the Web browser connection requests.)

Remote location may be off-line.

The machine you are trying to connect to may not be running or may be busy processing other requests. Try reaching another remote machine.

The remote network is responding inter-
mittently or not at all. Monitor > ATM shows ATM cell delineation successful but Hec sound is high.

There is a corrupt line causing the ATM data cells to fail the header error test.

Contact the service provider for verification. A lower speed connection may solve the problem.

The remote network is responding inter-
mittently or not at all. ATM cell delineation achieved but Monitor > Remote Sites > Remote Site Counters shows that many packets are being received with Bad CRC.

ATM cells are being dropped by a device in the path to the remote site.

Contact your service provider.

Accessing remote information is slower than expected.

The SDSL settings indicate that a slower baud rate than expected was negotiated for the downstream traffic.

Reset the SDSL link to cause re-negotiation through one of the following steps:

• If the OfficeConnect Remote 840 is accessible, disconnect the SDSL line for a few seconds.

• Save the current configuration and reboot.

  If a faster connection was not negotiated, contact your service provider. They may able to check the physical connection for excess noise which may be the reason the negotiated numbers are low.

Symptom

Possible Cause

Corrective Action

Remote IP network is not responding (ex., to PINGs or the web browser connection requests).

LAN or WAN connection problem.

See "LAN Connection Problems", "WAN Connection Problems", and "General Network Connection Problems".

IP Forwarding is turned off.

From the OfficeConnect Remote 840 Manager home page, access the Global > IP > IP Settings screen. Ensure that IP Forwarding is enabled.

PC or workstation does not have the OfficeConnect Remote 840 listed as a gateway.

Reconfigure the PC or workstation to use the OfficeConnect Remote 840's IP LAN address as its gateway.

Symptom

Possible Cause

Corrective Action

Some remote sites use the RIP protocol to advertise your IP address to other routers. It may take more than 30 seconds for the IP route to the OfficeConnect Remote 840 to be propagated throughout the remote network.

Wait 30 seconds and try to access remote site again.

IP routing table does not show a route to the remote network, indicating a configuration problem.

One of the following may solve the problem:

Remote WAN IP addresses are entered incorrectly. Check the addresses and reconfigure as needed.

RIP may be turned off. Set RIP to Listen mode to automatically learn routes to remote networks.

A static route (global config.) or framed route (remote site config.) is needed to reach the remote network. Add the route and check the IP routing table to confirm the entry.

No default gateway has been configured that would allow the OfficeConnect Remote 840 to automatically look for the remote network. Enable the default IP gateway option in the remote site profile.

Symptom

Possible Cause

Corrective Action

My video application does not run when Port Address Translation (PAT) is enabled.

Some video applications using UDP streaming have two connections, a TCP connection for control and a UDP stream for data. The TCP connection is initiated from the privately addressed workstation but the video stream may be initiated from the remote server. Because a mapping does not already exist for the UDP data stream, the data can not be mapped to a private address unless a static PAT port has been defined or the PAT default address is configured.

First verify the possible cause stated above is actually the problem. Set the Remote Site's PAT default address to your workstation's LAN address, then try to run your video application again. If it works, check to see if your video application allows you to specify a static UDP port. Microsoft NetShow allows you to configure a static UDP port in the Properties > Advanced screen. After setting a static port for the video application, you must add a corresponding static port entry on the OfficeConnect Remote 840. Set your Remote Site default PAT address to 0.0.0.0 before you try the static port.

If you cannot setup a static port on the Video application, check to see if the Video application allows you to specify TCP rather than UDP. TCP streams are typically initiated from the private side.

If you still are unsuccessful, the video application may be embedding address and port information within the data portion of the frame. If this is the case, consult your application vendor for possible workarounds.

Symptom

Possible Cause

Corrective Action

Remote IPX network is not responding (ex., can't find a Novell server).

LAN or WAN connection problem, or a general configuration problem.

See "LAN Connection Problems", "WAN Connection Problems", and "General Network Connection Problems".

IPX is not enabled over both the LAN and the WAN.

Check the Local Site > IPX and Remote Site > IPX screens and ensure that IPX is enabled on both interfaces.

IPX routing table does not show a route to the remote network, indicating a configuration problem.

One of the following may solve the problem:

Remote WAN IPX addresses are entered incorrectly. Check the addresses and reconfigure as needed.

RIP may be turned off. Set RIP to Listen mode to automatically learn routes to remote networks.

A static route (global config.) or framed route (remote site config.) is needed to reach the remote network. Add the route and check the IPX routing table to confirm the entry.

Symptom

Possible Cause

Corrective Action

Remote network is not responding.

LAN or WAN connection problem, or a general configuration problem.

See "LAN Connection Problems", "WAN Connection Problems", and "General Network Connection Problems".

Bridging is not enabled over both the LAN and the WAN.

Check the Local Site > Bridge and Remote Site > Modify screens and ensure that bridging is turned on over both interfaces and that the remote site is enabled.

The IP network is not responding because the OfficeConnect Remote 840 is trying to route IP packets, instead of bridging them.

Check the Global > IP > IP Settings screen and ensure that IP Forwarding is disabled.

The IP network is not responding because the LAN IP addresses are assigned on a different network than the remote address.

When bridging IP, the local network becomes part of the remote network and must be assigned addresses on the same network or sub-net.