Just a sample of the Echomail archive
Cooperative anarchy at its finest, still active today. Darkrealms is the Zone 1 Hub.
|    WIN95    |    Chat about Windows 95, 98, ME systems    |    13,597 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 11,649 of 13,597    |
|    Wilfred van Velzen to Ed Vance    |
|    Re: IP Address Changes-Why?    |
|    21 Feb 15 13:13:11    |
      Hi,              On 2015-02-20 23:35:00, Ed Vance wrote to All:        about: "IP Address Changes-Why?":               EV> Usually this XP MCE SP3 pc              Hey! This is the Win95 area. Get out of here with your XP questions! ;-)               EV> gets an IP Address of 192.168.1.100 and the Wallwatcher and Getlog        EV> programs work just fine.               EV> The other day the IP Address changed to 192.168.1.101 and Wallwatcher        EV> and Getlog hasn't wanted to work since.               EV> I have had this problem before and it was usually because I left the        EV> Cat-5 cable on the Vista pc connected and had turned the Vista pc on        EV> first, and it grabs the Dot One Hundred IP Address and when I turned on        EV> the XP pc later it gets a different IP Address.               EV> So I thought I fixed that by always making sure the Cat-5 wire to the        EV> Vista pc isn't connected before I turn the XP pc on.               EV> I have a BEFSX41 router that is connected to the DSL Modem and the XP        EV> pc, and I have been turning on the DSL Modem before turning on the        EV> router, then waiting 5 minutes for the LEDs to settle down before        EV> turning on the XP pc.               EV> I have been wandering through XP Help and Support pages to see if there        EV> was a way to always make the XP pc use the DOT One Hundred IP Address        EV> but all I could find was that I could fix the IP Address but Not To Do        EV> It because it was recommended to keep the DNS setting set to Automatic        EV> on the page I read about how to fix the IP Address.              I think this advice is wrong. If you run services on a pc, you better set the       IP configuration to static. Use an IP number outside the DHCP range which       apparently starts with 100 on your router. So 192.168.1.10 could be a good       candidate. The subnet mask would be 255.255.255.0. The default gateway and       Prefered DNS server should be copied from your current configuration. (You       know where to look for those?)              If you have made special adaptations to your routers/firewall configuration to       point to the .100 address, of course you have to change those to the new IP       address.              I don't know anything about the Wallwatcher and Getlog programs, but maybe       they also need to be told to use the new address. Or maybe just reboot after       the IP configuration change, will fix this automagically?              Does this make any sense to you?                     Bye, Wilfred.                     --- FMail-W32-1.69.1.95-B20140716        * Origin: Native IPv6 connectable node (2:280/464)    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca