Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member

Can not get to a individual IP address on our WAN

We have a situation where two different systems with different IP addresses but on the same VLAN can not get to IP addresses on our corporate WAN. Each of these two systems was attempting to get to two different IP addresses. The only common element in this situation is the 3524 switch on which they are connected and of course the 3550 routers (HSRP configuration) and the WAN router. Other users on the same VLAN, as well as a different VLAN could get to the IP addresses on the WAN.

The problems were corrected by changing the IP address on each of the systems.

Could the 3524 switch cause this type of a problem? (Hunting for straws.)

  • Other Network Infrastructure Subjects
3 REPLIES
VIP Purple

Re: Can not get to a individual IP address on our WAN

Hello,

hard to say without seeing the actual configurations. In general, if a host on a VLAN cannot reach a specific IP address which the other hosts on the same VLAN can reach, there is something wrong with the host configuration. Since you say that your hosts worked well after changing the IP address, I would check for access lists, or ´simple´ things like wrong subnet masks or default gateways. Flushing the routing table on the hosts (route -f) sometimes works as well.

Regards,

Georg

New Member

Re: Can not get to a individual IP address on our WAN

Forgot to state that all our workstations are DHCP clients. Hoever flushing the routing tables is something that we did not try. Thanks for the suggestion.

New Member

Re: Can not get to a individual IP address on our WAN

Once again this problem has occurred on the same system. It appeared that the network database was corrupted (could not add a route to the route table) so we reset the database (using netsh [Windows XP]). That cleaned up the database issue but still could not ping an address on our WAN. Once again changed the system's address to a different address in the same subnet and everything is working again. Flushing the route tables with the command “route –f” did not work.

84
Views
0
Helpful
3
Replies
This widget could not be displayed.