Dual Boot Machine Fedora 5 / WinXP, XP messes up the IP addressing
Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Dual Boot Machine Fedora 5 / WinXP, XP messes up the IP addressing
I have a dual boot machine with FC 5 and also WinXP. When first installed, FC5 login screen shows the Correct IP address/Computer name.
Now, many of the linux programs I have installed depend on the IP address/computer name not being changed. When forced to occassionly use the WinXP, it is NOT possible to set the FULL IP address/name.
Then back to Fedora linux bootup time after having been on windows, and the fun begins. All of the sudden, the programs that depend on the accurate IP and names no long can find the correct info because winXP changed IP and names. Usually truncating or changing it completely.
Clamav depends on adresses that do not change. So do some of the other programs installed on the linux side. Is there some way to correct this from happening or preventing winXP from screwing things up?
Please help, and thank you for any help that can be given.
I have it set up as computer/ethernet to cable modem, to the internet. Using seamonkey browser. Setup is 'DHCP' But the cable company does not change that true IP address.
But windows rewrites parts of clamav, amavisd, http, and a few others and then the startup is royally screwed up. Because suddenly fedora can not find the localhost.localdomain so it assigns the changes that windows assigned in the mbr
i heard that some other peoples are having similar problem with ethernet. and their solution was that do not restart your computer when switching op systems, instead shutdown the pc and then run the op sys you want.
It's nearly impossible for Windows to rewrite parts of clamav, .... It might reformat your whole Linux partition by accident.
Maybe Windows sets certain registers in your network card and without a power cycle they may still be there when you boot Linux. This might even be a Linux driver bug (not resetting stuff to a known state).
As said by riizikaz, shutdown the machine before switching to Linux. If that does not help, powercycle. If that does not help, come back here.
Can you indicate what exactly changes? IP address? Hostname? clamav configuration file? etc etc etc
You use dhcp. Don't take for granted what the ISP says. Check the IP address after a boot to linux with the command ifconfig. Next boot to windows and check the address with ipconfig. Next back to Linux and check again.
Does the address change?
Dual Boot Machine Fedora 5 / WinXP, XP messes up the IP addressing
Quote:
Originally Posted by Wim Sturkenboom
It's nearly impossible for Windows to rewrite parts of clamav, .... It might reformat your whole Linux partition by accident.
Maybe Windows sets certain registers in your network card and without a power cycle they may still be there when you boot Linux. This might even be a Linux driver bug (not resetting stuff to a known state).
As said by riizikaz, shutdown the machine before switching to Linux. If that does not help, powercycle. If that does not help, come back here.
Can you indicate what exactly changes? IP address? Hostname? clamav configuration file? etc etc etc
You use dhcp. Don't take for granted what the ISP says. Check the IP address after a boot to linux with the command ifconfig. Next boot to windows and check the address with ipconfig. Next back to Linux and check again.
Does the address change?
Have already tried the power off and then switch to the next os. Even to the point of leaving the computer power cord unplugged from the wall. That works sometimes.
What gets changed is some of the entries in .conf files for some and then some of the bootup files for others. Linux is booting, loading, and then says can not find address < original address > using 127.0.0.0 instead. And then several programs start NOT functioning correctly. Will try some of the other suggestions and let you know what happens.
As said, first verify IP address after each boot. I have a dual boot here in an (MS) network. Under Windows, it always gets the samne address from the DHCP server. Under Linux it varies, usually the same as under windows but recently I had an occasion where that was not the case.
Maybe Windows sets certain registers in your network card and without a power cycle they may still be there when you boot Linux. This might even be a Linux driver bug (not resetting stuff to a known state).
As said by riizikaz, shutdown the machine before switching to Linux. If that does not help, powercycle. If that does not help, ?
I have 7 OS on my single HDD.(one of 'em is window)
took me days to examine the CONF
At FEDORA v1 time I found out that I loose 3c940 module after reboot. Could be win messing the hardware.
Your IP-address does not change, so that's a good thing (it also excludes a possible Linux bug). How do you check your computername in Linux?
Suggestions to solve the problem
1)
Configure all your programs to use the ip-address and not a computername.
or
2)
Add an entry in the file /etc/hosts
Code:
71.227.184.165 your_desired_computername
and configure the applications to use that name. If a program tries to resolve a computername, one of the places where it will look is in /etc/hosts and it will then use the associated IP-address.
PS 1)
The computername is something that's stored somewhere 'in the OS'. In linux it's stored in /etc/HOSTNAME (as far as I can figure out). In windows, it's probably somewhere in the registry (not sure).
PS 2)
I still don't believe that Windows changes it in Linux.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.