Page 1 of 2 12 LastLast
Results 1 to 10 of 17

Thread: Networking Linux box (knoppix 3.4) with Windows XP PC

  1. #1
    Junior Member registered user
    Join Date
    Oct 2004
    Location
    Los Angeles
    Posts
    21

    Networking Linux box (knoppix 3.4) with Windows XP PC

    I have a dual boot system running XP pro and knoppix 3.4 and another PC running Windows XP pro only. I have DSL running and I have the two PCs running through an NR041 Linksys router. I can access the internet from both PCs so I know my lines are solid. How do I network the PCs together, though, for file sharing, printing and CD burning, etc.? The XP pro system has the CD burner and the printer... Any ideas, help or suggestions?

    Thanks!

  2. #2

  3. #3
    Junior Member registered user
    Join Date
    Oct 2004
    Location
    Los Angeles
    Posts
    21
    I am having a problem... I was able to follow the Samba directions a create a file but it didn't work.

    I can ping my windows PC and I can ping myself (ie, linux to linux) but I cannot ping my linux box from windows PC. I went into LAN properties and made sure that there were no locks on the windows PC, but it still isn't working.

    Any ideas on how I can even ping my linux box to winXP PC and vice versa?


    Help!

  4. #4
    Administrator Site Admin-
    Join Date
    Apr 2003
    Location
    USA
    Posts
    5,441
    Quote Originally Posted by nicorellius
    ......I can ping my windows PC and I can ping myself (ie, linux to linux) but I cannot ping my linux box from windows PC. I went into LAN properties and made sure that there were no locks on the windows PC, but it still isn't working......
    Very strange. You should certainly be able to ping any system on the local network from any other (getting Samba working may be a different issue, but the ping has to work first). You are trying to ping by IP address, are you not? I know that under windows from computer "desktop" I can ping "notebook" with a simple "ping notebook" and windows will resolve the address. But until you have everything working I'm hoping your restricting the ping to the more typical "ping 192.168.0.100" type commands.

    When you say you can ping yourself, linux to linux, are you talking about linux on 2 PC's (not really pinging yourself)? And can you ping the router from both systems? Are you very very sure you have the IP addresses right?

  5. #5
    Junior Member registered user
    Join Date
    Oct 2004
    Location
    Los Angeles
    Posts
    21
    I am restricting the pings to simple, ie, IP number to IP number. When you say ping router, do you mean ping 192.168.0.1? I think I have but (feeling dumb) can't remember the results... So far, however, this is what is going on,

    linux = 192.168.1.101 (only one machine)

    windows = 192.168.1.100 (only one machine)

    two PCs total

    ping: linux -> windows (192.168.1.101 -> 192.168.1.100) successful

    ping: windows -> linux unsuccessful

    ping: linux -> linux successful

    ping: windows -> windows successful

    I am at work currently and therefore not with my home PCs, but as soon as I get home, I am gong to try pinging everything all over, making very, very sure that I have the correct addresses...

    Any thoughts so far?

  6. #6
    Administrator Site Admin-
    Join Date
    Apr 2003
    Location
    USA
    Posts
    5,441
    Quote Originally Posted by nicorellius
    I am restricting the pings to simple, ie, IP number to IP number. When you say ping router, do you mean ping 192.168.0.1?
    Well, pretty much, but see below. If the router isn't responding to a ping them you likely have something even more basic going wrong, so you might as well do this test.

    Quote Originally Posted by nicorellius
    however, this is what is going on,

    linux = 192.168.1.101 (only one machine)

    windows = 192.168.1.100 (only one machine)
    ......
    Any thoughts so far?
    Now, something looks wacky right away. You said above the router was 192.168.0.1. The 192.168.xxx.xxx addresses are ranges of IP addresses that are class C addresses, they use a mask of 255.255.255.0. So if the router is at 182.168.1. then it should be handing out addresses like 192.168.0.100 and 192.168.0.101, not 192.168.1.xxx addresses. Most of these routhers let you assign both the router IP address and the range of IP addresses that the router hands out, but you should keep that range in the same class C address range that the router is in. So if the above address you gave are correct and not a typo, either move the router to 192.168.1.1 or move the IP range the router hands out to the 192.168.0.xxx range.

    And you are assigning IP addresses by DHCP, rather than manually setting them, are you not?

    Quote Originally Posted by nicorellius
    linux = 192.168.1.101 (only one machine)

    windows = 192.168.1.100 (only one machine)

    two PCs total

    ping: linux -> windows (192.168.1.101 -> 192.168.1.100) successful

    ping: windows -> linux unsuccessful

    ping: linux -> linux successful

    ping: windows -> windows successful
    Pinging your own IP address is meaningless.

    Once you resolve the IP address issue I brought up above, if you still have the problem, and if you can ping the router from each system, then either boot both systems in windows, or burn another Knoppix CD and boot both of the computers in Knoppix. Then you can see if you really have a windows/linux issue, or is you just have a problem pinging. My guess is that if you can't ping by IP address between the windows box and the Linux box, and there is no firewall issue blocking pings, then you would not be able to ping between 2 knoppix boxes either. If you can ping when Knoppix is running on each system then look for a firewall blocking pings on the windows box.

  7. #7
    Junior Member registered user
    Join Date
    Oct 2004
    Location
    Los Angeles
    Posts
    21
    Thanks a lot, Harry, for your help so far. Here is what's going on:

    First of all, I have only one of my PCs dual booting, the other is only XP. So I booted both with XP. Here are the ping results:

    XP 192.168.1.101 -> 192.168.0.1 success
    XP 192.168.1.101 -> 192.168.1.1 success
    XP 192.168.1.101 -> 192.168.1.100 no success
    XP 192.168.1.101 -> 192.168.1.101 success

    XP 192.168.1.100 -> 192.168.0.1 success
    XP 192.168.1.100 -> 192.168.1.1 success
    XP 192.168.1.100 -> 192.168.1.100 no success
    XP 192.168.1.100 -> 192.168.1.101 success

    My router is assigning IPs with DHCP but they stay the same.

    When I go to 192.168.0.1 I get an SBC site (maybe a modem IP) where I see all my account info, true IP, login, etc...

    When I go to 192.168.1.1 I can log into my router and make changes, etc...

    Since I have only one linux box, I cannot boot both with linux. That is why I booted both with windows. I figure if I can resolve this issue using windows then when I boot linux, I will be golden. The samba thing will have to wait, though.

    I know you said that pinging myself is meaningless. But why, then, can I not ping the 192.168.1.100 from either IP, but I can reach 192.168.1.101 from both IPs?

    Is it possible that SBC has something to do with my problem?

    Any thoughts?

  8. #8
    Administrator Site Admin-
    Join Date
    Apr 2003
    Location
    USA
    Posts
    5,441
    Quote Originally Posted by nicorellius
    When I go to 192.168.0.1 I get an SBC site (maybe a modem IP) where I see all my account info, true IP, login, etc...

    When I go to 192.168.1.1 I can log into my router and make changes, etc...
    You had previously said that the router's address was 192.168..0.1, but now it sounds like the router is at 192.168.1.1. I'm not sure what SBC means to you. Is it your ISP ? Is it your brand of modem?

    I've never worked with one, but have seen discussion that some new modems do have a router built in. If that is your case then both the modem's built-in router and the other router would be doing NAT. If that is what is happening, you should really disable the router in the modem and use just the external router for NAT, DHCP and the like.

    That said, your pinging problem still doesn't make much sense. Looks like the address ending in 100 is just not responding, which might be a firewall issue of some sort, but I would have to see more to really make a call.

    Quote Originally Posted by nicorellius
    ...

    First of all, I have only one of my PCs dual booting, the other is only XP. So I booted both with XP. .....

    Since I have only one linux box, I cannot boot both with linux. That is why I booted both with windows. I figure if I can resolve this issue using windows then when I boot linux, I will be golden. The samba thing will have to wait, though.
    Burn two Knoppix CD's and boot both computers from CD, not from the hard disk. I would even suggest booting the computer where you have Knoppix installed on hard disk from CD instead during the test - things seem to break in Koppix when installed to hard disk, there is no reason to add any extra variable to the test. Once everying is working right from CD then boot the dual boot one from Knoppix on the HD and confirm that nothing has changed, but for now keep things simple.

    I want to get a look at how things look with 2 Knoppix systems because I think (but am yet far from certain) that the reason for the strange ping results so far is Windows software, not any hardware issue. Pinging when both systems are in Knoppix is a test that will bypass windows.

    By the way, when you ping your own address you do go through some levels of the TCP/IP stack, but not all levels, so you're not realy testing everything and certainly not testing hardware. There are two other addresses that are intended for self-testing of the TCP/IP stack - but understand that none really check everything, although they are potential first checks that the local stack is working. For any address range, the lowest address in that range is yourself. Thus, if the router is handing out addresses in the range 192.168.1.xxx and a mask of 255.255.255.0, then either computer cound "ping itself" at 192.168.1.0, the lowest address in this range. Also, the address 127.0.0.1 is always a loop back address for your own stack.

    Quote Originally Posted by nicorellius
    I know you said that pinging myself is meaningless. But why, then, can I not ping the 192.168.1.100 from either IP, but I can reach 192.168.1.101 from both IPs?

    Is it possible that SBC has something to do with my problem?

    Any thoughts?
    I don't know, but my theory is that it's something in windows, maybe a firewall that's not letting that box respond to pings. Thus I want to get Windows out of the equation and try pinging this address when it's running Knoppix. Looking forward to hearing what SBC is. And if it's not the modem, then please identfy what make and model of modem you have, and give more information of what you see when you point your browser at 192.168.0.1.

  9. #9
    Junior Member registered user
    Join Date
    Oct 2004
    Location
    Los Angeles
    Posts
    21
    Sorry for the confusion. SBC Yahoo is my DSL internet provider.

    I will investigate if my modem has a built in router. Also, I will boot both systems from Knoppix CD and do the ping test. I will give a report and include my modem information as well.

    Thanks again...

  10. #10
    Junior Member registered user
    Join Date
    Oct 2004
    Location
    Los Angeles
    Posts
    21
    I booted both systems from Knoppix 3.4 CD and was able to succcessfully ping each PC from the other. In addition, I found out that 192.168.0.1 is the modem address, 192.168.1.1 is the router address, and 192.168.1.100, 101 are the addresses for each PC. I was able to ping all addresses from each PC booted from Knoppix 3.4.

    I also found out that Service Pack 2 was installed on my Windows PC so I uninstalled that because it has caused nothing but problems so far, and also because I have other means of protecting that PC.

    The modem is a SpeedStream 5100 and I believe it does not have a built-in router. There is a self test option at the modem address (192.168.0.1) that allows you to ping addresses to test connectivity. When I tried to ping my systems while at 192.168.0.1, it timed out. But then when I pinged from the console it worked fine.

    When I visit 192.168.0.1 I get all my internet service info. I can reset modem, changed modem codes, get loggs and statitics reports, check and change IP address assignment lease time, see MAC address, PPP location, PPPoE...

    When I visit 192.168.1.1, this is where I can change all the router settings like DHCP, DNS, Static and Dynamic IP...

    So I think you are right when you said it's a Windows problem. But then when I re-booted Windows without SP2 installed and making sure the system was not blocking pinging, it still didn't work. I even changed a setting at 192.168.1.1 where I can block WAN requests (pings) to allow for access to my system... I am not sure what is going on.

    SBC is internet service provider, by the way...


Page 1 of 2 12 LastLast

Similar Threads

  1. Networking windows to Linux
    By Phishman in forum Networking
    Replies: 0
    Last Post: 02-18-2005, 12:03 AM
  2. Networking Problem: Linux and Windows XP
    By nicorellius in forum Networking
    Replies: 1
    Last Post: 12-01-2004, 05:50 AM
  3. Networking fiiles from Knoppix to Windows
    By turbonow in forum Networking
    Replies: 2
    Last Post: 11-19-2004, 11:00 AM
  4. Knoppix and windows networking
    By Jakykong in forum MS Windows & New to Linux
    Replies: 8
    Last Post: 10-24-2004, 03:29 AM
  5. Knoppix and Windows networking
    By Case in forum Networking
    Replies: 4
    Last Post: 10-08-2004, 03:11 PM

Posting Permissions

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


HP Workstation Z640 2x Xeon E5-2623V3 32GB Ram 2x256GB SSD Quadro K420 NO OS GA picture

HP Workstation Z640 2x Xeon E5-2623V3 32GB Ram 2x256GB SSD Quadro K420 NO OS GA

$154.98



Dell T7810 Workstation 1x E5-2603 v3 16GB RAM Nvidia QUADRO +cables picture

Dell T7810 Workstation 1x E5-2603 v3 16GB RAM Nvidia QUADRO +cables

$120.00



E5-2699V4 Intel Xeon Processor  55M Cache, 2.20 GHz SR2JS CM8066002022506 picture

E5-2699V4 Intel Xeon Processor 55M Cache, 2.20 GHz SR2JS CM8066002022506

$155.00



Matching Pair Intel Xeon E5-2470V2 2.4GHz 25MB 8GT/s SR19S LGA 1356 Processor US picture

Matching Pair Intel Xeon E5-2470V2 2.4GHz 25MB 8GT/s SR19S LGA 1356 Processor US

$52.24



Dell Precision Tower 5810 Xeon E5-1650 v3 3.5 GHz 32 RAM 256GB SSD Windows 11 picture

Dell Precision Tower 5810 Xeon E5-1650 v3 3.5 GHz 32 RAM 256GB SSD Windows 11

$114.99



SR1XP Intel Xeon E5-2680 v3 12 Core 30MB 2.5GHz LGA 2011-3 Grade A Processor picture

SR1XP Intel Xeon E5-2680 v3 12 Core 30MB 2.5GHz LGA 2011-3 Grade A Processor

$3.38



Intel Xeon Gold 6148 - 2.40 GHz 20 Core (SR3B6) Processor picture

Intel Xeon Gold 6148 - 2.40 GHz 20 Core (SR3B6) Processor

$85.00



Intel Xeon E5-2667 V2 LGA 2011 3.3GHz 8 Core 130W 25MB 8GT/s CPU Processor picture

Intel Xeon E5-2667 V2 LGA 2011 3.3GHz 8 Core 130W 25MB 8GT/s CPU Processor

$14.99



Intel Xeon Platinum 8173M CPU LGA-3647 2.0GHz 28-Core SR37Q picture

Intel Xeon Platinum 8173M CPU LGA-3647 2.0GHz 28-Core SR37Q

$216.99



Matched pair Intel Xeon E5-2667v4 SR2P5 3.20GHz, 8 core, 25MB Processors LGA2011 picture

Matched pair Intel Xeon E5-2667v4 SR2P5 3.20GHz, 8 core, 25MB Processors LGA2011

$62.95