From the home office in South Bend:
7/31/02
The server will be undergoing a physical move sometime on Monday, August 5. Unfortunately, the jack in the new room is on a different subnet than the current one. The net result is that, at a minimum, the server will be down for as much as an hour or two. However, if you changed the "eccp109.ini" file to hold the IP address of the server (instead of the name, erdos3.math.nd.edu), this is going to be a problem. It is yet another problem that I didn't foresee - there will be no machine here to give the clients "forwarding instructions". So you will either have to replace the IP with the host name and hope it resolves, or wait for the new IP to become known and replace the old one with the new. I will post the new hostname and IP when it is known (which probably won't be until I reconnect in the new office - it is hard to get a static IP here, and I don't think I could get one in time anyway (10 working days to process!).
With the volume of traffic that the server now has, I would expect that the host name (which will not change) should work within a matter of hours after the move. I know alot of folks couldn't get it to resolve the last time we had to move, but we do have much more traffic now so it should propogate out much faster, I hope. I'll post more when I know it, including a precise time for the disconnect/ reconnect, and the new IP after we reconnect.
7/31/02
The server will be undergoing a physical move sometime on Monday, August 5. Unfortunately, the jack in the new room is on a different subnet than the current one. The net result is that, at a minimum, the server will be down for as much as an hour or two. However, if you changed the "eccp109.ini" file to hold the IP address of the server (instead of the name, erdos3.math.nd.edu), this is going to be a problem. It is yet another problem that I didn't foresee - there will be no machine here to give the clients "forwarding instructions". So you will either have to replace the IP with the host name and hope it resolves, or wait for the new IP to become known and replace the old one with the new. I will post the new hostname and IP when it is known (which probably won't be until I reconnect in the new office - it is hard to get a static IP here, and I don't think I could get one in time anyway (10 working days to process!).
With the volume of traffic that the server now has, I would expect that the host name (which will not change) should work within a matter of hours after the move. I know alot of folks couldn't get it to resolve the last time we had to move, but we do have much more traffic now so it should propogate out much faster, I hope. I'll post more when I know it, including a precise time for the disconnect/ reconnect, and the new IP after we reconnect.