>Either that or a standalone (member) server; if you log into the server machine
>rather than a domain, then it's simply a peer-to-peer environment on steroids.

>Look at how other stations access the NT box; if the MS Network Client doesn't
>log into a domain, but into a workgroup, the server is standalone.


> mmmm ... Well the workstation is configured to logon to domain
> Flamingo1. If I take out that set up, the computer can't see
> Flamingo1.

> As of the moment, the network has 1 Novell Server called Flamingo,
> A workgroup called Flamingo.

a little change on previous statement.

I tried logging onto the Window NT Server in a computer
whose client was not configured to log on to the domain Flamingo1
Went to the network neighborhood. Saw Flamingo1 under
Entire Network. Was able to connect to the Server by
mapping on of it's drives.

Tried logging on to Windows NT Server with a user not known
to the NT Server. I still could see it in the Network
Neighborhood but it asked for a password before I could
use the resources.

I don't know if these actions help indicate whether the
server is configured as a Primary Domain Server or a standalone (member) server. I don't think it's a peer-to-peer environment on steroids.

What do you think?