FIXED: Not all computers see server...
From: Bobby C. (clark_at_dixon-REMOVE-creek.com)
Date: 09/02/04
- Next message: SteveMST: "Re: Cannot Join Remote Workstation to Domain"
- Previous message: Miha Pihler: "Re: How to disable drive mapping by VPN users?"
- In reply to: Robert L [MS-MVP]: "Re: NEWBIE: Not all computers see server..."
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 2 Sep 2004 10:06:13 -0700
Bobby listened carefully from his corner of the padded cell while 'Robert L
[MS-MVP]' said:
Robert,
The NETBIOS over TCP/IP cured the problem and retained my firewall
configuration. Thanks!
> this may help. quoted from http://www.ChicagoTech.net
> NetBIOS and WINS are required in a mixed network
>
> NetBIOS and WINS name resolution is required only on mixed-mode
> (Windows 95, 98, Me, NT, 2000 and XP) networks to provide
> backward-compatibility older versions of Windows. If you have a
> domain mixed-mode network with DHCP and DNS, you are better to create
> WINS in your system. In workgroup mixed-mode network, most people
> enable NetBIOS over TCP/IP to resolve NetBIOS name to equivalent to
> IP addresses.
>
>
>
> "Bobby C." <clark@dixon-REMOVE-creek.com> wrote in message
> news:OnjVNExjEHA.2948@TK2MSFTNGP11.phx.gbl...
>> First a quick bit of background, hopefully this is enough. If not,
>> yell at
>> me and I'll supply a more.
>>
>> I have a small home office system with three machines for
>> development and testing. One running Win2K Pro (my main development
>> machine). Another is running XP Pro and is the one that we keep the
>> company books on. The final
>> machine is running Win98 SE (testing only).
>>
>> I have added a fourth machine to the network which I've installed
>> Server 2003 on and I'm trying to get the connections to work
>> properly. The previous three machines all are/were running
>> peer-to-peer and are currently
>> using NETBEUI. This was due to needed to connect with older machines
>> (which
>> have since died) and not understanding how to make TCP/IP work for
>> that. After installing the server software and making the new server
>> a member of the workgroup I can see the Win98 machine and it can see
>> the server. The Win2K and XP machines cannot see the server and
>> vice-versa. I suspect that
>> for proper networking I need to convert all the systems over to
>> TCP/IP but I'm not sure.
>>
>> These machines are behind a hardware firewall/router and connected
>> to a cable modem. We get the IP addresses dynamically from the DHCP
>> supplied by
>> the firewall/router. If I may ask a few dumb questions:
>>
>> Is there a good reference book on the best way to configure the
>> network and
>> the server? One maybe geared for small office networks and not
>> assuming that I'll setting up new servers on massive networks.
>>
>> Do I need to eliminate NETBEUI on the Win2K and XP machines and
>> strictly use
>> TCP/IP for all networking for this to work?
>>
>> If so, do I need to use a static IP address internally (from one
>> machine to
>> the next) or can they be dynamically created?
>>
>> If they can be dynamically created, am I right in assuming that I
>> have to have the server act as a DHCP server for one of it's roles?
>>
>> Sorry for the dumb questions.
>>
>>
>> --
>>
>> Bobby C.
>> Proper reply address is without the text -REMOVE-
>>
>> "If You're Not A Part Of The Solution, There's Good Money To Be Made
>> In Prolonging The Problem." - from the 2002 Despair series posters
>> entitled "Consulting"
-- Bobby C. Proper reply address is without the text -REMOVE- "If You're Not A Part Of The Solution, There's Good Money To Be Made In Prolonging The Problem." - from the 2002 Despair series posters entitled "Consulting"
- Next message: SteveMST: "Re: Cannot Join Remote Workstation to Domain"
- Previous message: Miha Pihler: "Re: How to disable drive mapping by VPN users?"
- In reply to: Robert L [MS-MVP]: "Re: NEWBIE: Not all computers see server..."
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
