Help!!! Win95/98 Networking Problem
Mr. Floppy
Windows 98/2000. Both PC's have the same NE2000 compatible NIC that are
known to be working fine. Both PC's have different names but the same
workgroup names. Each PC can see itself in network neighborhood but not the
other PC. I have files shared on each PC. I currently have TCP/IP and
NetBEUI installed on both PC's. I have tried allowing auto addressing of
the NIC and now have static addresses on both NIC's (169.254.137.73 and
169.254.137.74 both w/ subnet mask 255.255.0.0). I have even tried IPX/SPX
but neither PC can see the other. Am I doing something wrong? Any help is
appreciated. Thanks in advance. Scott
Mr. Floppy
network running fine under Windows 3.1/Dos. I am not using a hub but have a
cross over cable instead.
"Mr. Floppy" <scott...@yahoo.com> wrote in message
news:JiXa7.764$N42....@newsread1.prod.itd.earthlink.net...
mike schmidt
Have you tried to ping the other computers to confirm communications?
Also do you have file and printer sharing turned on?
"Mr. Floppy" <scott...@yahoo.com> wrote in message
news:JiXa7.764$N42....@newsread1.prod.itd.earthlink.net...
Brian {Hamilton Kelly}
scott...@yahoo.com "Mr. Floppy" writes:
Have you tried NET commands from an MS-DOS command prompt window? For
example
NET VIEW
ought to list both hosts; even if it doesn't
NET VIEW \\OTHERHOST
ought to list the shares available on \\OTHERHOST
With TCP/IP, can each machine ping the other's address? If not, go back
to basics and check the NICs, using the manufacturer's diagnostic program
(you'll probably need to boot into raw DOS to do this, maybe even from a
floppy).
IME, when this "invisibility" occurs (with a /working/ network) it's
because neither machine has decided to be a Browse Master, and hence
neither is looking for other computers on the net. One way to make
things more visible is to switch on LMAnnounce (under the "File&Print
Sharing" service's Properties: in theory this is unnecessary, but it
certainly seems to speed up the revelation of each machine to the others.
Oh, one other thing: IIRC, Win2K only supports NETBIOS over TCP/IP, and
thus having the NETBEUI protocol specified on a Win95/8 machine will
leave each invisible to the other. I suggest remove NETBEUI altogether
(unless needed for some other sharing) and enabling "I want to use
NETBIOS over TCP/IP" on the TCP/IP protocol's Properties.
Any or all of these aspects may be factors in your situation.
--
Brian {Hamilton Kelly} b...@dsl.co.uk
"We have gone from a world of concentrated knowledge and wisdom to one of
distributed ignorance. And we know and understand less while being incr-
easingly capable." Prof. Peter Cochrane, formerly of BT Labs
val harrop
Here is a checklist:
http://www.wown.com/j_helmig/netcheck.htm
If you can use start - find - <computername> and share your network
resources in that manner, you probably have a network neighborhood problem
and not a network problem. Network Neighborhood can take 15 minutes or more
to sort itself out. Sometimes this can be helped by enabling browse master
on one machine and disabling it on the other.
Val
ahmad kamal sulong
perhaps u just can't see it in network neighbourhood but it's there. try to ping
each other and see
but first, change your subnet mask to 255.255.255.0 because you are using only 2
pcs
Brian {Hamilton Kelly}
so that it's obvious why Mr Floppy should NOT change his subnet mask]
In article <3B70A9D4...@pointnetwork-asia.com>
kam...@pointnetwork-asia.com "ahmad kamal sulong" writes:
> > "Mr. Floppy" <scott...@yahoo.com> wrote in message
> > news:JiXa7.764$N42....@newsread1.prod.itd.earthlink.net...
> > > I have an old 486 running Windows 95 and a Pentium II dual booting between
> > > Windows 98/2000. Both PC's have the same NE2000 compatible NIC that are
> > > known to be working fine. Both PC's have different names but the same
> > > workgroup names. Each PC can see itself in network neighborhood but not
> > the
> > > other PC. I have files shared on each PC. I currently have TCP/IP and
> > > NetBEUI installed on both PC's. I have tried allowing auto addressing of
> > > the NIC and now have static addresses on both NIC's (169.254.137.73 and
> > > 169.254.137.74 both w/ subnet mask 255.255.0.0). I have even tried
> > IPX/SPX
> > > but neither PC can see the other. Am I doing something wrong? Any help
> > is
> > > appreciated. Thanks in advance. Scott
>
> perhaps u just can't see it in network neighbourhood but it's there. try to
> ping each other and see
Being able to ping TCP/IP traffic through is not necessarily an
indication that hosts and shares will be visible at the NetBIOS level.
As I already explained, his problem is likely to be that the Win2K
machine is encapsulating that traffic in TCP/IP, whilst the Win95 one is
putting it out in the NETBEUI packets.
Therefore the packets are whooshing past each other on the net, and being
ignored. He probably should abandon NETBEUI altogether, or if it's
essential for some other reason, ensure that "I want to use NetBIOS
through TCP/IP" is UNticked on the TCP/IP properties.
> but first, change your subnet mask to 255.255.255.0 because you are using
> only 2 pcs
He might well be using only two machines; however, if you look at the
network addresses, I suspect that he has been allocated these and not
chosen them for himself. [169.254.137.73] and [169.254.137.74] are not
addresses that anyone may allocate for themselves: the ranges for that
are defined in RFC-1918. As such, these addresses that he's using are in
an assigned NETBLK which covers all of [169.254.0.0--169.254.255.255],
which in modern terminology is the net 169.254/16 and was once known as
"an entire Class B"; so the correct netmask IS 255.255.0.0.
If I am mistaken and he has allocated these numbers to himself, then he
should change them to one of the ranges mandated in RFC-1918:
10.0.0.0 -- 10.255.255.255 (10/8) 255.0.0.0
172.16.0.0 -- 172.31.255.255 (172.16/12) 255.224.0.0
192.168.0.0 -- 192.168.255.255 (192.168/16) 255.255.0.0
(The final column shows the netmask for the entire range allocable in
each of these blocks; many people prefer to "feel comfortable" with the
idea of an old-fashioned Class C in 192.168.0.0, and use 255.255.255.0,
which was, I believe, your reason for making your erroneous assertion.)
The essential point is that the netmask DOES need to be the same on both
ends of the link; IME, Microsoft's TCP/IP *will* work with the netmasks
set differently (so long as the address bits, collated with the mask,
match) so that ping operates correctly, BUT the NetBIOS over TCP/IP
doesn't work. Don't ask me how M$ manage this supreme feat of
engineering skill: I think personally that they fucked up.