HI!
I have a problem which has suddenly come up. I am having two computers on LAN. One is a dual boot with Windows XP and Scientific Linux 5.1 (32 bit). The other was having Fedora Core 9 (64 bit). Both were working fine. For some reason, I had to change 64 bit Linux to 32 bit Linux. I installed Scientific Linux 5.1 (32 bit) which was not giving any problem in the dual boot machine. But to my surprise, the eth0 is not being recognized on this machine (where I have installed 32 bit Scientific Linux in place of 64 bit Fedora Core 9). When I give the command /sbin/ifconfig -a, I get the output of the following interfaces :

lo
sit0
veth0
veth1
veth2
veth3
vif0.1
vif0.2
vif0.3
virbr0
xenbr0

but nothing of eth0. Assuming that veth0 would be same as eth0, I tried to assign static IP to the machine as follows :
Made a script file :
/etc/sysconfig/network-scripts/ifcfg-veth0. Its contents are :

DEVICE=veth0
BOOTPROTO=static
BROADCAST=XXX.XXX.XXX.255
IPADDR=XXX.XXX.XXX.XXX
NETMASK=25.255.255.0
NETWORK=XXX.XXX.XXX.0
ONBOOT=yes

The contents of the file : /etc/sysconfig/network are :

NETWORKING=yes
NETWORKING_IPV6=no
HOSTNAME=domain
GATEWAY=XXX.XXX.XXX.255

When I start the network by using :
/etc/init.d/network restart , I get the following Output :

Shutting down interface veth0: [ ok ]
Shutting down loopback interface: [ ok ]
Disabling IPV4 packet forwarding: net.ipv4.ip_forward = 0
[ ok ]
Bringing up loopback interface: [ ok ]
Bringing up interface veth0: RTNETLINK answers : Invalid arguement
[ ok ]

By this, the network between the two machines is not established. Please help me to solve this problem. Thanks in advance.

I have read a post somewhere that ms can lock your ethernet....going into control panel and change setting

can't quite find link yet but its a microsoft setting

still can't find the original info but here is how to change your settings according to ms

http://support.microsoft.com/kb/306947/en-us
http://support.microsoft.com/kb/814156/en-us
http://support.microsoft.com/kb/316276/en-us

please post back if this WAS not the issue and can you confirm if you have made any changes to hardware or bios

Dear Mr. Aus9,
Thanks for the reply. But in my case, eth0 is not being recognized on the machine which has only Linux (ie. the particular machine on which eth0 is not being recognized is not dual boot). Now when I again re-installed the Scientific Linux on this machine from scratch, same problem persists. I have not made any changes to the hardware or bios. Wondering now whether it is a hardware problem or software problem... eth0 is being recognized by SL on dual boot machine, while eth0 was being recognized on this machine previously when I was working with 64 bit Linux. Hoping to get solution to this problem soon. Thanks in advance...

maybe you could consider your network is the issue.

I assume its this

ms/linux has eth0-------------------------> internet
|.......ip 192.1.x.y or 10.1.x.y
|
v
linux only has eth1 ip 192.1.x.y+1 etc

2) Making changes can be bad when you are trying to troubleshoot.

3) so on the current dual boot....do you have any issues with internet?
4) on current dual boot can you ping your other computer.

they can not both be on the same address. I assume you know that?