![]() ![]() | |||||
Quick Search | Power Search | Search Filter | Interest Finder | Browse Groups | Post Message |
Article 2 of 2 | Text Only![]() ![]() |
![]() Previous Article |
![]() Next Article |
![]() Current Results |
![]() View Thread |
![]() Post Message |
Subject: Re: DOS machine on 95 network From: alan denton <eyit@midland.co.nz> Date: 1997/08/05 Message-Id: <33E70D3B.6152@midland.co.nz> Article Segment 2 of 2 (Get Previous Segment) (Get All 2 Segments) > tn> I set up the DOS client with the IPX protocol. I've also tried 802.2 & > tn> 802.3 frame types. However, the last I left it, I also noticed that > tn> the win95 frame type was set to AUTO. Would changing this make any > tn> difference? > >IPX usually works fine. I found I had to fiddle the frame type (I >think 808.2 worked for me on a NT based network, where the frame type >was auto on the nt boxes). I've also successfully used it with NetBEUI >and TCP/IP (the latter is a memory hog though). > I might add my fiddling trying to make IPX go; Give it a network address, like '123'. I also specified 802.2 at first, but now its gone back to 'auto' which gives no problems. If your W95 machine is the Browse Master, choose 'enabled' over 'auto' in the file & printer sharing for MSN. > tn> Does anyone have any clues!? Am I using the right client software, or > tn> is there any others out there I can try? I downloaded this one from > tn> the Microsoft ftp site. > >It does work. However, you may need to manually look at your >AUTOEXEC.BAT and PROTOCOL.INI files. Sometimes SETUP gets a little >confused when installing the client, from my experience (it totally >screwed up TCP/IP and I had to fix it by hand). > > tn> Apologies for the questions. I only half understand what I'm doing, > tn> being fairly new to networking! I'm on a bit of a learning curve... > > tn> Any help would be appreciated. > >No probs. Try NetBEUI and see if you can contact machines on your >subnet. Also, check the basics like your network card's I/O address and >IRQ (though you usually get a message saying "The hardware is not >responding" in this case). Make sure you're not running another network >driver which would conflict with MSClient (e.g. packet driver for TCP/IP >apps). If you need another driver to co-exist, you'll need a shim of >some sort. > BTW I checked this part of USENET for a month or so now. This and other topics come up again and again, and I can 't detect the results of any action ever taken to collect the shared know-how in a document like a FAQ. Is this right ? - Gerry -- | X | gerry@dds.nl | X | Amsterdam, Holland | X | The ultimate medium for the loudmouth & obsessed: USENET
Previous | Next | Results | View Thread | Author Profile | Post Message | Post Reply | Send Email |
Copyright © 1995-97 Deja News, Inc. All rights reserved. |