Hi Ben

>They would not connect with TCP/IP alone.
If the IP Addresses were within the same sub-net then they were connected,
just not in a way that was useful to you. In order for you to run TCP/IP
only you would have had to make sure the NetBios under the TCP/IP properties
is allowed. and then you would need to deal with name resolutions. Poormans
Name Resolution is to setup LMHOST files on each machine with would link IP
address to System Name (ie. 10.0.0.1 = Win95Sys). one thing to what out for
on net is to not bind netbios to tcp/ip.

>I thought I had seen a comment on the list warning against
>multiple protocols as packets would be sent for each.

I have run System with IPX, NetBios, and TCP/IP running and have noticed any
problems, but with security I have dropped to mainly TCP/IP and NetBEUI

>Or is TCP/IP not a ??stand-alone?? protocol.
TCP/IP is stand alone.

How were your IP Addresses Setup. Static or Dynamic from a DHCP Server?
Some would argue with me on this, but I prefer Static in the either of
to of the non-routable IP ranges provided (10.0.0.0 or 192.168.0.0).

Ben Johansen - www.pcforge.com
list commands: www.pcforge.com/WiTangoTalk.htm

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On
Behalf Of Ben Petersen
Sent: Thursday, August 16, 2001 6:22 AM
To: [EMAIL PROTECTED]
Subject: RE: Off topic network Q


Ben,

Had TCP/IP and IPX/SPX on the laptop.  Those and others were
installed on the NT Server.  In that configuration the 95 machine
saw the NT Server machine as a server but NT Server didn't see the
95 machine as a server.

I removed IPX/SPX from the laptop and installed NetBEUI on both.
Now all seems to work fine.

Now another naive question. They would not connect with TCP/IP
alone.  I thought I had seen a comment on the list warning against
multiple protocols as packets would be sent for each. Or is TCP/IP
not a ??stand-alone?? protocol.

Thanks,

Ben Petersen

On 15 Aug 2001, at 16:09, Ben Johansen wrote:

> Hi Ben
>
> What protocols are you running. (ie. Netbios, TCP/IP)
>
> you need to setup sharing on your 98 system under network neighborhood
> then you need to right-click on a drive or a folder and select sharing,
just
> follow the dialog box.
>
> Security issues: if both systems are on the Internet then don't bind
Netbios
> to TCP/IP
>
> if when you go into network neighborhood you don't see the system listed,
> then try right-clicking on network neighborhood and select "find computer"
> and type the name of the win98 system
>
> if you are running tcpip only and you enable the netbios over tcpip then
you
> can edit a file called "LMHOSTS" (enter "hosts" under find file) if you
only
> see a LMHOSTS.SAM file then copy it to a file called "LMHOSTS" (no
> extension) and open it in notepad and you will see instructions in there
for
> linking an IP address to a netbios name
>
>
> Ben Johansen - www.pcforge.com
> list commands: www.pcforge.com/WiTangoTalk.htm
>
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On
> Behalf Of Ben Petersen
> Sent: Wednesday, August 15, 2001 7:29 AM
> To: [EMAIL PROTECTED]
> Subject: Off topic network Q
>
>
> Hi all,
>
> Since the list has been slow for a couple days I thought I'd ask a
> dumb question.
>
> I develop on a machine running NT server.  I have my laptop (win
> 98) networked to it for testing and misc.  I've also configured my
> laptop as a server, or at least on a peer to peer network it would
> show as a server.  But the desktop machine doesn't recognize the
> laptop as a server.
>
> Not a big deal, but inquiring minds....
>
> Thanks,
>
> Ben Petersen
>
>
>
>



Reply via email to