XP networking without NetBIOS or Active Directory

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: v8625 (v8625_at_hotmail.com)
Date: 04/01/04


Date: 31 Mar 2004 19:43:01 -0800

Need to network a few XP machines, Windows 2003 (standalone) server
and a Linux box (obviously needs Samba to talk to Windows). Setting up
Active Directory would require setting up a domain, a DNS server and
all that other good stuff that I am actually trying to avoid because
some of the machines, including Windows server, can be powered down at
times.
I would also like to keep things secure and block all NetBIOS traffic
on ports 135-139. Sufficient networking can be had with "NET USE" or
by running \\hostname\sharename in Windows Start>Run. I would still
keep port 445 for Samba.
1. Does it make sense?
2. Is there anything else I could do to improve
security/reliability/performance?



Relevant Pages

  • SecurityFocus Microsoft Newsletter #154
    ... MICROSOFT VULNERABILITY SUMMARY ... ISS RealSecure Server Sensor SSL Denial Of Service Vulnerabi... ... Roger Wilco Remote Server Side Buffer Overrun Vulnerability ... available for Microsoft Windows operating systems. ...
    (Focus-Microsoft)
  • SecurityFocus Microsoft Newsletter #49
    ... Subject: SecurityFocus Microsoft Newsletter #49 ... Microsoft Windows NNTP Denial of Service Vulnerability ... Microsoft IIS SSI Buffer Overrun Privelege Elevation Vulnerability ... Microsoft ISA Server H.323 Memory Leak Denial of Service... ...
    (Focus-Microsoft)
  • Re: Fileserver question
    ... >> another box running both 9.0 and Windows. ... >> computers in the same room and connected to a router. ... otherwise you will need to run a DHCP server on one ... > of the machines, preferably the server, or give both machines static ...
    (alt.os.linux.suse)
  • nslookup times out on some WinXP clients
    ... Basically, nslookup times out on some Windows machines, but not on others. ... we currently have a Windows 2000 Server DNS & DHCP Server serving IP ...
    (RedHat)
  • Re: New: LanMan98 V2 Not connecting
    ... all) Windows machines, the computer name as found in the system ... essentially Windows was rejecting the connection because it hadn't ... LanMan98 appears to be one, ... uses a low-level message protocol called SMB (Server Message Block). ...
    (comp.sys.acorn.networking)