Re: Win95 and WinXP Workgroup - troubleshooting shares

On Sat, 1 Oct 2005 12:15:42 -0700, "SeaMaid" <seamaid24-graphics@xxxxxxxxx>
wrote:

>"Chuck" <none@xxxxxxxxxxx> wrote in message
>news:ai8tj1h0ctqg9sirc4k8g5lniqsrj0qmed@xxxxxxxxxx
>> On Sat, 1 Oct 2005 06:31:02 -0700, "SeaMaid" <*deleted*> wrote:
>>
>>>Computer A
>>>Windows XP Pro SP2
>>>Network Protocols: TCP/IP
>>>
>>>Computer C
>>>Windows 95a
>>>Network Protocols: IPX/SPX, NetBEUI, TCP/IP
>>>"Chuck" <none@xxxxxxxxxxx> wrote in message
>>>news:h4vsj11ef9u35ka3r47etqtgvbi5gfh8fq@xxxxxxxxxx
>>>> On Sat, 1 Oct 2005 03:06:24 -0700
>>>>
>>>> David writes of security between the WAN (Internet) and LAN (your
>>>> computers)
>>>> sections of your NAT router. There is no firewall between the
>>>> individual
>>>> LAN
>>>> ports, and you cannot isolate your individual computers, from each
>>>> other,
>>>> using
>>>> any router settings.
>>>
>>>I'm not trying to isolate the computers from each other. The
>>>router/gateway
>>>has a hardware firewall that protects all PCs on the network. ZoneAlarm is
>>>a
>>>software firewall that protects each PC individually in addition to that
>>>hardware firewall.
>>>
>>>> You can damage the functionality of the individual computers by
>>>> misconfiguration
>>>> (though not permanently). You can do name resolution without NBT, but
>>>> this will
>>>> require additional work. NetBIOS name resolution is the preferred
>>>> solution, and
>>>> if you insist on shutting it off while you "troubleshoot a hardware
>>>> problem",
>>>> you could be causing your problems there. Please read some of my
>>>> articles,
>>>> which should allow you some background.
>>>> <http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html>
>>>> Chuck
>>>
>>>What is NBT? NetBIOS name resolution is fine if I can figure out what it
>>>is
>>>and how to use it. I do not know what you mean by "shutting it off". Do
>>>you
>>>mean shutting off NetBIOS? If it should not be shut off in my particular
>>>network, that's fine. Just let me know.
>>>
>>>The Win95 computer has had this problem for a long time.
>>>
>>>The Win98 computer has not been used for a while. It got the same prompt
>>>when trying to connect to Computer A. The Win98 PC is the only one that
>>>has
>>>been disconnected from the network because it has other problems. Its
>>>external Bantam Backpack CDROM driver is corrupt, and the internal hard
>>>drive may be failing. Yesterday, it would not boot at all. The BIOS did
>>>not
>>>even detect that a hard drive was connected. Today it sees the drive, but
>>>there are still problems. It's very old (Compaq LTE5300). At least I have
>>>retrieved most of the data from it already. Bantam has the Backpack
>>>drivers
>>>available for download should a reinstall be needed on a new hard drive.
>>>Those issues will be addressed in a Win98 newsgroup.
>>>
>>>Misconfiguration may be in my Windows XP Services on Computer A. I posted
>>>them earlier. Please review them and see if anything raises red flags. I
>>>will be reading the articles on your site later today. I have been up all
>>>night and need to sleep now.
>>
>> I'm a techie. We never sleep. ;-)
>>
>> Seriously, the multiple protocols are going to be a problem. Plus, a
>> protocol /
>> transport on just one computer is useless. Plus, it will cause problems
>> with
>> file sharing.
>>
>> Windows Explorer will look for other computers on all transports, because
>> it
>> assumes that you want to see everything out there. If you have IPX/SPX,
>> NetBIOS
>> Over TCP/IP (aka NBT), and NetBEUI all involved in file sharing, the
>> browser
>> service on your computer (this should not be confused with Internet
>> Explorer or
>> its competitors) has to wait for response (or no response) from each
>> transport
>> before continuing. If no other computer uses a given transport, you are
>> wasting
>> computer time.
>>
>> Computers in a domain require additional attention to detail. Making a
>> computer
>> with XP work on an AD domain is not a simple task. Here's some more
>> reading for
>> you.
>> <http://nitecruzr.blogspot.com/2005/05/windows-xp-on-nt-domain.html>

>I am not in a domain, have no servers, and do not think I have Active
>Directory (AD). Isn't AD just part of server operating systems like Win2000
>Server, Win2000 Advanced Server, and Windows Server 2003? This is a
>stand-alone workgroup in a home.

OK, dunno where I got the AD bit.

You do need NetBIOS Over TCP/IP enabled. The "Default" setting is for a
corporate network, where the DHCP server provides the NBT setting as On or Off.
A NAT router won't provide this setting, so you need to ensure that NBT is ON,
by setting it ON on all computers.
<http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html#Components>

NBT is a Transport, that works when combined with the TCP/IP protocol. IPX/SPX
and NetBEUI are alternate protocols. Duplicate protocols / transports mean
excessive computer load, and excessive network traffic.
<http://nitecruzr.blogspot.com/2005/07/windows-networking-and-alternate.html>

You do need to check your file permissioning, too. Classic vs Simple File
Sharing, and Guest vs non-Guest authentication, must be setup properly. This
is, admittedly, not a simple task. And it's more complicated with multiple and
legacy operating systems like Windows 95.
<http://nitecruzr.blogspot.com/2005/06/file-sharing-under-windows-xp.html>
Chuck
Paranoia comes from experience - and is not necessarily a bad thing.
.

Relevant Pages

  • Re: Capturing Windows Login Name
    ... annoyance of typing their user names and passwords again. ... that among other protocols supports NTLM. ... server in the last step, ... a site under the same Windows controller domain, ...
    (comp.lang.php)
  • Re: Workgroup
    ... I have one XP Home used as a file server and 5 other PCs ... >>protocols are installed, it can access the internet, ... >than one protocol can make the network unreliable, ... >Windows XP Network Protocols ...
    (microsoft.public.windowsxp.network_web)
  • Re: INTERNET ACCESS/RESPONSE PROBLEM
    ... The server could not bind to the transport %1. ... If network devices are working properly, and the event status code is 9A, ... Windows NT-Based Computer ...
    (microsoft.public.windowsxp.general)
  • Re: INTERNET ACCESS/RESPONSE PROBLEM
    ... The server could not bind to the transport %1. ... If network devices are working properly, and the event status code is 9A, ... Windows NT-Based Computer ...
    (microsoft.public.windowsxp.help_and_support)
  • Re: SBS 2003 VPN
    ... >> From Help VPN Protocols: The following network protocols have been ... >>> Windows 2000 and its newsgroup, I also posted this question there. ... >>> I am using Windows Server 2003 Standard for Small Business Server. ... I have tried the Remote Access wizard in Server ...
    (microsoft.public.windows.server.sbs)
Loading