Network Purgatory (Was network hell)
Hi, I've been downgraded in my suffering. I'd really like to figure this out and am thankful for all the help so far. Here's where I am. I have three machines on the network; the internet server (Suse 7.2 with masq services), a win2k machine and the Suse 8.0 notebook. All machines have internet access. The W2K and Suse 8 notebook can obviously therefore see the gateway. They cannot, however, see one another. I tried from the w2k box to ping the 8.0 notebook. Nada. The reverse was the same. Both machines can ping the gateway or I'd go incredibly nuts right this second. Can anyone offer some assistance? I'm frantic. Nick
Hi, First part no problem: Gateway: 192.168.0.99 W2K: 192.168.10.1 Notebook: 192.168.10.3 Second part: where on Suse 8.0 would I find the routing table? I can't even find route.conf anymore! TIA NIck At 06:06 PM 5/2/2002 +0200, you wrote:
On Thursday 02 May 2002 17:58, Nick Selby wrote:
Can anyone offer some assistance? I'm frantic.
Could you post ip addresses and routing tables of both systems?
Anders
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com
On Thursday 02 May 2002 18:15, Nick Selby wrote:
First part no problem:
Gateway: 192.168.0.99 W2K: 192.168.10.1 Notebook: 192.168.10.3
OK, and netmasks? 255.255.255.0 on all systems?
Second part: where on Suse 8.0 would I find the routing table? I can't even find route.conf anymore!
ip route list (I think that gives the whole thing. I'm still a little new to the iproute2 thing) route print I believe is the WinWayOfDoingThings. Anders
Cool!
OK, and netmasks? 255.255.255.0 on all systems? Yes!
Linux: 192.168.10.0/24 dev eth0 proto kernel scope link src 192.168.10.4 default via 192.168.10.1 dev eth0 Windows: MS TCP Loopback interface 0x1000003 ...00 80 48 c9 4a 7d ...... Winbond W89C940 PCI Network Adapter. =========================================================================== =========================================================================== Active Routes: Network Destination Netmask Gateway Interface Metric 0.0.0.0 0.0.0.0 192.168.10.1 192.168.10.102 1 127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1 192.168.10.0 255.255.255.0 192.168.10.102 192.168.10.102 1 192.168.10.102 255.255.255.255 127.0.0.1 127.0.0.1 1 192.168.10.255 255.255.255.255 192.168.10.102 192.168.10.102 1 224.0.0.0 224.0.0.0 192.168.10.102 192.168.10.102 1 255.255.255.255 255.255.255.255 192.168.10.102 192.168.10.102 1 Default Gateway: 192.168.10.1 ====================================================================== Can you really make heads or tails of that? I sure hope so!!! Nick At 06:22 PM 5/2/2002 +0200, you wrote:
On Thursday 02 May 2002 18:15, Nick Selby wrote:
First part no problem:
Gateway: 192.168.0.99 W2K: 192.168.10.1 Notebook: 192.168.10.3
Second part: where on Suse 8.0 would I find the routing table? I can't even find route.conf anymore!
ip route list
(I think that gives the whole thing. I'm still a little new to the iproute2 thing)
route print I believe is the WinWayOfDoingThings.
Anders
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com
On Thursday 02 May 2002 18:27, Nick Selby wrote:
Cool!
OK, and netmasks? 255.255.255.0 on all systems?
Yes!
Linux:
192.168.10.0/24 dev eth0 proto kernel scope link src 192.168.10.4 default via 192.168.10.1 dev eth0
Windows:
MS TCP Loopback interface 0x1000003 ...00 80 48 c9 4a 7d ...... Winbond W89C940 PCI Network Adapter. =========================================================================== =========================================================================== Active Routes: Network Destination Netmask Gateway Interface Metric 0.0.0.0 0.0.0.0 192.168.10.1 192.168.10.102 1 127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1 192.168.10.0 255.255.255.0 192.168.10.102 192.168.10.102 1 192.168.10.102 255.255.255.255 127.0.0.1 127.0.0.1 1 192.168.10.255 255.255.255.255 192.168.10.102 192.168.10.102 1 224.0.0.0 224.0.0.0 192.168.10.102 192.168.10.102 1 255.255.255.255 255.255.255.255 192.168.10.102 192.168.10.102 1 Default Gateway: 192.168.10.1 ======================================================================
Can you really make heads or tails of that? I sure hope so!!!
Sort of. The numbers don't really match what you posted before. As far as I can make out you have Win2K: 192.168.10.102 Linux: 192.168.10.4 Gateway: 192.168.10.1 Everything looks ok to me. Could it be that you were pinging the wrong ip numbers? Anders
At 06:35 PM 5/2/2002 +0200, you wrote:
Can you really make heads or tails of that? I sure hope so!!!
Sort of. The numbers don't really match what you posted before. As far as I can make out you have
Win2K: 192.168.10.102 Linux: 192.168.10.4 Gateway: 192.168.10.1
Everything looks ok to me. Could it be that you were pinging the wrong ip numbers?
This is bizarre. In the Yast2 setup on the Notebook, it says 192.168.10.3 . Now when I ping the ~.4 it, of course, works. And vice versa, when I ping ~10.10 HOWEVER, while W2K can now ping the suse notebook, it cannot see it on the network. If I go into My Network Neighborhood, it shows nothing, and if I click Computers Near Me, The Whole Network, or anything else, it comes back "Could not be found." I tried mapping a new drive, starting with the IP address 192.168.10.4 and it told me "The network path was not found" The pinging, however, is encouraging. This must be excruciating to more experienced users and I appreciate the help. Nick
On Thursday 02 May 2002 18:48, Nick Selby wrote:
HOWEVER, while W2K can now ping the suse notebook, it cannot see it on the network. If I go into My Network Neighborhood, it shows nothing, and if I click Computers Near Me, The Whole Network, or anything else, it comes back "Could not be found." I tried mapping a new drive, starting with the IP address 192.168.10.4 and it told me "The network path was not found"
Do you have something shared with samba on the linux box? Anders
any reason why the workstations and the gateway are on different networks (or subnets) wouldnt it just be easier to have gateway 192.168.10.99 and win2k be 192.168.10.1 and notebook to be 192.168.10.3 with gateway of each machine except gateway being 192.168.10.99, everything with netmask of 255.255.255.0 and the gateway for the gateway be whatever is assigned by the dsl/cable/ppp line? On Thursday 02 May 2002 11:22 am, Anders Johansson wrote:
On Thursday 02 May 2002 18:15, Nick Selby wrote:
First part no problem:
Gateway: 192.168.0.99 W2K: 192.168.10.1 Notebook: 192.168.10.3
OK, and netmasks? 255.255.255.0 on all systems?
Second part: where on Suse 8.0 would I find the routing table? I can't even find route.conf anymore!
ip route list
(I think that gives the whole thing. I'm still a little new to the iproute2 thing)
route print I believe is the WinWayOfDoingThings.
Anders
-- Chad Whitten Network/Systems Administrator neXband Communications cwhitten@nexband.com
I'm late to this discussion, so pardon me if this has already been
asked. Are you using the SuSE firewall? In SuSE 7.1, it blocks
access between subnets. Try taking the firewall down, pinging, and
then putting it back up.
Jeffrey
Quoting Nick Selby
Hi, I've been downgraded in my suffering. I'd really like to figure this out and am thankful for all the help so far.
Here's where I am. I have three machines on the network; the internet server (Suse 7.2 with masq services), a win2k machine and the Suse 8.0 notebook.
All machines have internet access. The W2K and Suse 8 notebook can obviously therefore see the gateway.
They cannot, however, see one another.
I tried from the w2k box to ping the 8.0 notebook. Nada. The reverse was the same.
Both machines can ping the gateway or I'd go incredibly nuts right this second.
Can anyone offer some assistance? I'm frantic.
Nick
At 11:13 AM 5/2/2002 -0500, you wrote:
I'm late to this discussion, so pardon me if this has already been asked. Are you using the SuSE firewall? In SuSE 7.1, it blocks access between subnets. Try taking the firewall down, pinging, and then putting it back up.
No< I've disconnected the firewall for now -shoulda mentioned that.
Quoting Nick Selby
: Hi, I've been downgraded in my suffering. I'd really like to figure this out and am thankful for all the help so far.
Here's where I am. I have three machines on the network; the internet server (Suse 7.2 with masq services), a win2k machine and the Suse 8.0 notebook.
All machines have internet access. The W2K and Suse 8 notebook can obviously therefore see the gateway.
They cannot, however, see one another.
I tried from the w2k box to ping the 8.0 notebook. Nada. The reverse was the same.
Both machines can ping the gateway or I'd go incredibly nuts right this second.
Can anyone offer some assistance? I'm frantic.
Nick
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com
participants (4)
-
Anders Johansson
-
Chad Whitten
-
Jeffrey Taylor
-
Nick Selby