VINES Clients Cannot Communicate with Servers over Router

Symptom: Clients cannot connect to VINES servers over one or more routers. Clients might or might not be able to connect to servers on their directly connected networks.

Table 13-1 outlines the problems that might cause this symptom and describes solutions to those problems.

Table 13-1 VINES: Clients Cannot Communicate with Servers over Router

Possible Problem Solution

Router interface is down Step 1 Use the show interfaces exec command to check the status of the router interfaces.

Step 2 If the status line indicates that an interface that should be up is

"administratively down," use the no shutdown interface configuration command on the interface.

Refer to the troubleshooting chapter that covers the media type used in your network.

Hardware or media problem For information on troubleshooting hardware problems, refer to the troubleshooting chapter that covers the media type used in your network.

Addressing problem Step 1 On a serverless segment, use the show vines route exec command to make sure the router is seeing server network layer addresses.

Step 2 If the router is not seeing server addresses, make sure that the server and router addresses are correct. To change the address, use the following syntax:

vines routing [address | recompute] Syntax Description:

• address (Optional)—Network address of the router. You should specify an address on a router that does not have any Ethernet or FDDI1 interfaces. You can also specify an address in the unlikely event that two routers map themselves to the same address.

• recompute (Optional)—Dynamically redetermines the router's network address.

VINES metric value is not

Step 1

Use the show vines interface exec command to check the status of VINES

specified

interfaces on the router. Make sure all VINES interfaces have the

vines metric interface configuration command configured. The metric

command enables VINES processing on the interface.

Step 2

If the vines-metric interface configuration command is not configured on

the interface, specify the command for the interface.

Configure the vines metric based on whether the interface is LAN or

WAN connected. Suggested metrics for LAN and WAN connections

follow:

• Ethernet and 16-Mbps Token Ring: vines-metric 2

• 4-Mbps Token Ring: vines-metric 4

• T1 line: vines-metric 35

• Other WAN link: vines-metric 45

VINES: Clients Cannot Communicate with Servers over Router

Possible Problem

Solution

Missing vines serverless or vines arp-enable commands

A network that does not have an attached server must be configured with the vines serverless broadcast and vines arp-enable router configuration commands.

Note: These commands are enabled by default in Cisco IOS Release 10.3 and later.

Step 1 Use the show running-config privileged exec command on routers attached to networks with no VINES servers attached. Look for vines serverless and vines arp-enable router configuration commands entries.

Step 2 If both the vines serverless and the vines arp-enable commands are not present, specify the commands for router interfaces in serverless networks.

Syntax:

The following syntax is required to enable vines serverless: vines serverless [dynamic | broadcast]

Missing vines serverless or

Syntax Description:

vines arp-enable commands

• dynamic (Optional)—Forward broadcasts toward one server only if

there are no servers present on this interface.

• broadcast (Optional)—Always flood broadcasts out all other router

interfaces to reach all servers.

Syntax:

The following syntax is required to enable vines arp-enable:

vines arp-enable [dynamic]

Syntax Description:

• dynamic (Optional)—Responds to ARP2 and SARP3 requests on this

interface only if there are no other VINES servers present.

Misconfigured access list

Step 1

Misconfigured access list

Step 1

Step 2

Step 3

Use the show vines access-list privileged exec command on routers in the path from source to destination. This command shows whether there are access lists configured on the router.

Disable all access lists configured on the router using no vines access-group commands.

Test the connection from the client to the server to see whether connections are now possible. If the connection is successful, an access list is blocking traffic.

Step 4 To isolate the problem access list, apply one access list statement at a time until you can no longer create connections.

Step 5 When the problem list is identified, alter it so that necessary traffic is allowed to pass. On a serverless segment, make sure that well-known ports 0x06 (VINES file service) and 0x0F (StreetTalk) are not filtered. Configure explicit permit statements for traffic you want the router to forward.

Step 6 If problems persist, continue testing for problem access lists on all routers in the path from source to destination.

1 FDDI = Fiber Distributed Data Interface

2 ARP = Address Resolution Protocol

3 SARP = Sequence Address Resolution Protocol

Was this article helpful?

0 0
The Ultimate Computer Repair Guide

The Ultimate Computer Repair Guide

Read how to maintain and repair any desktop and laptop computer. This Ebook has articles with photos and videos that show detailed step by step pc repair and maintenance procedures. There are many links to online videos that explain how you can build, maintain, speed up, clean, and repair your computer yourself. Put the money that you were going to pay the PC Tech in your own pocket.

Get My Free Ebook


Post a comment