I'm sorry for posting this again, but not sure what heading to put it under. Anway this is a backup server, and I'm trying to make it the main server. The IP address are totally different, and the main server is no longer in existence. I need to check all the conf files to check to make sure all the address are right. Can someone help? More information below that I posted under networking. Thanks,
Big Dummy,
Kenny

Hi, everybody. Someone I know has a machine with Slackware 9.1.0 on it and he doesn't want to update anything in fear of something not being backwards compatiable. I have been yanking my hair out....well what's left anyway. I did the netconfig option...and set up everything...I am able to go to the internal ip address of that server. Of course, I ge a internal server error....and to email someone who designed the software. Can someone help me and tell me what other conf files I need to edit, and where they are? Where is the log file ...with the files that are accessed and loaded...then they might be easy to edit them. Of course, i tried various edit commands, but they don't work...not a valid program or file. I'm just trying to get this webserver up for him that can allow people to access the linux box with his ip address. Any help will be appreciated. Thanks in advance.
Big Dummy,
Kenny

It would help if you 1) used decent titles; 2) explained what the problem is, because what you've posted makes no sense; and 3) don't double post.

Well, basically, the problem is that i need to verify all the conf files to make sure they are set right on bootup to make this box a webserver with the program that is already installed. The httpd.conf file does not seem to be in the directory that it is supposed to be in. All i need to do is figure out. I need to know what files I need to edit or check to allow people across the internet to type in the IP address to access the information on this server. Right now, when I type in the network IP address I get an internal server error...and the Internet IP address I get nothing. I hope this makes better sense. Thanks.

Are the original machine and the new one the same distro and versions?
If so, how was the new machine created ie can you guarantee that both have the same software installed. If so, the conf files should be in the same places, in fact (if the old box is no longer being used) you can just copy the conf files over.

I'm not sure, the main server was kept somewhere else. This box hasn't been used in a while, and the guy who wants it up knows nothing. When I type in the network ip of the computer, it sends me to a page saying an internal server error. It's like it is being fowarded somewhere in a particular file. Since it doesn't exist anymore, that is probably why I get the internal server error. The other server I won't be able to have access to. I probably sound confusing like the other person said, but I'm confused myself. The software has to stay on there....and I'm afraid if I upgrade the Slackware 9.1.0 it'll be overwritten or the program won't work.

Look, computers are not magic.(!) You're going to have to explain to this 'friend' that if he wants this done (at all, never mind correctly) you're going to need full (root) access to both systems.
Ideally, you'd clone one to the other using some kind of backup or rsync system.
Sorry if this sounds harsh, but (imho) otherwise, you've got no chance of doing this.
Good luck.

It sounds like you're trying to move webservers? Basically the post above explains what you need. You're going to want access (not necessarily root) but at least permissions on the directory where your httpd.conf is and your httpd logs on both servers. Without this, you're project is near impossible.

You also will want ftp (or at least sftp) access to both servers. You're also gonna want to know what version of apache or otherwise that you're working with on both servers. It is not uncommon for different builds to end up with the .conf or executable files in different directories.

Lastly, "Internal server error" can mean alot of different things and you're probably going to want to check your logs to figure out exactly what is causing this error.

If you can get this information, and post some of it (please cut out hostnames/ips though) we should be able to help quite a bit more.