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.

Introduction to Linux - A Hands on Guide

This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.

Hi,
I have two machines connected into LAN directly via crossover cable. One of them is running CentOS 4.2, the other is Windows XP Home Edition. They are set up for simple file sharing. Their IP addresses are manually assigned:

At CentOS, samba is installed but smb.conf has not been touched.
When I ping the local loopback at both machines, it works. Pinging their own IP addresses also works, but when I ping WinXP from CentOS (by the IP address), it shows no output unless I press Ctrl-C (and then follows statistics about packets sent, zero received and 100% packet loss).
What is to be done to make XP visible from CentOS?

Sorry but 169.254.0.0 is not a good idea for an IP Address...
1st of all change the IP's.
Let say Class C-Network so WinXP 192.168.1.1 and the centOS to 192.168.1.2
and the Netmask (Subnet) 255.255.255.0.
Then your ping will work if the no firewall is still blocking, and if its a real cross over cable. But if one of the systems has got a gigabit NIC you won't even need a crosscable cause crossing is one of the standard implementation of the gigabit standard. And if you want to share files you need Samba configured on your CentOS machine and in the XP Firewall the File and Printer Sharing enabled.

ok what happens if you ping from WinXP to CentOS?
and are you really sure that the Device is up in CentOS?
check with #system-config-network.
then check #system-config-security if the eth0 or whatever is listed as truthed interface?

Okay so you changed physical the NIC of the XP Computer. So there will be of course no static configuration anymore.
What are the manufactors of the NICs? And what is their vendor name?
How long is the cable your are using?
Did you ever thought about in spending some money in a cheap hub or switch and a simple patch cable. Total coast will be something around 15 bucks (less expensive to very expensive...)
Do you have any applications like VMWARE installed on any of your systems? ThirdParty Firewall Software like McAfee, Norton ?!

After changing IP address of the XP box, ping started working again, but only Xp-to-CentOS. And since you mentioned McAfee firewall, that reminded me that I actually have an express edition of a third-party firewall (McAfee) that came bundled with AOL software. The first time the firewall was mentioned I aimed straight to Windows firewall...
Opening Properties of this express edition, and lookie here: ICMP's were blocked and there was a log about bunch of denials to the IP address of the CentOS machine...
Now both machines ping each other without problem... sorry if I caused any inconvinience... would cold six-pack of beer suffice as an apology, odcheck?
P.S: Network cards are Lynksis and D-Link and cable is 3 meters long...