Discussion:
Cant ping windows network card, but can ping the linux card..
(too old to reply)
Tor Harald Thorland
2004-09-13 06:56:52 UTC
Permalink
Hi,

I have tryed to setup a network with a couple of PC's.
The linux box has 2 NIC's one with static IP, connected to a DSL line. (Internet working)
The other card has a static IP adress of 192.168.132.1
The windows XP box has IP 192.168.132.2
The windows box can ping the fedora core 2 pc nicely, but the fedora box can't ping the windows box..!
Any suggestions? Anyone who can give me some help in solving this and get the XP box on the net.

THT
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.fedoraproject.org/pipermail/users/attachments/20040913/63178f98/attachment.html
Edward
2004-09-13 07:13:28 UTC
Permalink
Post by Tor Harald Thorland
Hi,
I have tryed to setup a network with a couple of PC's.
The linux box has 2 NIC's one with static IP, connected to a DSL line. (Internet working)
The other card has a static IP adress of 192.168.132.1
The windows XP box has IP 192.168.132.2
The windows box can ping the fedora core 2 pc nicely, but the fedora box
can't ping the windows box..!
Any suggestions? Anyone who can give me some help in solving this and
get the XP box on the net.
You running a firewall on the XP box connection?

Regards,
Ed.
Tor Harald Thorland
2004-09-13 07:28:29 UTC
Permalink
Post by Edward
Post by Tor Harald Thorland
Hi,
I have tryed to setup a network with a couple of PC's.
The linux box has 2 NIC's one with static IP, connected to a DSL line.
(Internet working)
The other card has a static IP adress of 192.168.132.1
The windows XP box has IP 192.168.132.2
The windows box can ping the fedora core 2 pc nicely, but the fedora box
can't ping the windows box..!
Any suggestions? Anyone who can give me some help in solving this and
get the XP box on the net.
You running a firewall on the XP box connection?
Regards,
Ed.
The firewall is Off..
I got this answer when I ping it.
[tortho at localhost tortho]$ ping 192.168.132.2
PING 192.168.132.2 (192.168.132.2) 56(84) bytes of data.
Post by Edward
From 192.168.132.1 icmp_seq=0 Destination Host Unreachable
From 192.168.132.1 icmp_seq=1 Destination Host Unreachable
THT
Paul Howarth
2004-09-13 07:56:37 UTC
Permalink
Post by Tor Harald Thorland
I got this answer when I ping it.
[tortho at localhost tortho]$ ping 192.168.132.2
PING 192.168.132.2 (192.168.132.2) 56(84) bytes of data.
Post by Edward
From 192.168.132.1 icmp_seq=0 Destination Host Unreachable
From 192.168.132.1 icmp_seq=1 Destination Host Unreachable
What's the output of:

ifconfig -a
netstat -rn

Paul.
--
Paul Howarth <paul at city-fan.org>
PFJ
2004-09-13 08:17:26 UTC
Permalink
Hi,
Post by Paul Howarth
Post by Tor Harald Thorland
I got this answer when I ping it.
[tortho at localhost tortho]$ ping 192.168.132.2
PING 192.168.132.2 (192.168.132.2) 56(84) bytes of data.
Post by Edward
From 192.168.132.1 icmp_seq=0 Destination Host Unreachable
From 192.168.132.1 icmp_seq=1 Destination Host Unreachable
ifconfig -a
netstat
Okay, can the linux box ping to the outside world and can the Win32 box
ping to the outside world. If you're going through a router, what is the
IP address of the router (mine is 192.168.2.1) and can that be pinged
from both machines? Are you going directly from machine to machine and
if so, are you using a twisted lead or a straight lead (twisted are the
one you normally have from machine to network and won't work machine to
machine)?

Are you running a firewall on either/both machine(s)?

Personally, I would do this (assuming you're on a router)

1. Find the IP address of the router (look at the user guide)
2. Disable all firewalls and disconnect the router to the outside world
3. Ensure that all firewalls are off on the router
4. From the linux box, ensure the NIC is working (/sbin/ifconfig eth0
will let you know, you will get an IP address [192.168.2.100 say])
5. If you don't get an IP address, /sbin/ifup eth0. If that fails, /
sbin/lsmod - see if the network driver has been loaded. If it hasn't /
sbin/modprobe <name_of_driver>. Then try /sbin/ifup eth0. If it still
fails, there is a problem with the NIC. If it works and you don't have
an IP for the card, try a new cable, /sbin/ifdown eth0 then /sbin/ifup
eth0. If there is still no IP address, you will need to test the line
from the NIC to the router.
6. If you do get an address, see if you can ping the router. Assuming
you can ping the router (which indicates all the connections, leads and
NIC is happy), repeat for the Windows box.
7. If everything is happy with the windows box, you should be able to
ping either box. A simpler test is to run vsftpd on the linux box and
see if you can ftp onto it. Why is that simpler? Well, some software on
the Win32 side will stop the ability to ping.
8. If you can go from machine to machine, reconnect the router to the
outside world and see if you can either ping or ftp to a remote site. If
you can't, then it is probably a DNS problem (fire up neat, switch off
get IP dynamically and enter your ISPs DNS, reactive eth0 and try
again).
9. On one machine at a time (I'd go linux first), re-enable any
firewalls you have *slowly* until something breaks.

That's the nice trouble shooting way.

TTFN

Paul

P.S. Sorry if this has been covered, I've not followed the thread.
--
"If I face my God tomorrow, I can tell Him I am innocent.
I've never harmed anyone. I have cheated no one.
I have deceived no one. I have hurt no one.
Except myself. And that He will forgive me." - Hans Holzel
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : http://lists.fedoraproject.org/pipermail/users/attachments/20040913/b2b4efc5/attachment.bin
Jeff Vian
2004-09-13 08:43:55 UTC
Permalink
Post by PFJ
Hi,
Post by Paul Howarth
Post by Tor Harald Thorland
I got this answer when I ping it.
[tortho at localhost tortho]$ ping 192.168.132.2
PING 192.168.132.2 (192.168.132.2) 56(84) bytes of data.
Post by Edward
From 192.168.132.1 icmp_seq=0 Destination Host Unreachable
From 192.168.132.1 icmp_seq=1 Destination Host Unreachable
ifconfig -a
netstat
Okay, can the linux box ping to the outside world and can the Win32 box
ping to the outside world. If you're going through a router, what is the
IP address of the router (mine is 192.168.2.1) and can that be pinged
from both machines? Are you going directly from machine to machine and
if so, are you using a twisted lead or a straight lead (twisted are the
one you normally have from machine to network and won't work machine to
machine)?
Not true.

Standard ethernet cable is straight thru and is used from machine to
switch/hub. Crossover cables (which you refer to as twisted leads) are
required to go directly from NIC to NIC without using a hub/switch
between.
Post by PFJ
Are you running a firewall on either/both machine(s)?
Personally, I would do this (assuming you're on a router)
1. Find the IP address of the router (look at the user guide)
2. Disable all firewalls and disconnect the router to the outside world
3. Ensure that all firewalls are off on the router
4. From the linux box, ensure the NIC is working (/sbin/ifconfig eth0
will let you know, you will get an IP address [192.168.2.100 say])
5. If you don't get an IP address, /sbin/ifup eth0. If that fails, /
sbin/lsmod - see if the network driver has been loaded. If it hasn't /
sbin/modprobe <name_of_driver>. Then try /sbin/ifup eth0. If it still
fails, there is a problem with the NIC. If it works and you don't have
an IP for the card, try a new cable, /sbin/ifdown eth0 then /sbin/ifup
eth0. If there is still no IP address, you will need to test the line
from the NIC to the router.
6. If you do get an address, see if you can ping the router. Assuming
you can ping the router (which indicates all the connections, leads and
NIC is happy), repeat for the Windows box.
7. If everything is happy with the windows box, you should be able to
ping either box. A simpler test is to run vsftpd on the linux box and
see if you can ftp onto it. Why is that simpler? Well, some software on
the Win32 side will stop the ability to ping.
8. If you can go from machine to machine, reconnect the router to the
outside world and see if you can either ping or ftp to a remote site. If
you can't, then it is probably a DNS problem (fire up neat, switch off
get IP dynamically and enter your ISPs DNS, reactive eth0 and try
again).
9. On one machine at a time (I'd go linux first), re-enable any
firewalls you have *slowly* until something breaks.
That's the nice trouble shooting way.
TTFN
Paul
P.S. Sorry if this has been covered, I've not followed the thread.
Tor Harald Thorland
2004-09-13 09:47:10 UTC
Permalink
Thanks for all the quick answers, I'll found a virus scanner with a firewall
(sorry) that maby is the problem.
I'll check everything out when my other problem with the machine not boot
ing is fixed :-(
Everything that can be messed up is messed up today!!

THT
----- Original Message -----
From: "Jeff Vian" <jvian10 at charter.net>
To: "For users of Fedora Core releases" <fedora-list at redhat.com>
Sent: Monday, September 13, 2004 10:43 AM
Subject: Re: Cant ping windows network card, but can ping the linux card..
Post by Jeff Vian
Post by PFJ
Hi,
Post by Paul Howarth
Post by Tor Harald Thorland
I got this answer when I ping it.
[tortho at localhost tortho]$ ping 192.168.132.2
PING 192.168.132.2 (192.168.132.2) 56(84) bytes of data.
Post by Edward
From 192.168.132.1 icmp_seq=0 Destination Host Unreachable
From 192.168.132.1 icmp_seq=1 Destination Host Unreachable
ifconfig -a
netstat
Okay, can the linux box ping to the outside world and can the Win32 box
ping to the outside world. If you're going through a router, what is the
IP address of the router (mine is 192.168.2.1) and can that be pinged
from both machines? Are you going directly from machine to machine and
if so, are you using a twisted lead or a straight lead (twisted are the
one you normally have from machine to network and won't work machine to
machine)?
Not true.
Standard ethernet cable is straight thru and is used from machine to
switch/hub. Crossover cables (which you refer to as twisted leads) are
required to go directly from NIC to NIC without using a hub/switch
between.
Post by PFJ
Are you running a firewall on either/both machine(s)?
Personally, I would do this (assuming you're on a router)
1. Find the IP address of the router (look at the user guide)
2. Disable all firewalls and disconnect the router to the outside world
3. Ensure that all firewalls are off on the router
4. From the linux box, ensure the NIC is working (/sbin/ifconfig eth0
will let you know, you will get an IP address [192.168.2.100 say])
5. If you don't get an IP address, /sbin/ifup eth0. If that fails, /
sbin/lsmod - see if the network driver has been loaded. If it hasn't /
sbin/modprobe <name_of_driver>. Then try /sbin/ifup eth0. If it still
fails, there is a problem with the NIC. If it works and you don't have
an IP for the card, try a new cable, /sbin/ifdown eth0 then /sbin/ifup
eth0. If there is still no IP address, you will need to test the line
from the NIC to the router.
6. If you do get an address, see if you can ping the router. Assuming
you can ping the router (which indicates all the connections, leads and
NIC is happy), repeat for the Windows box.
7. If everything is happy with the windows box, you should be able to
ping either box. A simpler test is to run vsftpd on the linux box and
see if you can ftp onto it. Why is that simpler? Well, some software on
the Win32 side will stop the ability to ping.
8. If you can go from machine to machine, reconnect the router to the
outside world and see if you can either ping or ftp to a remote site. If
you can't, then it is probably a DNS problem (fire up neat, switch off
get IP dynamically and enter your ISPs DNS, reactive eth0 and try
again).
9. On one machine at a time (I'd go linux first), re-enable any
firewalls you have *slowly* until something breaks.
That's the nice trouble shooting way.
TTFN
Paul
P.S. Sorry if this has been covered, I've not followed the thread.
--
fedora-list mailing list
fedora-list at redhat.com
To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-list
PFJ
2004-09-13 11:14:59 UTC
Permalink
Hi,
Post by Jeff Vian
Standard ethernet cable is straight thru and is used from machine to
switch/hub. Crossover cables (which you refer to as twisted leads) are
required to go directly from NIC to NIC without using a hub/switch
between.
Damn. I knew it was one way or the other!

TTFN

Paul
--
"If I face my God tomorrow, I can tell Him I am innocent.
I've never harmed anyone. I have cheated no one.
I have deceived no one. I have hurt no one.
Except myself. And that He will forgive me." - Hans Holzel
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : http://lists.fedoraproject.org/pipermail/users/attachments/20040913/58cce705/attachment.bin
Tor Harald Thorland
2004-09-13 09:47:10 UTC
Permalink
Thanks for all the quick answers, I'll found a virus scanner with a firewall
(sorry) that maby is the problem.
I'll check everything out when my other problem with the machine not boot
ing is fixed :-(
Everything that can be messed up is messed up today!!

THT
----- Original Message -----
From: "Jeff Vian" <jvian10 at charter.net>
To: "For users of Fedora Core releases" <fedora-list at redhat.com>
Sent: Monday, September 13, 2004 10:43 AM
Subject: Re: Cant ping windows network card, but can ping the linux card..
Post by Jeff Vian
Post by PFJ
Hi,
Post by Paul Howarth
Post by Tor Harald Thorland
I got this answer when I ping it.
[tortho at localhost tortho]$ ping 192.168.132.2
PING 192.168.132.2 (192.168.132.2) 56(84) bytes of data.
Post by Edward
From 192.168.132.1 icmp_seq=0 Destination Host Unreachable
From 192.168.132.1 icmp_seq=1 Destination Host Unreachable
ifconfig -a
netstat
Okay, can the linux box ping to the outside world and can the Win32 box
ping to the outside world. If you're going through a router, what is the
IP address of the router (mine is 192.168.2.1) and can that be pinged
from both machines? Are you going directly from machine to machine and
if so, are you using a twisted lead or a straight lead (twisted are the
one you normally have from machine to network and won't work machine to
machine)?
Not true.
Standard ethernet cable is straight thru and is used from machine to
switch/hub. Crossover cables (which you refer to as twisted leads) are
required to go directly from NIC to NIC without using a hub/switch
between.
Post by PFJ
Are you running a firewall on either/both machine(s)?
Personally, I would do this (assuming you're on a router)
1. Find the IP address of the router (look at the user guide)
2. Disable all firewalls and disconnect the router to the outside world
3. Ensure that all firewalls are off on the router
4. From the linux box, ensure the NIC is working (/sbin/ifconfig eth0
will let you know, you will get an IP address [192.168.2.100 say])
5. If you don't get an IP address, /sbin/ifup eth0. If that fails, /
sbin/lsmod - see if the network driver has been loaded. If it hasn't /
sbin/modprobe <name_of_driver>. Then try /sbin/ifup eth0. If it still
fails, there is a problem with the NIC. If it works and you don't have
an IP for the card, try a new cable, /sbin/ifdown eth0 then /sbin/ifup
eth0. If there is still no IP address, you will need to test the line
from the NIC to the router.
6. If you do get an address, see if you can ping the router. Assuming
you can ping the router (which indicates all the connections, leads and
NIC is happy), repeat for the Windows box.
7. If everything is happy with the windows box, you should be able to
ping either box. A simpler test is to run vsftpd on the linux box and
see if you can ftp onto it. Why is that simpler? Well, some software on
the Win32 side will stop the ability to ping.
8. If you can go from machine to machine, reconnect the router to the
outside world and see if you can either ping or ftp to a remote site. If
you can't, then it is probably a DNS problem (fire up neat, switch off
get IP dynamically and enter your ISPs DNS, reactive eth0 and try
again).
9. On one machine at a time (I'd go linux first), re-enable any
firewalls you have *slowly* until something breaks.
That's the nice trouble shooting way.
TTFN
Paul
P.S. Sorry if this has been covered, I've not followed the thread.
--
fedora-list mailing list
fedora-list at redhat.com
To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-list
PFJ
2004-09-13 11:14:59 UTC
Permalink
Hi,
Post by Jeff Vian
Standard ethernet cable is straight thru and is used from machine to
switch/hub. Crossover cables (which you refer to as twisted leads) are
required to go directly from NIC to NIC without using a hub/switch
between.
Damn. I knew it was one way or the other!

TTFN

Paul
--
"If I face my God tomorrow, I can tell Him I am innocent.
I've never harmed anyone. I have cheated no one.
I have deceived no one. I have hurt no one.
Except myself. And that He will forgive me." - Hans Holzel
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : http://lists.fedoraproject.org/pipermail/users/attachments/20040913/58cce705/attachment-0002.bin
Jeff Vian
2004-09-13 08:43:55 UTC
Permalink
Post by PFJ
Hi,
Post by Paul Howarth
Post by Tor Harald Thorland
I got this answer when I ping it.
[tortho at localhost tortho]$ ping 192.168.132.2
PING 192.168.132.2 (192.168.132.2) 56(84) bytes of data.
Post by Edward
From 192.168.132.1 icmp_seq=0 Destination Host Unreachable
From 192.168.132.1 icmp_seq=1 Destination Host Unreachable
ifconfig -a
netstat
Okay, can the linux box ping to the outside world and can the Win32 box
ping to the outside world. If you're going through a router, what is the
IP address of the router (mine is 192.168.2.1) and can that be pinged
from both machines? Are you going directly from machine to machine and
if so, are you using a twisted lead or a straight lead (twisted are the
one you normally have from machine to network and won't work machine to
machine)?
Not true.

Standard ethernet cable is straight thru and is used from machine to
switch/hub. Crossover cables (which you refer to as twisted leads) are
required to go directly from NIC to NIC without using a hub/switch
between.
Post by PFJ
Are you running a firewall on either/both machine(s)?
Personally, I would do this (assuming you're on a router)
1. Find the IP address of the router (look at the user guide)
2. Disable all firewalls and disconnect the router to the outside world
3. Ensure that all firewalls are off on the router
4. From the linux box, ensure the NIC is working (/sbin/ifconfig eth0
will let you know, you will get an IP address [192.168.2.100 say])
5. If you don't get an IP address, /sbin/ifup eth0. If that fails, /
sbin/lsmod - see if the network driver has been loaded. If it hasn't /
sbin/modprobe <name_of_driver>. Then try /sbin/ifup eth0. If it still
fails, there is a problem with the NIC. If it works and you don't have
an IP for the card, try a new cable, /sbin/ifdown eth0 then /sbin/ifup
eth0. If there is still no IP address, you will need to test the line
from the NIC to the router.
6. If you do get an address, see if you can ping the router. Assuming
you can ping the router (which indicates all the connections, leads and
NIC is happy), repeat for the Windows box.
7. If everything is happy with the windows box, you should be able to
ping either box. A simpler test is to run vsftpd on the linux box and
see if you can ftp onto it. Why is that simpler? Well, some software on
the Win32 side will stop the ability to ping.
8. If you can go from machine to machine, reconnect the router to the
outside world and see if you can either ping or ftp to a remote site. If
you can't, then it is probably a DNS problem (fire up neat, switch off
get IP dynamically and enter your ISPs DNS, reactive eth0 and try
again).
9. On one machine at a time (I'd go linux first), re-enable any
firewalls you have *slowly* until something breaks.
That's the nice trouble shooting way.
TTFN
Paul
P.S. Sorry if this has been covered, I've not followed the thread.
PFJ
2004-09-13 08:17:26 UTC
Permalink
Hi,
Post by Paul Howarth
Post by Tor Harald Thorland
I got this answer when I ping it.
[tortho at localhost tortho]$ ping 192.168.132.2
PING 192.168.132.2 (192.168.132.2) 56(84) bytes of data.
Post by Edward
From 192.168.132.1 icmp_seq=0 Destination Host Unreachable
From 192.168.132.1 icmp_seq=1 Destination Host Unreachable
ifconfig -a
netstat
Okay, can the linux box ping to the outside world and can the Win32 box
ping to the outside world. If you're going through a router, what is the
IP address of the router (mine is 192.168.2.1) and can that be pinged
from both machines? Are you going directly from machine to machine and
if so, are you using a twisted lead or a straight lead (twisted are the
one you normally have from machine to network and won't work machine to
machine)?

Are you running a firewall on either/both machine(s)?

Personally, I would do this (assuming you're on a router)

1. Find the IP address of the router (look at the user guide)
2. Disable all firewalls and disconnect the router to the outside world
3. Ensure that all firewalls are off on the router
4. From the linux box, ensure the NIC is working (/sbin/ifconfig eth0
will let you know, you will get an IP address [192.168.2.100 say])
5. If you don't get an IP address, /sbin/ifup eth0. If that fails, /
sbin/lsmod - see if the network driver has been loaded. If it hasn't /
sbin/modprobe <name_of_driver>. Then try /sbin/ifup eth0. If it still
fails, there is a problem with the NIC. If it works and you don't have
an IP for the card, try a new cable, /sbin/ifdown eth0 then /sbin/ifup
eth0. If there is still no IP address, you will need to test the line
from the NIC to the router.
6. If you do get an address, see if you can ping the router. Assuming
you can ping the router (which indicates all the connections, leads and
NIC is happy), repeat for the Windows box.
7. If everything is happy with the windows box, you should be able to
ping either box. A simpler test is to run vsftpd on the linux box and
see if you can ftp onto it. Why is that simpler? Well, some software on
the Win32 side will stop the ability to ping.
8. If you can go from machine to machine, reconnect the router to the
outside world and see if you can either ping or ftp to a remote site. If
you can't, then it is probably a DNS problem (fire up neat, switch off
get IP dynamically and enter your ISPs DNS, reactive eth0 and try
again).
9. On one machine at a time (I'd go linux first), re-enable any
firewalls you have *slowly* until something breaks.

That's the nice trouble shooting way.

TTFN

Paul

P.S. Sorry if this has been covered, I've not followed the thread.
--
"If I face my God tomorrow, I can tell Him I am innocent.
I've never harmed anyone. I have cheated no one.
I have deceived no one. I have hurt no one.
Except myself. And that He will forgive me." - Hans Holzel
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : http://lists.fedoraproject.org/pipermail/users/attachments/20040913/b2b4efc5/attachment-0002.bin
Wolfgang Gill
2004-09-13 08:10:26 UTC
Permalink
Post by Tor Harald Thorland
Post by Edward
Post by Tor Harald Thorland
Hi,
I have tryed to setup a network with a couple of PC's.
The linux box has 2 NIC's one with static IP, connected to a DSL line.
(Internet working)
The other card has a static IP adress of 192.168.132.1
The windows XP box has IP 192.168.132.2
The windows box can ping the fedora core 2 pc nicely, but the fedora box
can't ping the windows box..!
Any suggestions? Anyone who can give me some help in solving this and
get the XP box on the net.
You running a firewall on the XP box connection?
Regards,
Ed.
The firewall is Off..
I got this answer when I ping it.
[tortho at localhost tortho]$ ping 192.168.132.2
PING 192.168.132.2 (192.168.132.2) 56(84) bytes of data.
Post by Edward
From 192.168.132.1 icmp_seq=0 Destination Host Unreachable
From 192.168.132.1 icmp_seq=1 Destination Host Unreachable
THT
And are you sure that the MS-Firewall is off?? As the SP2 update re-enables it
and causes nothing but problems with other firewall software (Like Norton
Personal Firewall for example). Also check the services to see that it's not
running as well. As turning it off in the control panel doesn't remove the
service. You will have to do that manually. Damn MS firewall crap!!

Wolf
--
Open WebMail Project (http://openwebmail.org)
Paul Howarth
2004-09-13 07:56:37 UTC
Permalink
Post by Tor Harald Thorland
I got this answer when I ping it.
[tortho at localhost tortho]$ ping 192.168.132.2
PING 192.168.132.2 (192.168.132.2) 56(84) bytes of data.
Post by Edward
From 192.168.132.1 icmp_seq=0 Destination Host Unreachable
From 192.168.132.1 icmp_seq=1 Destination Host Unreachable
What's the output of:

ifconfig -a
netstat -rn

Paul.
--
Paul Howarth <paul at city-fan.org>
Wolfgang Gill
2004-09-13 08:10:26 UTC
Permalink
Post by Tor Harald Thorland
Post by Edward
Post by Tor Harald Thorland
Hi,
I have tryed to setup a network with a couple of PC's.
The linux box has 2 NIC's one with static IP, connected to a DSL line.
(Internet working)
The other card has a static IP adress of 192.168.132.1
The windows XP box has IP 192.168.132.2
The windows box can ping the fedora core 2 pc nicely, but the fedora box
can't ping the windows box..!
Any suggestions? Anyone who can give me some help in solving this and
get the XP box on the net.
You running a firewall on the XP box connection?
Regards,
Ed.
The firewall is Off..
I got this answer when I ping it.
[tortho at localhost tortho]$ ping 192.168.132.2
PING 192.168.132.2 (192.168.132.2) 56(84) bytes of data.
Post by Edward
From 192.168.132.1 icmp_seq=0 Destination Host Unreachable
From 192.168.132.1 icmp_seq=1 Destination Host Unreachable
THT
And are you sure that the MS-Firewall is off?? As the SP2 update re-enables it
and causes nothing but problems with other firewall software (Like Norton
Personal Firewall for example). Also check the services to see that it's not
running as well. As turning it off in the control panel doesn't remove the
service. You will have to do that manually. Damn MS firewall crap!!

Wolf
--
Open WebMail Project (http://openwebmail.org)
Tor Harald Thorland
2004-09-13 07:28:29 UTC
Permalink
Post by Edward
Post by Tor Harald Thorland
Hi,
I have tryed to setup a network with a couple of PC's.
The linux box has 2 NIC's one with static IP, connected to a DSL line.
(Internet working)
The other card has a static IP adress of 192.168.132.1
The windows XP box has IP 192.168.132.2
The windows box can ping the fedora core 2 pc nicely, but the fedora box
can't ping the windows box..!
Any suggestions? Anyone who can give me some help in solving this and
get the XP box on the net.
You running a firewall on the XP box connection?
Regards,
Ed.
The firewall is Off..
I got this answer when I ping it.
[tortho at localhost tortho]$ ping 192.168.132.2
PING 192.168.132.2 (192.168.132.2) 56(84) bytes of data.
Post by Edward
From 192.168.132.1 icmp_seq=0 Destination Host Unreachable
From 192.168.132.1 icmp_seq=1 Destination Host Unreachable
THT
Robert Slade
2004-09-13 16:45:49 UTC
Permalink
Post by Tor Harald Thorland
Hi,
I have tryed to setup a network with a couple of PC's.
The linux box has 2 NIC's one with static IP, connected to a DSL line. (Internet working)
The other card has a static IP adress of 192.168.132.1
The windows XP box has IP 192.168.132.2
The windows box can ping the fedora core 2 pc nicely, but the fedora
box can't ping the windows box..!
Any suggestions? Anyone who can give me some help in solving this and
get the XP box on the net.
THT
I have just had a similar problem with FC2 and 2 network cards. The
machine I was using to try FC2, was happily working and so was the
network. Using a spare HD I put FC2 on it - no network, I could ping the
network cards and local loopback but nothing else. I eventually found
the problem to be that FC2 identifies the cards differently. What was
eth0 on FC1 became eth1 with FC2 and vice versa. You may have something
similar.

Rob
Tor Harald Thorland
2004-09-13 20:30:56 UTC
Permalink
Hi,

Thanks for all the answers!!
It was the damn virus scanner wich blocked it.
Now i'm only struggeling with getting the windows box to connect to the
internet through the linux box.

THT
Post by Robert Slade
Post by Tor Harald Thorland
Hi,
I have tryed to setup a network with a couple of PC's.
The linux box has 2 NIC's one with static IP, connected to a DSL line.
(Internet working)
The other card has a static IP adress of 192.168.132.1
The windows XP box has IP 192.168.132.2
The windows box can ping the fedora core 2 pc nicely, but the fedora
box can't ping the windows box..!
Any suggestions? Anyone who can give me some help in solving this and
get the XP box on the net.
THT
I have just had a similar problem with FC2 and 2 network cards. The
machine I was using to try FC2, was happily working and so was the
network. Using a spare HD I put FC2 on it - no network, I could ping the
network cards and local loopback but nothing else. I eventually found
the problem to be that FC2 identifies the cards differently. What was
eth0 on FC1 became eth1 with FC2 and vice versa. You may have something
similar.
Rob
Tor Harald Thorland
2004-09-13 20:30:56 UTC
Permalink
Hi,

Thanks for all the answers!!
It was the damn virus scanner wich blocked it.
Now i'm only struggeling with getting the windows box to connect to the
internet through the linux box.

THT
Post by Robert Slade
Post by Tor Harald Thorland
Hi,
I have tryed to setup a network with a couple of PC's.
The linux box has 2 NIC's one with static IP, connected to a DSL line.
(Internet working)
The other card has a static IP adress of 192.168.132.1
The windows XP box has IP 192.168.132.2
The windows box can ping the fedora core 2 pc nicely, but the fedora
box can't ping the windows box..!
Any suggestions? Anyone who can give me some help in solving this and
get the XP box on the net.
THT
I have just had a similar problem with FC2 and 2 network cards. The
machine I was using to try FC2, was happily working and so was the
network. Using a spare HD I put FC2 on it - no network, I could ping the
network cards and local loopback but nothing else. I eventually found
the problem to be that FC2 identifies the cards differently. What was
eth0 on FC1 became eth1 with FC2 and vice versa. You may have something
similar.
Rob
Tor Harald Thorland
2004-09-13 06:56:52 UTC
Permalink
Hi,

I have tryed to setup a network with a couple of PC's.
The linux box has 2 NIC's one with static IP, connected to a DSL line. (Internet working)
The other card has a static IP adress of 192.168.132.1
The windows XP box has IP 192.168.132.2
The windows box can ping the fedora core 2 pc nicely, but the fedora box can't ping the windows box..!
Any suggestions? Anyone who can give me some help in solving this and get the XP box on the net.

THT
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.fedoraproject.org/pipermail/users/attachments/20040913/63178f98/attachment-0002.html
Edward
2004-09-13 07:13:28 UTC
Permalink
Post by Tor Harald Thorland
Hi,
I have tryed to setup a network with a couple of PC's.
The linux box has 2 NIC's one with static IP, connected to a DSL line. (Internet working)
The other card has a static IP adress of 192.168.132.1
The windows XP box has IP 192.168.132.2
The windows box can ping the fedora core 2 pc nicely, but the fedora box
can't ping the windows box..!
Any suggestions? Anyone who can give me some help in solving this and
get the XP box on the net.
You running a firewall on the XP box connection?

Regards,
Ed.
Robert Slade
2004-09-13 16:45:49 UTC
Permalink
Post by Tor Harald Thorland
Hi,
I have tryed to setup a network with a couple of PC's.
The linux box has 2 NIC's one with static IP, connected to a DSL line. (Internet working)
The other card has a static IP adress of 192.168.132.1
The windows XP box has IP 192.168.132.2
The windows box can ping the fedora core 2 pc nicely, but the fedora
box can't ping the windows box..!
Any suggestions? Anyone who can give me some help in solving this and
get the XP box on the net.
THT
I have just had a similar problem with FC2 and 2 network cards. The
machine I was using to try FC2, was happily working and so was the
network. Using a spare HD I put FC2 on it - no network, I could ping the
network cards and local loopback but nothing else. I eventually found
the problem to be that FC2 identifies the cards differently. What was
eth0 on FC1 became eth1 with FC2 and vice versa. You may have something
similar.

Rob
Continue reading on narkive:
Loading...