Subj : question
To   : Bob Seaborn
From : David Calafrancesco
Date : Fri Apr 11 2003 08:37 am

Bob Seaborn wrote in a message to David Calafrancesco:

 BS>       I'm about to give up on it altogether, and replace the server
 BS> with a newer box, hopefully a faster dual cpu system with more RAM
 BS> & HD available.  I was hoping that I could find a solution to this
 BS> perplexing problem to give us breathing room to be abkle to utilize
 BS> a slow/deliberate switchover to the new system, plus give me a
 BS> decent learning curve.

Then here is what you need to look at and consider for a smooth migration. 

Look at the services the machine is offering, ensure that each service is being 
directed to a specific hostname. For example, web services go to 
www.hostname.dom and file services go to ftp.hostname.dom, smtp.host... 
pop.host... etc etc. Once you have that part in place (and from what you said 
it is already there for at least web and ftp but I don't know what hostname you 
were using for the other services) then you can pick a part of the system and 
move it over to a new host. Once each service is it's own hostname, they can be 
directed to any physical system you may need to send it to via dns. A CNAME 
record is just fine for most of these (except the MX for the domain can't be a 
CNAME). 

You can you tell powerweb to turn off ALL web services, right? That would allow 
it to do the smtp/pop3 and maybe even ftp for a while as you build a new 
solution for the email & ftp services. 

If you can do that, then a very quick short term solution is to leave it in 
place while you build a new email solution, drop apache 1.3.25 into place for 
the web content, and you are back in business... total work required maybe an 
hour if you need to read up on apache configs, otherwise it is as long as it 
takes to get the package and unzip it and edit the httpd.conf file. 

Once you at least have apache up on the OS2 system and powerweb not talking 
http anymore, your probes for proxy will go away (eventually anyway) as soon as 
it is circulated that you are no longer an open proxy. 

That's your quickest path... shutdown web inside powerweb if you can, otherwise 
direct www.whatever to a different host. You can then shift the powerweb to an 
irregular port if you can't just shut it down entirely. Optimal would be a 
firewall software on the box that would stop all connections to the shifted 
port as a last resort. 

Dave Calafrancesco, Team OS/2
dave@drakkar.org

.... They got the library at Alexandria, they're not getting mine! 
--- 
 * Origin: Druid's Grove BBS - (845)/876-2237 (1:2624/306)

.