[NBLUG/noise] Windows networking

Chris Wagner chriswagner at amyskitchen.net
Mon Jun 5 15:24:15 PDT 2006


Netbeui isn't required for Microsoft networking to work, a TCP/IP
network will handle Netbios just fine and Netbios over TCP/IP should be
enabled by default (look in the TCP/IP properties for the network
adapter).  Enabling Netbeui is generally a bad idea as it is a poorly
designed and rather antiquated protocol.

-----Original Message-----
From: noise-bounces at nblug.org [mailto:noise-bounces at nblug.org] On Behalf
Of Walter Hansen
Sent: Monday, June 05, 2006 3:06 PM
To: Random discussion about anything,including non-Linux stuff.
Subject: RE: [NBLUG/noise] Windows networking

You'll want to check to make sure you have windows networking installed.
For SE, from control panel, right click on networkng and select
properties. You should see your adapters and the protocols loaded. I'm
not sure, but I think you'll need netbui or somesuch for SE to network.
They've elimnated or replaced it with XP. You'll have to enable windows
networking here for it to work. You'll probably want (share my files and
share my printers clicked).

Also make sure that both computers have the workgroup set to the same
thing. Stock is WORKGROUP or MSHOME depending on what version of Win.

> One of the causes behind getting that error message under network 
> neighborhood is when you are only logging into Windows Logon and not 
> 'Client for Microsoft Networks' in Windows 98.  Also, if a user is 
> hitting Escape/Cancel to bypass the logon prompt, the same applies.  
> Is either of these the case?
>
> - Chris
>
> -----Original Message-----
> From: noise-bounces at nblug.org [mailto:noise-bounces at nblug.org] On 
> Behalf Of William Tracy
> Sent: Monday, June 05, 2006 2:39 PM
> To: Random discussion about anything,including non-Linux stuff.
> Subject: Re: [NBLUG/noise] Windows networking
>
> Actually, it's not just that I can't see anything under Network 
> Neighborhood--when I click on it I get the message that it cannot 
> connect to the network. :-P
>
> So, maybe it's not recognizing my ethernet connection as an ethernet 
> connection?
>
> William
>
> _______________________________________________
> noise mailing list
> noise at nblug.org
> http://nblug.org/cgi-bin/mailman/listinfo/noise
>
>
>
> _______________________________________________
> noise mailing list
> noise at nblug.org
> http://nblug.org/cgi-bin/mailman/listinfo/noise
>
>



_______________________________________________
noise mailing list
noise at nblug.org
http://nblug.org/cgi-bin/mailman/listinfo/noise





More information about the noise mailing list