cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
232
Views
0
Helpful
1
Replies

Unix Server Not accessable from 3550EMI

SAM ANANDARAJAH
Level 1
Level 1

Hope you could help me,

I have a situation as follows:

3640 to WWW,fa0/0 conneted to 4506(L3).3550 EMI have a les connetions to HQ.

4506(l3)

main Hub site have a unix server LOCAL USERS CAN ACCES,these are connected via g0/1 g0/2 to 3550

On main sites users can access the unix nop problem.

4506 running eigrp /ospf .

from hub site new les to remote site,conneted via 3550 48 port emi.as a Trunk....and users in remote lasn have got the helper address.

from remote I can telnet to 4506 and 3550 and the rmote site 3550/ port).

when the user do traceroute it drops in between 4506 and 3550.but the dhcp address hbtained,dynamically.

question is ;why is the whole subets in remote site can not access the unix server,?

1 Reply 1

konigl
Level 7
Level 7

Can the remote site users access other systems on the main site network, that is, systems on the same subnet as the Unix server? Or do they just have a problem with the Unix server? If they can access other systems on the same subnet as Unix server, then Unix server is the problem (see suggestion 3 below).

Can remote site users get out to the Internet (WWW)?

I am not sure I understand your network design completely, but from what I read in your post here is what I would suggest:

1. Check the L3 switch at main hub site: specifically, look for an ip route that matches the subnet used at the remote site for users.

2. If the route is missing, then it is not being learned by EIGRP or OSPF. You can either put in static routes to the remote subnet, or on the remote site L3/router you can enable the routing protocols on that subnet's interface. (You probably do not have the user subnet listed under "router ospf ...." on the remote L3 device, so it is not being advertised on other subnets and learned by the L3 devices at the main site.)

3. Depending on how your network is set up, you may also need to tell the Unix server how to reach the remote subnet. It may be receiving traffic from the inside, and sending replies out to the Internet instead of back to an internal router.

I would need to know more details about your network, in order to give you more specific things to check. But this should get you started.

Hope this helps.

Review Cisco Networking for a $25 gift card