On Mon, 14 Jul 2003, John Klos wrote: > I hate to sound cynical, but getting Windows computers to see each other > on a physical ethernet segment is difficult enough. >
No, you're just flamebaiting... > Before worrying about file sharing, which is always a pain in the ass on > Windows, try to get TCP/IP working first. If you're using DHCP, are the > Windows computers getting IPs? If so, or if they are static IPs, can you > ping the IPs directly from the router or from the Linux machine? Can the > Windows computers ping the router? > Try typing Start->Run->WINIPCFG to show your IP configuration. If you have multiple adapters installed, then choose the correct adapter from the dropdown. It should show the IP address and the subnet mask. Make sure that it's in the same range (ie., 192.168.0.x) and that the subnet is also the identical. Open a MS-DOS Command Prompt. Try any (or all) of the following commands. ping <target ip> tracert <target ip> arp -a Do it for both the other computer and the router itself. It should look nearly identical from either computer. If not, then something's amiss. > Due to the shortage of IPv4 space, broadcast IPs are being used more and > more as regular addresses, so it's generally not a good idea to make a > diagnosis based on whether or not they work. > Also, note that most OSes have restricteded support for responding to broadcast ping based on the fact that it was abused as a DoS tool in the late 90s (ping class A/B/C broadcast using spoofed packet). Kevin "Starfox" Arima -- NYCwireless - http://www.nycwireless.net/ Un/Subscribe: http://lists.nycwireless.net/mailman/listinfo/nycwireless/ Archives: http://lists.nycwireless.net/pipermail/nycwireless/
