Listening 8080 but no access from outside

[southwestcrm]

We have ONE server that is running IIS and XAMPP Apache. Apache has been put onto Port 8080 so that there is no conflict with IIS on port 80. The server has two NICs. The first NIC is used for internal access within the firewall and the 2nd NIC is visible on the Internet. Port forwarding has been set up on the 2nd NIC so that 8080 should be visible externally.

the URL is accessible internally but I cannot get it to be seen externally.
Internally the URL looks similar to http://servername:8080/crmsystem
Externally the URL looks similar to http://internal.domainname:8080/crmsystem

httpd.conf has been set to
Listen 8080

We have tried
Listen <IP>:8080

The server is just not found over the Internet. I'm at a loss where to begin with this issue. It seems that Apache is only looking at the one internal NIC card and not the other. Is there anyone out there willing to help or has an answer?

Many thanks

[Nobbie]

>The server is just not found over the Internet.

You should provide us the NIC and the IP in order to check, if we can reach the server. If you are only checking from INSIDE the LAN if the OUTSIDE IP (NIC) is reachable, this may fail due to NAT problems of the router (it depends on the router).

If you replace

Listen 8080

by

Listen IP:8080

the IP MUST NOT(!) be the external WAN IP, but the internal LAN IP of the server (like 192.168.1.2).

>It seems that Apache is only looking at the one internal NIC card and not the other

I dont understand the meaning of that - what do you mean by "NIC", and by "internall NIC card" and what is "the other"? Usually, a NIC is a Domain name, not(!) a piece of hardware like a network card or similar. Seems you are mixing up some things, what makes it impossible to understand what you mean.

[southwestcrm]

Thanks for your help.
When I say NIC I am meaning "Network Interface Card"
Listen 192.168....:8080 was the IP address we were trying rather than the WAN IP address
The server has two network interface cards installed. One is used to connect to the internal lan. The other provdes remote access to the internal lan. I assumed port 8080 may somehow only be 'listening' to one of these network interface cards. please forgive my lack of technical knowledge. Does this help at all?

[Nobbie]

What is the ip/submask of the first network adapter, what is the ip/submask of the second adapter (please full specifications)? These two networks MUST NOT overlap, that does not work an a single pc.

Why do you use two different network adapters in one pc? Thats not necessary if you want to run different applications on different ports.

How are the network adapters physically connected? Do you have different routers?

[southwestcrm]

The IP addresses are 192.168.15.100/24 (External adapter) and 192.168.16.100/24 (Internal adapter).

The reason for two network adapters is that this is a Microsoft Small business server (2003) which runs as a two NIC configuration.

However apache should listen to its designated port on all network adapters by default.

[Nobbie]

You overlooked one question:

How are the network adapters physically connected? Do you have different routers?

>However apache should listen to its designated port on all network adapters by default.

Not if you specify "Listen IP:8080". Only if you ommit the IP.

[southwestcrm]

Thanks for your help....

There is only the one router and Apache is set to listen:8080
internet -> Draytek firewall/router -> SBS external NIC <SBS> -> sbs internal nic ->Internal Lan

[southwestcrm]

More info...

The server is an SBS2003 server setup with two network cards. (this is how an SBS server is designed to work)
The external network adapter has the IP 192.168.15.100
The internal adapter has the IP 192.168.16.100

We are port forwarding port 8080 from the firewall/router to the SBS external IP address.

Accessing the website on port 8080 from the internal network (192.168.16.xxx) works fine.

However any attempt to access the website on the IP 192.168.16.100:8080 fails.

We can access the SBS web services ok (RWW, OWA etc) the Xampp hosted website on port 8080 does not work.

I have VPN’d to the inside of the firewall and tested with the same result so this is not a firewall/port forwarding issue

Any more help would be appreciated

[Nobbie]

>There is only the one router and Apache is set to listen:8080

Only one router? You have two different network cards, with different IPs/submask, which results in two different LANs. Which card is connected to the router, and what is with the other card?

Is there any card physically NOT connected to any switch/router?

>The external network adapter has the IP 192.168.15.100
>The internal adapter has the IP 192.168.16.100

What do you mean by "external" und "internal" adapter? How is the "external" adapter connected to the "external world" (= www), how is the "internal" adapter connecte to the internal LAN?

>However any attempt to access the website on the IP 192.168.16.100:8080 fails.

The network adapter with this IP does have (as all adapters) an external plug (a so called RJ-45) - is this plug connected to any other device?

[TomL86]

here is an interpretation of the above description which hopefully makes it easier to understand for everyone who is not familiar with how SBS servers are configured with a dual NIC setup.

INTERNET ->
*public wan address* Draytek Firewall/Router *192.168.15.x* ->
*192.168.15.100* SBS *192.168.16.100
Internal Lan 192.168.16.0/24 this is where the client machines are located

its hard to describe without drawing a diagram but hopefully the above makes sense.
Each device is listed with the Ip addresses either side.

Rest assured this is all setup as it is supposed to be as it is normal to setup a SBS server with dual network cards.
hopefully this helps you explain the situation southwestcrm
Tom

[southwestcrm]

Thanks for your explantion Tom - a much better description!!

[Nobbie]

So, obviously 192.168.16.0/24 is an internal LAN, which is *not* connected to the internet. You cannot reach it from outside, so if you run Apache on 192.168.16.100, it cannot be accessed from outside.

There is no use to add a portforwarding from the router (which is connected to 192.168.15.0/24) to 192.168.16.100:8080, because the router *cannot* reach that address. It is not within the scope of 192.168.15.0/24

[TomL86]

apache should be listening on all network adapters on port 8080, so this includes 192.168.15.100, The router is forwarding all incoming traffic on port 8080 to this IP address. please ignore the internal network as we only concerned with makin the website available on 192.168.15.100

Nobbie, im well aware of how port forwarding and networking works. Apache however is not my strong point, assuming the httpd.conf is set to listen 8080 it should work across all network adapters /ip addresses? I guess another question to ask is are there any other settings that can affect which Ip addresses/ports that apache will listen on.

Tom

[Nobbie]

>The router is forwarding all incoming traffic on port 8080 to this IP addres

So you want Apache to be accessed/reached on 192.168.15.100:8080 and *not* on 192.168.16.100:8080 (as written above). It is very hard to help, if informations differs from one post to another.

Ok, I will assume the following:

a) 192.168.15.0/24 is connected via Router to the internet
b) Apache is running on 8080, all internal IPs. You might specify more precisely the Listen-Directive to "Listen 192.168.15.100:8080"
c) you have a portforwarding on your router, which forwards Port 8080 to 192.168.15.100

So far ok?

So you *should* have access to Apache via http://192.168.15.100:8080 from your LAN. Does that work?

[Nobbie]

I re-read your posts again:

Accessing the website on port 8080 from the internal network (192.168.16.xxx) works fine.

However any attempt to access the website on the IP 192.168.16.100:8080 fails.

Am I right that the above statement is a (very ugly and annoying) typo!? You meant 192.168.15.100 instead of 192.168.16.100? Is it right?