On Tue, 20 Jun 2000, Andreas Meyer wrote:
> On 19-Jun-00, Fred Wright wrote:
>
> >> --- 192.168.0.2 ping statistics ---
> >> 45 packets transmitted, 0 packets received, 100% packet loss
> >
> > This means that there is no route to the destination, which usually
> > indicates ARP trouble. Start from offline in MiamiDx and a fresh
> > boot of the PC, and do the ping with MiamiTCPDump running in another
> > window.
>
> What means ARP?
Address Resolution Protocol - it's used to determine the Ethernet address
for a given IP address. When you ping "from scratch", it first needs an
ARP exchange for the machines to determine each other's Ethernet
addresses, then the actual IP packets can be sent.
> miamitcpdump: listening on eth0
> 00:07:39.940000 192.168.1.2.netbios-dgm > 192.168.1.255.netbios-dgm: udp 180
> 00:07:39.940003 192.168.1.2.netbios-dgm > 192.168.1.255.netbios-dgm: udp 180
> 00:07:40.000001 192.168.1.2.netbios-dgm > 192.168.1.255.netbios-dgm: udp 209
> 00:07:40.500001 arp who-has 192.168.1.2 tell 192.168.1.1 (52:54:40:26:79:ca)
> 00:07:45.560002 arp who-has 192.168.1.2 tell 192.168.1.1 (52:54:40:26:79:ca)
> 00:07:50.620002 arp who-has 192.168.1.2 tell 192.168.1.1 (52:54:40:26:79:ca)
> 00:07:55.020001 192.168.1.2.netbios-dgm > 192.168.1.255.netbios-dgm: udp 210
> 00:07:55.660002 arp who-has 192.168.1.2 tell 192.168.1.1 (52:54:40:26:79:ca)
> 00:08:00.720002 arp who-has 192.168.1.2 tell 192.168.1.1 (52:54:40:26:79:ca)
> 00:08:25.040002 192.168.1.2.netbios-dgm > 192.168.1.255.netbios-dgm: udp 209
This shows that you are receiving the PC's broadcasts OK, but not ARP
responses. I'd suggest trying broadcast pings to see if it's specifically
ARP that's failing, but Windoze doesn't like to answer broadcast pings.
What I'd suggest is that you try pinging from the PC (again starting
from scratch) with MiamiTCPDump running. Try both a normal unicast ping
(192.168.1.1) and a broadcast ping (192.168.1.255), and see what gets
through.
Unfortunately this looks more like a hardware problem with the NIC on one
of the two machines, where unicasts from PC to Amiga aren't working (the
other direction is unknown, although you might look to see if the PC's hub
LED flashes when you ping from the Amiga).
> After a ctrl-c I get:
> miamitcpdump: MiamiPCapLoop: read error from BPF
>
> 10 packets received by filter
> 0 packets dropped by kernel
That's normal.
> meanwhile a Miami-window opens:
> 20.06.00 00:08:16 MiamiDx-INetD Too many requests for netbios-ns/udp.
> Temporarily shutting down socket.
> 20.06.00 00:08:46 MiamiDx-INetD Socket for netbios-ns/udp restored.
That's another problem. :-) You might need to crank up inetd.toomany
and/or socket.maxqlen to get rid of these.
> >> I setup an Ethernet-Interface in MiamiDX with the
> >> z2-dp8390.mni-driver, option MEDIA=AUTO.
> >> IP-Adress 192.168.0.1 (Amiga)
> >> 192.168.0.2 (win95)
> >
> > Umm, where are you putting the second IP? Except for a definition in
> > Hosts, you don't need to predefine the PC's IP, and I'd get numeric
> > pings to work before messing with Hosts.
>
> The second IP is defined on PC-side. Sorry, this was a bit confusing!
>
> >> Subnet-mask 255.255.255.0
> >> Gateway 192.168.0.2
> >
> > Is the PC really supposed to be a gateway to somewhere? If not, this
> > is incorrect. In any case, it's unneeded for local pings.
>
> hm, I addded the 192.168.0.2 in Miami as Gateway and the PC has the ID
> 192.168.0.2
I forgot that Miami insists on having some gateway definition, due to its
PPP roots. If you don't have a real gateway on the LAN (i.e., you're not
using the PC to route net traffic), it's usually best to use a nonexistent
IP, e.g. 192.168.1.254.
This is fixed in MiamiDx, which is perfectly happy to have no gateway on
the LAN.
> >> The LEDs for the Amiga-port and the win95-port are on at the hub.
> >> On the windows-side I created a TCP/IP -> 10 M Ethernet PCI-Adapter
> >> interface for Microsoft Network-Clients with File- and
> >> Printersharing. WINS deactivated
> >> Installed gateways 192.168.0.1
> >
> > Again, you should only add the Amiga as a gateway if it's really
> > going to be a gateway to somewhere, and in any case it's not needed
> > for local pings.
> >
> >> 192.168.0.2
> >
> > Huh? You're making the machine a gateway to itself? And trusting
> > Windoze not to get confused by that?
>
> I donīt understand that one. I made the Amiga as a gateway by
> inserting the 192.168.0.2 in the gatewayfield in the interface.
It looked like you'd defined this on the PC.
If you're using Miami rather than MiamiDx, it's absolutely guranteed that
the Amiga isn't a gateway. :-)
> >> Binds Client for Microsoft-Networks
> >> File- and Printer for Microsoft-Networks
> >
> > If you plan to connect the PC to the net without a firewall, be
> > *very* careful about enabling Microsoft Networking, especially the
> > server side. Unless you plan to use Samba, you're better off leaving
> > Microsoft Networking disabled, since the PC will boot faster and
> > have fewer security holes that way.
>
> Yes, I understand that. But disabling Microsoft-Networking would not
> allow file-sharing, would it?
True, just be careful you're not sharing your files with every cracker on
the net. They like nothing better than to look for open shares or shares
with easily guessable passwords.
> > The LEDs will tell you which machine is sending, which should be
> > both in the case of a successful ping. But MiamiTCPDump will tell
> > you more.
> >
> > You might also try using 192.168.1 addresses instead of 192.168.0,
> > since Holger indicated that some Microsoft software doesn't like
> > 192.168.0.
>
> Yes, you see above. i have changed them to 192.168.1.1 and 192.168.1.2
> but with the same results.
>
> >> I just experienced that when the ethernet-interface is online, I
> >> cannot connect to my ISP....
> >
> > On which machine?
>
> on the Amiga. I get errors with Yam that my ISP is not available.
> Also downloading a file with Voyager fails when the ethernet is
> online.
> Going offline with the ethernet-interface and then online with ppp0
> works then.
Are you using Miami or MiamiDx? In the former case, you obviously can't
have both interfaces online at the same time. In the latter case, make
sure you set the gateway priority to 0 for the Ethernet, or at least to a
lower value than what you use for the PPP interface.
Fred Wright
--
To unsubscribe send "unsubscribe miami-talk-ml" to
"[EMAIL PROTECTED]". For help on list commands send "help" to
"[EMAIL PROTECTED]".
