Newsgroup: it.comp.os.win.win2000
Titolo: Any Ideas: Simple Two Node peer-peer is failing

I have a pretty simple home LAN, but am having some perplexing problems...
Everything was fine one week ago, before I installed Win2000.  I had an NT
4.0 Workstation and a Win98 Workstation...  Both using static IP addresses,
and the NT machine was using RAS to dial out to my ISP, and I also think
that I had long ago installed BetBuei on it. I had shares on the NT machine,
which were persistently mapped on the Win98 box...   Then I decided to
replace the Win98 machine with a new Win2000 Pro workstation, and the
troubles began.
After the Win2000 build was completed (onto a brand new machine) It was able
to get on the network, and to see the NT shares... but any file transfer
over 20 meg would drop the connection (temporarily) and fail.  I reinstalled
Win2000 three times... same thing.  The old Win98 machine (nowl plugged into
a new port on the hub, since Win2000 was occupying the old Win98 port)
continued to work just fine, even with large file transfers.
So next I reinstalled NT 4.0 on the NT workstation.  I did not put NetBuei
on it.  Now I couldn't even see NT from Win 2000 nor could I see Win 2000
from NT...  So I added LMHOST and HOSTS files for the name resolutions.  But
still, pings from one machine to the other just time out.
If I do a NET VIEW from NT 4.0, I only see the NT 4.0 machine.
If I do a NET VIEW from Win2000, I see both the NT 4.0 machine and the
Win2000 machine.
Still, all pings time out.
I am utterly lost as to what may be going on...  Here are the details of the
two machines:
Workstation 1
===============
Machine Name: Clay
OS Version: WinNT 4.0, SP4
LMHOST: 216.0.0.1 CLAY #PRE
                  216.0.0.2 LAURA #PRE
HOSTS: 216.0.0.1 CLAY
              216.0.0.2 LAURA
Workgroup: BEATTY FAMILY
Services: Computer Browser
               NetBios Interface
               RPC Configuration
               Server
               Workstation
Protocols: TCP/IP
Static IP: 216.0.0.1
Subnet: 255.255.255.0
No WINS, No Gateway, No DNS
Adapter NE2000 Adapter
Bindings
    NetBios->WINS Client (TCP/IP) -> Novell NE2000
    Server->WINS Client (TCP/IP) -> Novell NE2000
    Workstation->WINS Client (TCP/IP) -> Novell NE2000
Workstation 2
===============
Machine Name: Laura
OS Version: Win2000 Pro, SP1
No WINS, No Gateway, No DNS
LMHOST: 216.0.0.1 CLAY #PRE
                  216.0.0.2 LAURA #PRE
HOSTS: 216.0.0.1 CLAY
              216.0.0.2 LAURA
Workgroup: BEATTY FAMILY
Installed: Client for Microsoft Networks  ==> Named Service Provider =
Windows Locator
               File and Printer Sharing for Microsoft Networks
               Internet Protocol (TCP/IP)
Static IP: 216.0.0.2
Subnet: 255.255.255.0
Enable Netbios over TCP/IP = True
Any help is GREATLY appreciated!!
-Clay



,

Sent via Deja.com 
http://www.deja.com/
Before you buy.

 wrote in message news:8ref6n$6b4$1...@nnrp1.deja.com...


First of all your IP addresses violate Internet Assigned Names Authority
rules for addresses for private networks. Use class C addresses
beginning with 192.168. This block is reserved for private networks
whereas your addresses belong to someone out there. Also try making your
workgroup name one without spaces -- use the underscore chareacter if
you must. HOSTS and LMHOSTS are probably not needed at all on your
network. But the real issue is that your pings aren't working. That
suggests that it's either a hardware failure of some sort of addressing
failure -- you forgot to include the data from your Windows 98 machine
which is also on the network.
Do this -- tell me 
1.) What kind of network do you have PHYSICALLY? Is it coax, do you have
10/100-base-T or what? If twisted pair cables are used, are the cards in
your 98 and 2000 boxes 10-base-T, 100-base-T or 10/100. I need to know
the same about your hub.
2.) Do "ipconfig" from the 2k and NT machines, and "winipcfg" from the
98 machine and post the output, which should include the hardware
addresses of the cards.
3.) If you can, go out and buy a CROSSOVER cable. This can DIRECTLY plug
one NIC to another, without the need for a hub. This eliminates any
possibility of the hub being the cause.


 I have a pretty simple home LAN, but am having some perplexing
problems...
[Snip]
Try changing your workgroups to be shorter and to not have spaces in
them - this has caused me problems in the past.
Mike.

 wrote in message
news:8redlj$6l2$1...@bob.news.rcn.net...


 wrote in message
news:8redlj$6l2$1...@bob.news.rcn.net...
