Find the answer to your Linux question:
Results 1 to 5 of 5
Enjoy an ad free experience by logging in. Not a member yet? Register.
  1. #1

    problem linux windows network

    I;m trying to connect a linux box to a windows 98.
    I;m sure i have hosts routes resolv and all things ok.
    when i ping the other box it doesn;t respond .
    When i;m ruuning ethereal it seems that the two boxes are talking to each other, the win box sends some smb , netbios and ipx protocols packets .
    I have not configured samba ,is it nessesary to have it configured if i don;t want to do file sharing??
    The boxes don;t respond to eachother what is wrong .
    MY route table U 0 0 0 eth0 U 0 0 0 lo

  2. #2
    Just Joined!
    Join Date
    Apr 2004
    The packets the Windows box is sending are probably broadcast packets and not sent specifically in response to your attempts to ping the windows box.

    Is there any form of firewall running on the windows box?

    By default win 98 would respond to pings but if you have installed a firewall then as most of the common windows firewalls block pings by default this could be the reason you are getting no response from the windows box.

    You make no mention of what happens if you try to ping the linux box from the windows box.

    How exactly are you trying to connect them? Via a network, using wireless or bluetooth devices?

    If you only have one network interface card then the routing table is unlikely to be at fault.

    What is the output of
    on the linux box

  3. #3
    Sorry i;didn;t give much feedback in the first place.
    I am not running firewall on win box
    A ping from win box just fails.The ping from linux doesn;t fail just seems not to respond but i said what shows the ethereal (and u are right they are broadcast packets from win identifying itsself).
    I have only one ether card per box and i connect them with cable with RJ45 plugs -directly no hub no switch- last my ifconfig is:
    eth0 Link encap:Ethernet HWaddr 00:05:5D:33:C2:26
    inet addr: Bcast: Mask:
    RX packets:0 errors:0 dropped:0 overruns:0 frame:0
    TX packets:4 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:100
    RX bytes:0 (0.0 b) TX bytes:240 (240.0 b)
    Interrupt:11 Base address:0xbf00

    lo Link encap:Local Loopback
    inet addr: Mask:
    UP LOOPBACK RUNNING MTU:16436 Metric:1
    RX packets:656 errors:0 dropped:0 overruns:0 frame:0
    TX packets:656 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:0
    RX bytes:33000 (32.2 Kb) TX bytes:33000 (32.2 Kb)

    i didnt include the pppx interface but i think it doesnt matter .

  4. $spacer_open
  5. #4
    Just Joined!
    Join Date
    Apr 2004
    Are you sure that the network cable you are using is a crossover lead?

    If there is no hub or switch between the two network cards and you just connect them directly, you need to use a network cable that is wired differently to the normal patch lead.

  6. #5
    For a direct connection you need a cross cable. Its because Tx of comp 1 should go int Rx of Comp 2 and vice versa.


Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts