thx director saab, let me explain a bit more 1. There is one server machine with two RJ45 (हो कि त्यस्तै के जाति हो, टेलिफोनको जस्तै तर अलिक ठूलो दूलोमा छिराउनी ) NICs. Of course, one is eth0, the other is eth1. 2. As the system hosts some internet stuff, eth0 is connected to a port which directly goes to the ISP. 3. The entire building is "hot" with wireless internet, so a wireless router snaps that in and distributes to other computers (which are not wireless-enabled) through a switch and RJ45 (?) cabling. On doing this, the internet connection is also shared but also we have an efficient and secured LAN alongwith. सिभिल ईन्जिनियरले कम्प्युटरको काम गरेसी त्यस्तै भद्रगोल हुन्छ। The "server" machine is also connected to the router because it has to "file-serve" the other janta-computers. This connectivity is thro the "eth1" in the server. 4. Sometimes, not always, when the server is reboot, the indicator lamp in the switch for the server's eth1 अलिक ढिलो पिलिक्क पिलिक्क गर्छ। That means there is sth wrong with eth1, i guess. But I can easily access the file-system of the server from the other jantas, which means eth1 is up. But if I try to access the machine from outside the LAN, i cannot, which means eth0 is down. Then, I suspect whether eth0 and eth1 are interchanged-kind-of-thing, so i do "ifconfig" : eth0 is down, eth1 is up, fine and doing its job. 5. If I go from Desktop>> Network Devices>> whatever and "up" the eht0 or simply command "ifconfig eth0/up" it works. for fun, if i did "ifconfig eth1/up" it says it failed to bring eth1 up but the thing is working fine. 6. This happened after i yum-med and did a few updates to get a dvd player/writer. 7. We have rather installed GRUB, but nothing is shown on the boot-log, i checked most of the things already. 8. The nepali font and unicode problem is in another machine also running FC3 and is just a workstation within the same LAN 9. I will try to dig into the boot-log again, weekend ma ta shiv_puja garnu parena? Thanks for ur interests Keep rolling...