Not resolving from my LAN

I have a server set up in my home with CentOS 5. I put ZENcart on it, Got everything set up and working just fine. I was even able to get the Credit Card authorization to work. I could log into the admin page just fine from one of my other two computers on my LAN or from the server itself, and everything was working just great. Because I thought that the internet provider I had was too slow, I changed providers. I used to connect to the net through a Netgear Router, but now I have to use Qwest's Actiontec M1000 modem. I am told that my store looks just fine if you brows it from the net, but from my LAN, I am not getting any of the PHP stuff resolved, and can no longer brows to the admin login. The store acts the same, whether I brows to it from one of the other computers or even the server itself.
Can someone here give me a clue?

Just a little more info:

I've had to change the IP address of my server from 192.168.1.130 to 192.168.0.130. I hope I have done that right.
Seems funny though that I can't even brows to a page on the server it'self.
When I use the server to try to brows to http://localhost/, everything works fine for the html stuff on the initial page only. The PHP stuff doesn't resolve, and I can't get into the admin page. It just feels like addressing problems.

The computer you are NOT able to connect from probably has an internet server setting like that in XP Pro. Once installed it becomes its own localhost and will not look for any other.

dbltoe:

The computer you are NOT able to connect from probably has an internet server setting like that in XP Pro. Once installed it becomes its own localhost and will not look for any other.
Im not sure what your saying... When I am trying to brows to my store's home page, I'm doing it from the linux server that I have the store installed on, and I can't even get it to find anything past the initial page. I probably didn't explain it well enough the first time...

pfristoe:

I've had to change the IP address of my server from 192.168.1.130 to 192.168.0.130. I hope I have done that right.
Since your Zen Cart site is configured to use a "name" for the domain, and not the IP address itself, all computers which attempt to access it must be able to correctly resolve the domain name to the correct address.

If you changed the address of the server, then you also need to change the DNS entries in your router etc so that the domain name points to the new IP address.

Sometimes this is done in a "hosts" file on your PC. If you previously configured your hosts file with the old IP address, then you'll need to update that file with the new one.
If your hosts file does not contain the server's information (or if you've never heard of this and don't know what I'm talking about), then your computer network probably uses some other kind of DNS resolution system ... which you'll need to get your IT person to help you sort out.

My DNS is https://www.barterhouse.net which is pointing to 216.160.204.15, my static IP given by Qwest. My server on my own subnet is 192.168.0.130, and is named sixthstreet, one of three computers on my subnet called (wourgroup). My Linux computer 216.160.204.15 runing CentOS 5 with apache 2 is programmed to intercept requests through port 80, 25, and 433 when addressed to https://www.barterhouse.net (216.160.204.15). When I brows to my website from outside my subnet everything works great. When I try to go to 216.160.204.15 from inside the subnet I get the Qwest router. When I brows to the sixthstreet computer from inside the subnet, I get the website but it will not resolve the PHP stuff, and gets confused trying to access the subdirectories.

Sounds like you need to make sure that PCs on your subnet see "www.barterhouse.net" as 192.168.0.130 instead of listening to the main DNS server.

If your router is advanced enough to server its own DNS overrides, or if you're using a proxy that intercepts traffic, then you should be able to program either of those to serve up the right internal address for the name of your webserver.

Or, you could hard-code the domain name and its internal IP address into each of your subnet PCs via a hosts file. But then if you go and change the IP address again, you'll have to go change all those again ... putting you back in the situation you started with.
Best to fix it in your router/proxy, if that's where the problem originates.