> Shouldn't that be enough? The win95 machine sees nothing in
> Network Neighborhood except itself. Maybe I have to do something
> in the win95 machine to make it look for novell networks? Or
> is there a way to check on the networking to see if the iPX packets
> are getting re-routed from eth0 to eth1
Try a 'cat /proc/net/ipx_route'. This should print a list of all IPX
networks that the router knows about, including the internal networks in
the file server(s). If there are no entries, then you have a problem with
the IPX interface config. One possibility is the frame type...are you
sure that your network uses 802.3 frames? 802.2 has been the default
since Netware v3.00. You might want to try configuring the IPX interfaces
*without* specifying the frame type, which will cause the adapter to
autosense it based on what traffic it sees going by.
> Since I know nothing about networking, I'm
> without a clue. The only complication I can detect is that our networking
> professionals tell us to use the mask 255.255.252.0 in setting up
> our machines, so the ethernet card that is plugged into the wall has
> that, but I followed the IPMASQ directions and used 255.255.255.0 for
> eth1 and in the win95 machine.
The TCP/IP stuff shouldn't have any effect on the IPX setup.
|Frederick F. Gleason, Jr.|WAVA Radio - 105 FM |Voice: 1-(703)-807-2266 |
| Chief Engineer |1901 N. Moore Street| FAX: 1-(703)-807-2248 |
| |Arlington, VA 22209 | Web: HTTP://www.wava.com|
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
For daily digest info, email [EMAIL PROTECTED]
