"Alister" <alister.***@hotmail.co.uk> wrote in message
news:922c48cc-418a-45d5-b2a7-69608c0fbbc7@u18g2000pro.googlegroups.com...
> This is probably slightly off topic for this group, but I am
> struggling to get a legacy NT4 machine to connect to our Windows 2000
> domain - or indeed the network!
>
> On the NT4 machine I have TCP/IP and NETBEUI protocols installed.
>
> I can ping 127.0.0.1 and the machine's IP (which is static) but I
> can't ping anything else - default gateway, local DNS server etc.
>
> If I open Network Neighbourhood I can browse to the domain, but the
> only visible machine is itself.
>
> If I plug the same network cable into an XP machine which sits next to
> the NT machine it works fine - so I know there is nothing wrong with
> the physical path.
>
> I can't check the NIC 'cos I don't have another machine with ISA
> slots, but from other clients (XP or Win2k) on the network I can ping
> the NT4 machine's IP and can see the machine if I browse the network,
> but I can't access the shares which are set up on it, which would seem
> to suggest the NIC is OK
>
> You might say "Bin the NT4 and get a proper OS", but I can't. We need
> to run NT4 on this one machine to support a legacy SQL 6.5 database
> which we are working on for a client.
>
> Does anyone remember the tricks necessary to get NT4 to talk over TCP/
> IP?
>
> Thanks
>
> Alister

On Nov 19, 7:35 pm, "Phillip Windell" <philwind***@hotmail.com> wrote:
> 1. Get rid of NetBEUI.  You're only supposed to run TCP/IP
>
> 2.  Install WINS on the DC or other suitable Server.  Make sure that, at a
> minimum, the DC(s) use the WINS and the NT machines uses WINS in the TCP/IP
> config.  Full full functionality you want all machines to use WINS in the
> TCP/IP config.
>
> 3. Use the Netbios name of the Domain when joining the domain or logging
> into it with the NT machine. Make sure the name is not too long and that
> there are no spaces or "dots" in it (remember we are talking about the
> Netbios version of the name here).  I think the name length limit is 15
> characters.
>
> --
> Phillip Windellwww.wandtv.com
>

On Nov 19, 9:36 pm, "Phillip Windell" <philwind***@hotmail.com> wrote:
> "Alister" <alister.***@hotmail.co.uk> wrote in message
>
> news:aaaca10f-009f-4c5d-b68c-2a62deb7215c@k36g2000yqe.googlegroups.com...
>
> > We already run WINS on the DC, so that's ok.
>
> > I will remove NETBEUI though, I thought (wrongly) it was required.
>
> Yea,...Netbios and NetBEUI are two completely different things.  NetBEUI is
> just simply a "Netbios compatible" non-routable transport protocol.  But
> Netbios itself can actually work over TCP/IP as well.
>
> > I haven't got as far as joining the domain, as The NT machine can't
> > see anything on the network,
> > but I would have used the netbios name for that as you say.
>
> > It's a long time since I last played networks with an NT machine. Can
> > you think of any silly gotchas I might have done / not done that would
> > break it ( apart from the netbeui)?
>
> Nothing comes to mind.  It's been about 7 or 8 years for me with NT4.
>
> --
> Phillip Windellwww.wandtv.com
>
> The views expressed, are my own and not those of my employer, or Microsoft,
> or anyone else associated with me, including my cats.
> -----------------------------------------------------

On Nov 19, 9:36 pm, "Phillip Windell" <philwind***@hotmail.com> wrote:
> "Alister" <alister.***@hotmail.co.uk> wrote in message
>
> news:aaaca10f-009f-4c5d-b68c-2a62deb7215c@k36g2000yqe.googlegroups.com...
>
> > We already run WINS on the DC, so that's ok.
>
> > I will remove NETBEUI though, I thought (wrongly) it was required.
>
> Yea,...Netbios and NetBEUI are two completely different things.  NetBEUI is
> just simply a "Netbios compatible" non-routable transport protocol.  But
> Netbios itself can actually work over TCP/IP as well.
>
> > I haven't got as far as joining the domain, as The NT machine can't
> > see anything on the network,
> > but I would have used the netbios name for that as you say.
>
> > It's a long time since I last played networks with an NT machine. Can
> > you think of any silly gotchas I might have done / not done that would
> > break it ( apart from the netbeui)?
>
> Nothing comes to mind.  It's been about 7 or 8 years for me with NT4.
>
> --
> Phillip Windellwww.wandtv.com
>
> The views expressed, are my own and not those of my employer, or Microsoft,
> or anyone else associated with me, including my cats.
> -----------------------------------------------------