NT4 on a 2000 Domain

  • Thread starter Thread starter Alister
  • Start date Start date
A

Alister

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
 
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 Windell
www.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.
 
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.
Click to expand...


Hi Phil,
thanks for your reply.

We already run WINS on the DC, so that's ok.

I will remove NETBEUI though, I thought (wrongly) it was required.

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)?

Thanks again

Alister.
 
Alister said:
We already run WINS on the DC, so that's ok.

I will remove NETBEUI though, I thought (wrongly) it was required.
Click to expand...

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)?
Click to expand...

Nothing comes to mind. It's been about 7 or 8 years for me with NT4.

--
Phillip Windell
www.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.
-----------------------------------------------------
 
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.



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.
-----------------------------------------------------
Click to expand...

Right!

I tried removing NETBEUI and still had no success.

So I bunged a crossover cable between the NT machine and a 2K machine
on their own little network
using LMHOSTS and nothing else and it still didn't work. It looks as
though the NIC /is/ faulty (its an old ISA SMC 10Mb beasty) so I am
now trying to find an NE2000 or similar in the "I seem to hoard 20 yr
old PC bits" box.

Thanks for your help

Alister
 
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.



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.
-----------------------------------------------------
Click to expand...

Hi Phil,

well, I fixed it!

The network card is an SMC 8416 EtherEZ which, it turns out by default
uses PNP.

NT4 of course, doesn't know about PNP and goes "wibble"

Microsoft KB137475 offers access to a DOS utility which turns off the
pnp features of the card,
after which it was quite happy.

Isn't Google wonderful!

Thanks for all your help

Alister
 
Alister said:
NT4 of course, doesn't know about PNP and goes "wibble"
Click to expand...

There actually is a PNP Utility for NT4 that makes it use PNP (in a somewhat
limited way). It would probably do fine with the Nic as the Nic was. It
also helps with Modems, Sounds Cards, etc.

It is right on the original NT4 CD:

<driveletter:\drvlib\pnpisa\x86

Right-click on the "pnpisa.inf"

Choose "Install"

Reboot

--
Phillip Windell
www.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.
-----------------------------------------------------
 
Back
Top