Lonely NT Server on a 2003 Domain

Archived from groups: microsoft.public.win2000.setup_deployment (More info?)

Recently we upgraded our NT domain to 2003 by creating a new NT BDC,
promoting it to PDC and then upgrading it. Everything has beenworking fine,
except for our NT machines. I have an NT Server that is simply a domain
member that will not connect to the network, nor will 2 lone NT Client
machines. All have SP 6. The server is configured with a static IP, and is
in the DNS. Active directory is set up in Windows Server 2003 Interim mode
because of these old NT servers (the old NT PDC, now BDC does not like
everything either, but at least it talks). I've tried digging through group
policy settings and active directory settings to see if I can find anything
relevant but to no luck. I know that the books all say that NT servers
*should* work in Interim mode, so I'm a bit stuck.

The renegade NT machine is a server only. Running SQL Server 7 and IIS.
When the server is brought up, it will not connect, rather saying that it's
using a cached profile. Web services on another machine can reach the SQL
Server, but the web sites on the machine cannot reach another SQL Server 2000
database.

I plan on moving either the server up from NT, or moving services off of it
and removing it entirely. However, I need to try and fix this networking
problem now so that we can make the next steps in a controlled incremental
manner.

Any thoughts anyone? I appreciate all the help I get here. Thanks.