Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

The scene:

  • There are two subnets
  • Network A is via router
  • There are two hosts, host A1 on and A2 on
  • Both A1 and A2 have only one NIC, and none of them are directly on the B network.
  • Both A1 and A2 can see the outside world fine, and can also be reached from outside.

Network B is, also via router (same as A). A web server B1 is on

The problem:
The web server B1 can be reached by host A2 but not A1. Why is that?

Could it be that the router is missing something or is the problem with host A1?

share|improve this question
Can you post the routing table of the router and 1-1 host from each network ? – Gabor Vincze Mar 9 '12 at 7:14 can't be the router for the systems in subnet B.

What is server B1 using as default gateway ?

I assume it is and that ought to be an interface on that same router.

If it works for one host in A and not for the other my first guess is a firewall or access control list getting in the way somewhere.

That could be on the router, on server B1 or even on client A1 itself

Routing table issues seem unlikely as A2 can get through so some routing is working. (It could be that the router has static routes for individual ip-addresses in stead for routes for the whole subnets. It's quite rare to do this, but not impossible so you better check just to make sure.)

share|improve this answer
I also thought it seemed odd that is the router for subnet B! But what if the router for B is routing for both subnets A and B? Am I correct that the router must have two IPs, one for each NIC, so (for subnet A) and (for subnet B). Is that all that is needed? I don't have access to the router, so I am only advising. I have a feeling it is either a firewall rule, or perhaps as you say a static route. – imse Mar 9 '12 at 15:40
You are correct. It needs both ip-addresses. And it must be configured to actually route traffic between them. – Tonny Mar 9 '12 at 22:32

Connectivity checklist:

  1. Can B1 be pinged from A1? Vice-versa?
  2. Examine routing table from A1
  3. Examine routing table from Router
  4. Examine routing table from B1
  5. Examine firewall (if any) on B1
share|improve this answer
1: Yes 2: dev eth0 proto kernel scope link src default via dev eth0 3: don't know (I'm allowed no access) 4. see (3). (5) see (3). – imse Mar 9 '12 at 15:35

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.