On Mon, 19 Jun 2000, Andreas Meyer wrote:
> Friends, I have pretty much problems here to ping either the Amiga
> from win95 or vise versa.
>
> PING 192.168.0.2 (192.168.0.2): 56 data bytes
> ping: wrote 192.168.0.2 64 chars, ret=-1
> ping: wrote 192.168.0.2 64 chars, ret=-1
> ..........
> --- 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.
> 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.
> 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.
> 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?
> 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.
> DNS deactivated
OK for starters.
> When I start the PC the LED on the hub for its port is flashing
> periodicly. Same when I miamiping the PC but with the results above.
That's Microsoft Networking.
> When I ping from windows-side in a DOS-shell I get three times a
> "Request timed out" emmediatly and thats it.
> I set up Samba but without being able to ping the machines I don�t
> need to try that out.
Amen to that. :-)
> Could someone please help me out of this mess? I tried different ports
> on the hub, diagnostic-tools on the PC-side say the networkcard is
> fine. What am I doing wrong? Why are the LEDs at the hub just flashing
> and that�s all?
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.
> I just experienced that when the ethernet-interface is online, I
> cannot connect to my ISP....
On which machine?
Fred Wright
--
To unsubscribe send "unsubscribe miami-talk-ml" to
"[EMAIL PROTECTED]". For help on list commands send "help" to
"[EMAIL PROTECTED]".
