It looks as if we are getting somewhere. Now can you verify the addresses of the win98 machines? Then you should try to ping them from one-another and from the SuSE machine. Once we have established connections, then we can start the delicate matter of setting up SMB networking. You must be aware that the DHCP server is not obliged to provide the same address to a host when it is reconnected to the net. We then get the problem of finding the hosts if they are rebooted into a different address. SMB handles this by a requested naming and search mechanism but for tcp/ip work you must have a name server, or you will have to rediscover the ip addresses yourself each time. Peter On Tuesday 16 April 2002 2:35 pm, you wrote: <snip>
OK, that makes a difference:
ifconfig -a eth0 Link encap:Ethernet HWaddr 00:50:2C:01:2B:1B inet addr:192.168.1.100 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::250:2cff:fe01:2b1b/10 Scope:Link UP BROADCAST NOTRAILERS RUNNING MTU:1500 Metric:1 RX packets:175124 errors:0 dropped:0 overruns:0 frame:0 TX packets:193281 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 RX bytes:129379728 (123.3 Mb) TX bytes:56967625 (54.3 Mb) Interrupt:11 Base address:0xec00
lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:160 errors:0 dropped:0 overruns:0 frame:0 TX packets:160 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:10432 (10.1 Kb) TX bytes:10432 (10.1 Kb)
sit0 Link encap:IPv6-in-IPv4 NOARP MTU:1480 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
# netstat -tn Active Internet connections (w/o servers) Proto Recv-Q Send-Q Local Address Foreign Address State tcp 0 0 192.168.1.100:37755 66.57.9.47:6346 ESTABLISHED tcp 0 5514 192.168.1.100:37748 80.62.224.89:6346 ESTABLISHED tcp 0 0 192.168.1.100:32774 65.119.4.104:143 ESTABLISHED tcp 0 1596 192.168.1.100:37517 80.0.194.171:6441 ESTABLISHED tcp 0 1295 192.168.1.100:37426 24.197.250.5:6346 ESTABLISHED tcp 0 522 192.168.1.100:37782 68.81.42.27:6346 ESTABLISHED tcp 0 1304 192.168.1.100:37815 24.49.156.5:6347 ESTABLISHED
# netstat -rn Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface 192.168.1.0 0.0.0.0 255.255.255.0 U 40 0 0 eth0 0.0.0.0 192.168.1.1 0.0.0.0 UG 40 0 0 eth0
So the SuSE IP address for my machine is 192.168.1.100 (may be the same in Win 2k). I pinged from a Win 98 SE machine and was successfull.
Now we are getting somewhere ;-) The question is what does this than say about the condition of the SuSE network, i.e. why can't I get smbclient and LinNeighborhood to work?
Cheers,
Brian