WIN95 to Unix via ethernet, help
ray crossley
i'm trying to connect a win95 machine to a unix machine, but they refuse to
even ping each other. i believe both machines are properly configured -- i've
successfully connected linux and unix before (why i don't just run linux now
is a long story.
my guess is that win95 doesn't provide the appropriate client software to
make this connection. any recommendations?
if it matters, the unix box is an indy.
thanks,
ray crossley
John R Buchan
In article <crossley.4...@libertynet.org>, cros...@libertynet.org
says...
First, is your network functional?
Can you ping each machine by IP?
You mentioned that you had done this with linux. Was this linux installed
on the same system that 95 is currently on? This would pretty much rule
out hardware problems, except a misconfiguration of the net card in 95.
What type of 'connection' are you referring to?
If your network is functional and you have the appropriate software (both
server and client), you should be able to 'connect' with FTP, Telnet, etc.
If you are trying to 'map a drive', you will need to run Lan Manager on
the unix system.
--
John R Buchan
j.bu...@worldnet.att.net
ray crossley
win95 states that my hardware is working properly, though i don't entirely
trust win95. i know the indy hardware is functional.
the machines can ping themselves but not each other. ftp and telnet fail.
yes i did have linux installed on another pc. i'm only running win95 after
failing to get it, with pcmcia card services, running on this laptop.
as i said, i suspect it's the client software provided with win95. though i
don't know enough about tcp/ip to be certain, the clients seem to be for
strictly wintel-to-wintel platforms.
i'm looking for pointers to some good (read free or cheap) software for
cross-platform tcp/ip over ethernet.
thanks.
John R Buchan
In article <crossley.5...@libertynet.org>, cros...@libertynet.org
says...
Are you pinging by IP or by name? It makes a considerable difference. If
pinging by IP fails, you have a basic network or TCP/IP config problem.
If pinging by IP works and pinging by name fails, you have a name
resolution problem.
You need to get the basic network and TCP/IP functional before you worry
about FTP, telnet or any other apps.
Gordon McAndrew
cros...@libertynet.org (ray crossley) wrote:
;>>> i'm trying to connect a win95 machine to a unix machine, but
they
;>>refuse to
;>>>even ping each other. i believe both machines are properly configured
;> win95 states that my hardware is working properly, though i don't
entirely
;>trust win95. i know the indy hardware is functional.
;> the machines can ping themselves but not each other. ftp and telnet
fail.
You have something basic wrong with your connection between the two
machines.
Win95 has all the functionality to do a Win95 to Unix connection. The
ping has to work before anything else will work. You just need the TCP/IP
protocol set up.
Are you networking these machines with ethernet? Coax or UTP? Terminators
on the Coax. Special UTP wire for direct links. HUB?
As you can see you have provided us with too little info to help much.
Gordon McAndrew
LAN Manager,
Alberta Environmental Centre,
Vegreville,
Alberta, Canada
gmca...@aec.env.gov.ab.ca Home
gor...@aec.env.gov.ab.ca Office
gor...@vegnet.afternet.com
ray crossley
all's well now. my problem was caused by:
a trumpet winsock, which when installed likes to create a path
statement pointing to itself, causing all tcp/ip commands to be
interpreted as commands to an internet server
and/or:
my attempt to configure both a pcmcia socket controller and a
network adapter, which makes perfect sense until you think
about it for a few minutes. (you should configure just the
network adapter.)
so, until the next slackware linux release, i'm quite happy with
win95.
thanks.
>First, is your network functional?
>>> Can you ping each machine by IP?
>>>
>>>You mentioned that you had done this with linux. Was this linux installed
>>>on the same system that 95 is currently on? This would pretty much rule
>>>out hardware problems, except a misconfiguration of the net card in 95.
>>
>>
>>
>>>What type of 'connection' are you referring to?
>>
>>>If your network is functional and you have the appropriate software (both
>>>server and client), you should be able to 'connect' with FTP, Telnet, etc.
>>
>>>If you are trying to 'map a drive', you will need to run Lan Manager on
>>>the unix system.
>>
>>>--
>>>John R Buchan
>>>j.bu...@worldnet.att.net
>>
>> win95 states that my hardware is working properly, though i don't
>entirely
>>trust win95. i know the indy hardware is functional.
>> the machines can ping themselves but not each other. ftp and telnet
>fail.
>>
Ray Reid
John R Buchan (j.bu...@worldnet.att.net) wrote:
: In article <crossley.4...@libertynet.org>, cros...@libertynet.org
: says...
: >
: > i'm trying to connect a win95 machine to a unix machine, but they
: refuse to
: >even ping each other. i believe both machines are properly configured -- i've
: >successfully connected linux and unix before (why i don't just run linux now
: >is a long story.
: > my guess is that win95 doesn't provide the appropriate client software
: to
: >make this connection. any recommendations?
: > if it matters, the unix box is an indy.
: First, is your network functional?
: Can you ping each machine by IP?
:
: You mentioned that you had done this with linux. Was this linux installed
: on the same system that 95 is currently on? This would pretty much rule
: out hardware problems, except a misconfiguration of the net card in 95.
: What type of 'connection' are you referring to?
: If your network is functional and you have the appropriate software (both
: server and client), you should be able to 'connect' with FTP, Telnet, etc.
: If you are trying to 'map a drive', you will need to run Lan Manager on
: the unix system.
: --
: John R Buchan
: j.bu...@worldnet.att.net
I have managed to Link up a PC running Slackware Linux 3.0 and another
PC which dual boots either Linux/NTWS4.0/Win95.
The major problem I had was the port and IRQ settings on the net cards.
I found that even if Windows/Linux correctly detects you're card
you won't be able to ping each other if the port addresses on the net cards
are not spot on; Eg Windows say's Yeah I know this card but network
stops there.
Linux bootup is a good mechanism for detecting net card config.
TIP:Try various port addresses.
dde...@physics.utoronto.ca
In <51mr1c$j...@badger.wmin.ac.uk>, ob...@westminster.ac.uk (Ray Reid) writes:
>John R Buchan (j.bu...@worldnet.att.net) wrote:
>: In article <crossley.4...@libertynet.org>, cros...@libertynet.org
>: says...
>: >
>: > i'm trying to connect a win95 machine to a unix machine, but they
>: refuse to
>: >even ping each other. i believe both machines are properly configured -- i've
>
>The major problem I had was the port and IRQ settings on the net cards.
>
>I found that even if Windows/Linux correctly detects you're card
>you won't be able to ping each other if the port addresses on the net cards
>are not spot on; Eg Windows say's Yeah I know this card but network
>stops there.
>
>Linux bootup is a good mechanism for detecting net card config.
>TIP:Try various port addresses.
I agree. I have installed a number of Win95 machines using "Plug and Play"
hardware, and pretty much universally the Win95 install found the wrong
settings. Most Network cards come with a utility (or you can get one off
the 'net - although that's a bit of a chicken and egg thing - which sniffs
out your port (address) and IRQ. Then, when you do the card's install in
Win95 force it to use those settings, even if it tells you that you are wrong.
________________________________________
David Demmer
Ontario Laser and Lightwave Research Centre