Hello... I have what i think is an interesting problem. That ...or i'm missing something entirely. I'm not completely green on LAMP, but i admit I have alot to learn.
I will go into detail with my problem, since it may get confusing otherwise:
I'm attempting to set up a cms for local use around the office, a makeshift intranet, so to speak. Our 'admin' area has 5 computers behind a router with the address ranges 172.16.xx.xx. A single line from this same router goes to the 'shop' area of my office, where i've installed another router occupying the 172.16.1.5 address of that range (static). Behind this second router, DHCP feeds 3 computers in my shop area with addresses in the 192.168.1.xx range. These 3 "shop" computers are thus on their own seperate LAN from the "admin" computers.
Hope I didn't lose anyone.
Here's the problem. I installed Xampp on 192.168.1.102 computer. Debian Linux machine, No problems. This computer is always on, and always occupies that address. I then installed a few cms's to test drive, namely Mambo and OsCommerce. These also have no problems, and I can access them beautifully from the "shop" LAN.
Now I want "admin" computers to see this stuff too... so I forward port 80 of the shop router (172.16.1.5) to 192.168.1.102.
I run to the admin area and get on a computer (172.16.1.7) and try to access my webserver in the shop.
There is a long one minute pause or longer, then only the text appears from either cms. The browsers hang while trying to load picture files from either cms. Funny thing is, the Xampp default page and all it's links work just fine. From the admin computers I point the browser to:
http://172.16.1.5/ -- accesses the default Xammp page - no problems
http://172.16.1.5/mambo -- hangs on picture files
http://172.16.1.5/catalog -- hangs on picture files
(both cms's show waiting for files from 192.168.1.102)
Is this a problem with the router's port forwarding (Linksys BEFW11S4),
or something that needs to be tweaked with apache? And why would Xampp's page and links work fine and not the cms's?
Keep in mind, any computer on the 192.168.xx.xx LAN can access everything with top speed by pointing to - http://192.168.1.102.
This is why i didn't think it was a directory permissions problem.
Sorry so long winded, but hope the detail helps..
thanks,
Duncan