Linux - Networking This forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game. |
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.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
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.
|
 |
12-08-2005, 06:36 AM
|
#1
|
Member
Registered: Oct 2005
Posts: 39
Rep:
|
cant ping
i cant ping from my WIndows machine to my Suse or vice versa. everything is set up right i have disabled all fire walls to see if that made a differece but it doesnt. Suse says Destination unreachable and Windows Crashes.
any ideas?
|
|
|
12-08-2005, 07:08 AM
|
#2
|
Member
Registered: Dec 2003
Distribution: Debian, FreeBSD
Posts: 310
Rep:
|
Are they both on the same physical network? What are the IPs, and subnet masks of both computers? What do you mean by "and Windows Crashes"?
|
|
|
12-08-2005, 08:39 AM
|
#3
|
Member
Registered: Oct 2005
Posts: 39
Original Poster
Rep:
|
its set up like this
windows
192.168.0.1
255.255.255.0
192.168.0.1
Linux
192.168.0.2
255.255.255.0
default gateway 192.168.0.1
in windows i Do ping 192.1680.2 and it doesnt do anything, no messages it just stays blank.
In linux i go ping -c5 192.168.0.1 and it says destination unreachable
|
|
|
12-08-2005, 09:00 AM
|
#4
|
Member
Registered: Nov 2004
Location: Hellas
Distribution: Zenwalk 6.4
Posts: 337
Rep:
|
are both network cards working?
i mean check if the leds on both pcs are working
check the installation on windows
as for suse I think you have a correct set up because you cannot assign an ip if you haven't.
|
|
|
12-08-2005, 09:11 AM
|
#5
|
Member
Registered: Oct 2005
Posts: 39
Original Poster
Rep:
|
The light is definantly flashing away on the card connected to Linux but it isnt flashing on the windows machine. But there are no conflicts and it says the dvice is working properly. have i missed something out of the configuration in Windows mayb?
|
|
|
12-08-2005, 10:01 AM
|
#6
|
Member
Registered: Dec 2003
Distribution: Debian, FreeBSD
Posts: 310
Rep:
|
Quote:
its set up like this
windows
192.168.0.1
255.255.255.0
192.168.0.1
Linux
192.168.0.2
255.255.255.0
default gateway 192.168.0.1
|
Do you have the two computers hooked directly to each other? If so make sure you are using a crossover cable if there is no switch or hub in place..
Also you dont want the Windows box to have the same IP set on it as its gateway. You didn't clarify in you post but Im guessing you have 192.168.0.1 assigned as a gateway, as well as its IP. If so remove that gateway IP.
If the 2 computers are on the same physical network, and on the same subnet you do not even need to assign a gateway.
|
|
|
12-08-2005, 10:04 AM
|
#7
|
Member
Registered: Oct 2005
Posts: 39
Original Poster
Rep:
|
oh rite, i will remove the deafult gateway then c if it works. do i need to do anything with the routing option? they are conneceted with a crossover cable!
|
|
|
12-08-2005, 10:05 AM
|
#8
|
Member
Registered: May 2003
Location: NYC
Distribution: CentOS
Posts: 261
Rep:
|
If your gateway is setup as 192.168.0.1 then your windows ip address should be something else like 192.168.0.x ... x being any number between 2-255. Since your linux machine is 192.168.0.2 then your windows machine should be something like 192.168.0.3
I am assuming that your default gateway is your router and both machines are connected to eachother through a router
Also for testing purposes ping localhost (127.0.0.1) to see if your loopback works. It basically tests your NIC card.
And lastly if your winddows machine is XP then you should disable its default firewall because it blocks icmp packets which essentially is your ping request.
|
|
|
12-08-2005, 11:13 AM
|
#9
|
Senior Member
Registered: Sep 2005
Location: Out
Posts: 3,307
Rep:
|
After testing the loopback, test the real network interface:
on windows:
on linux:
|
|
|
12-09-2005, 02:51 AM
|
#10
|
Member
Registered: Oct 2005
Posts: 39
Original Poster
Rep:
|
the loop back works on the Linux machine but it doesnt work with Windowz so waht does this mean then, the card is faulty
|
|
|
All times are GMT -5. The time now is 05:51 AM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|