Window XP client connectivity with Windows NT 4.0 server?

If this a possibikity? I have a LAN configuration of 4 Windows 98 Second
Edition as client to Windows NY 4.0 Server. I am attempting introduce a
Windows XP Pro workstation into the mix and appear to be having difficulty.
The XP station appears in the network list on all workstations and on the
server. Looking in Server Manager on Server. The XP station is being
identified as a NT 5 Workstation and I cannot gain access to it. I get
success pings from the XP workstation to all other sations and server. The XP
station does not lsit any of the other stations and the server in it network
list.
We are planning a migration in the near future all systems, such as upgrade
of NT 4.0 Server to Windows 2003 Server and all workstations to XP
Professional. However, we did not want to do, as we have some mission
critical applications running don't need any compatibilties issues to bring
us to a halt.
Any suggestions?

What do you mean you are trying to connect to the XP machine from the NT
Server? Using Explorer of the Admin Tools?

I ran a similar setup for quite some time, XP Pro with NT 4.0 Servers
without much issue.

Oh, but bringing in an SBS 2003 server was a lot of fun, in that MS, work
over time kind of way.

The only saving grace to help in your success is if the upgrade consists of
New Machines, not just an upgarde of the Software, that way you can make the
migration slow and fall back to the old machines if needed.

"mort dignet" wrote:

> If this a possibikity? I have a LAN configuration of 4 Windows 98 Second
> Edition as client to Windows NY 4.0 Server. I am attempting introduce a
> Windows XP Pro workstation into the mix and appear to be having difficulty.
> The XP station appears in the network list on all workstations and on the
> server. Looking in Server Manager on Server. The XP station is being
> identified as a NT 5 Workstation and I cannot gain access to it. I get
> success pings from the XP workstation to all other sations and server. The XP
> station does not lsit any of the other stations and the server in it network
> list.
> We are planning a migration in the near future all systems, such as upgrade
> of NT 4.0 Server to Windows 2003 Server and all workstations to XP
> Professional. However, we did not want to do, as we have some mission
> critical applications running don't need any compatibilties issues to bring
> us to a halt.
> Any suggestions?
>

Add a WINS Service to the NT Domain Controller.

Set the WINS Server in the TCP/IP Settings of the XP Pro machine. Join it to
the Domain if it is not already.

The Win9x/NT4 "world" is Netbios (WINS) Based,....the 2000/2003/XP "world"
is DNS based

--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com
-----------------------------------------------------
Understanding the ISA 2004 Access Rule Processing
http://www.isaserver.org/articles/IS...cessRules.html

Microsoft Internet Security & Acceleration Server: Guidance
http://www.microsoft.com/isaserver/t...dance/2004.asp
http://www.microsoft.com/isaserver/t...dance/2000.asp

Microsoft Internet Security & Acceleration Server: Partners
http://www.microsoft.com/isaserver/partners/default.asp

Deployment Guidelines for ISA Server 2004 Enterprise Edition
http://www.microsoft.com/technet/pro...isaserver.mspx
-----------------------------------------------------



"mort dignet" <mort (E-Mail Removed)> wrote in message
news:64B77E6E-C7BF-46A6-9F9A-(E-Mail Removed)...
> If this a possibikity? I have a LAN configuration of 4 Windows 98 Second
> Edition as client to Windows NY 4.0 Server. I am attempting introduce a
> Windows XP Pro workstation into the mix and appear to be having
difficulty.
> The XP station appears in the network list on all workstations and on the
> server. Looking in Server Manager on Server. The XP station is being
> identified as a NT 5 Workstation and I cannot gain access to it. I get
> success pings from the XP workstation to all other sations and server. The
XP
> station does not lsit any of the other stations and the server in it
network
> list.
> We are planning a migration in the near future all systems, such as
upgrade
> of NT 4.0 Server to Windows 2003 Server and all workstations to XP
> Professional. However, we did not want to do, as we have some mission
> critical applications running don't need any compatibilties issues to
bring
> us to a halt.
> Any suggestions?
>

would the same senario be applicable it the workstation was XP Home?

"Phillip Windell" wrote:

> Add a WINS Service to the NT Domain Controller.
>
> Set the WINS Server in the TCP/IP Settings of the XP Pro machine. Join it to
> the Domain if it is not already.
>
> The Win9x/NT4 "world" is Netbios (WINS) Based,....the 2000/2003/XP "world"
> is DNS based
>
> --
> Phillip Windell [MCP, MVP, CCNA]
> www.wandtv.com
> -----------------------------------------------------
> Understanding the ISA 2004 Access Rule Processing
> http://www.isaserver.org/articles/IS...cessRules.html
>
> Microsoft Internet Security & Acceleration Server: Guidance
> http://www.microsoft.com/isaserver/t...dance/2004.asp
> http://www.microsoft.com/isaserver/t...dance/2000.asp
>
> Microsoft Internet Security & Acceleration Server: Partners
> http://www.microsoft.com/isaserver/partners/default.asp
>
> Deployment Guidelines for ISA Server 2004 Enterprise Edition
> http://www.microsoft.com/technet/pro...isaserver.mspx
> -----------------------------------------------------
>
>
>
> "mort dignet" <mort (E-Mail Removed)> wrote in message
> news:64B77E6E-C7BF-46A6-9F9A-(E-Mail Removed)...
> > If this a possibikity? I have a LAN configuration of 4 Windows 98 Second
> > Edition as client to Windows NY 4.0 Server. I am attempting introduce a
> > Windows XP Pro workstation into the mix and appear to be having
> difficulty.
> > The XP station appears in the network list on all workstations and on the
> > server. Looking in Server Manager on Server. The XP station is being
> > identified as a NT 5 Workstation and I cannot gain access to it. I get
> > success pings from the XP workstation to all other sations and server. The
> XP
> > station does not lsit any of the other stations and the server in it
> network
> > list.
> > We are planning a migration in the near future all systems, such as
> upgrade
> > of NT 4.0 Server to Windows 2003 Server and all workstations to XP
> > Professional. However, we did not want to do, as we have some mission
> > critical applications running don't need any compatibilties issues to
> bring
> > us to a halt.
> > Any suggestions?
> >
>
>
>

XP Home won't be joining too any domains unless you can find tools on the
internet to fool it.

"mort dignet" wrote:

> would the same senario be applicable it the workstation was XP Home?
>
> "Phillip Windell" wrote:
>
> > Add a WINS Service to the NT Domain Controller.
> >
> > Set the WINS Server in the TCP/IP Settings of the XP Pro machine. Join it to
> > the Domain if it is not already.
> >
> > The Win9x/NT4 "world" is Netbios (WINS) Based,....the 2000/2003/XP "world"
> > is DNS based
> >
> > --
> > Phillip Windell [MCP, MVP, CCNA]
> > www.wandtv.com
> > -----------------------------------------------------
> > Understanding the ISA 2004 Access Rule Processing
> > http://www.isaserver.org/articles/IS...cessRules.html
> >
> > Microsoft Internet Security & Acceleration Server: Guidance
> > http://www.microsoft.com/isaserver/t...dance/2004.asp
> > http://www.microsoft.com/isaserver/t...dance/2000.asp
> >
> > Microsoft Internet Security & Acceleration Server: Partners
> > http://www.microsoft.com/isaserver/partners/default.asp
> >
> > Deployment Guidelines for ISA Server 2004 Enterprise Edition
> > http://www.microsoft.com/technet/pro...isaserver.mspx
> > -----------------------------------------------------
> >
> >
> >
> > "mort dignet" <mort (E-Mail Removed)> wrote in message
> > news:64B77E6E-C7BF-46A6-9F9A-(E-Mail Removed)...
> > > If this a possibikity? I have a LAN configuration of 4 Windows 98 Second
> > > Edition as client to Windows NY 4.0 Server. I am attempting introduce a
> > > Windows XP Pro workstation into the mix and appear to be having
> > difficulty.
> > > The XP station appears in the network list on all workstations and on the
> > > server. Looking in Server Manager on Server. The XP station is being
> > > identified as a NT 5 Workstation and I cannot gain access to it. I get
> > > success pings from the XP workstation to all other sations and server. The
> > XP
> > > station does not lsit any of the other stations and the server in it
> > network
> > > list.
> > > We are planning a migration in the near future all systems, such as
> > upgrade
> > > of NT 4.0 Server to Windows 2003 Server and all workstations to XP
> > > Professional. However, we did not want to do, as we have some mission
> > > critical applications running don't need any compatibilties issues to
> > bring
> > > us to a halt.
> > > Any suggestions?
> > >
> >
> >
> >

XP Home cannot join a Domain.
But XP (either type) is DNS based, not Netbios based.

--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com

"mort dignet" <(E-Mail Removed)> wrote in message
news:C625BF57-DCAE-4495-B23D-(E-Mail Removed)...
> would the same senario be applicable it the workstation was XP Home?
>
> "Phillip Windell" wrote:
>
> > Add a WINS Service to the NT Domain Controller.
> >
> > Set the WINS Server in the TCP/IP Settings of the XP Pro machine. Join
it to
> > the Domain if it is not already.
> >
> > The Win9x/NT4 "world" is Netbios (WINS) Based,....the 2000/2003/XP
"world"
> > is DNS based
> >
> > --
> > Phillip Windell [MCP, MVP, CCNA]
> > www.wandtv.com
> > -----------------------------------------------------
> > Understanding the ISA 2004 Access Rule Processing
> > http://www.isaserver.org/articles/IS...cessRules.html
> >
> > Microsoft Internet Security & Acceleration Server: Guidance
> > http://www.microsoft.com/isaserver/t...dance/2004.asp
> > http://www.microsoft.com/isaserver/t...dance/2000.asp
> >
> > Microsoft Internet Security & Acceleration Server: Partners
> > http://www.microsoft.com/isaserver/partners/default.asp
> >
> > Deployment Guidelines for ISA Server 2004 Enterprise Edition
> >
http://www.microsoft.com/technet/pro...isaserver.mspx
> > -----------------------------------------------------
> >
> >
> >
> > "mort dignet" <mort (E-Mail Removed)> wrote in message
> > news:64B77E6E-C7BF-46A6-9F9A-(E-Mail Removed)...
> > > If this a possibikity? I have a LAN configuration of 4 Windows 98
Second
> > > Edition as client to Windows NY 4.0 Server. I am attempting introduce
a
> > > Windows XP Pro workstation into the mix and appear to be having
> > difficulty.
> > > The XP station appears in the network list on all workstations and on
the
> > > server. Looking in Server Manager on Server. The XP station is being
> > > identified as a NT 5 Workstation and I cannot gain access to it. I get
> > > success pings from the XP workstation to all other sations and server.
The
> > XP
> > > station does not lsit any of the other stations and the server in it
> > network
> > > list.
> > > We are planning a migration in the near future all systems, such as
> > upgrade
> > > of NT 4.0 Server to Windows 2003 Server and all workstations to XP
> > > Professional. However, we did not want to do, as we have some mission
> > > critical applications running don't need any compatibilties issues to
> > bring
> > > us to a halt.
> > > Any suggestions?
> > >
> >
> >
> >

"mort dignet" <mort (E-Mail Removed)> wrote in message
news:64B77E6E-C7BF-46A6-9F9A-(E-Mail Removed)...
> If this a possibikity? I have a LAN configuration of 4 Windows 98 Second
> Edition as client to Windows NY 4.0 Server. I am attempting introduce a
> Windows XP Pro workstation into the mix and appear to be having
> difficulty.
> The XP station appears in the network list on all workstations and on the
> server. Looking in Server Manager on Server. The XP station is being
> identified as a NT 5 Workstation and I cannot gain access to it. I get
> success pings from the XP workstation to all other sations and server. The
> XP
> station does not lsit any of the other stations and the server in it
> network
> list.

I know for a fact that what you describe works for an NT 4.0 domain runing
SBS. And I also know for a fact that it works in a mixed "workgroup"
environment of Win98 and XP Pro. In both cases, XP Pro was "base" or SP1.
The latter example was my personal in-the-home LAN 3 years ago.

One thing I found is that visibility and access on a Win9X machine in a
workgroup depends if the user on the Win9x machines are logged in using the
username and password fields. And another obstacle to visibility is the use
of firewalls. Either of these may cause machine visibility and file-sharing
issues.


> We are planning a migration in the near future all systems, such as
> upgrade
> of NT 4.0 Server to Windows 2003 Server and all workstations to XP
> Professional. However, we did not want to do, as we have some mission
> critical applications running don't need any compatibilties issues to
> bring
> us to a halt.
> Any suggestions?

I did such a conversion for one of my clients. Here are some of the
compatablility issues I stumbled across going from NT to a Win2000/2003
server environment.

I have found that certain older applications that worked on NT 4 can only
run on XP Pro if the user is logged in an administrator. Otherwise you may
see bogus "permission" type errors. I am not sure why, but I found it out
empirically when trying to get older versions of autocad and Corel to run on
an XP Pro platform. If the security model of your organization precludes
users running as "administrator," you should upgrade to the current versions
of the application first.

You didn't say if your NT LAN was a domain or a work group, or if the server
is running the standard version of NT 4.0 or Small Business System version
4.0 or 4.5. The amount of effort to migrate from an NT domain is greater
than for a workgroup.

Jim