login problem

[aego]

I have a win nt domain and a windows workgroup. When i login to the network with a windows 98 computer from the windows workgroup, all is fine. It logs on to the nt domain, login scripts are executed, shares are shown.

Now i want to do the same with w2k pro workstation. however after looking several times ( and yes, restarting too!!!) no luck.

Am i missing something here - probably yes - or is this just the case with W2K professional ?

 

[rstockton]

Have you added the win2k machine to the Domain?

 

[gman10]

Unless the machine is in the domain, you won't have much luck rstockton is correct

 

[aego]

i have added the machine to the domain (and removed it again too (it still did not work).

i feel i have to elaborate. i only wanted to use the domain as i did under windows nt & 98 :
a situation where i have a number of workgroups ( win98 ) which use a central nt domain for network logon and sharing of resources. the users are all members of different groups ofcourse, and only a select number of users have rights to shares and resources on the domain itself. the rest uses the network to gain internet access (which works fine!).

There are already windows 2000 machines member of the domain. This machine should not be, the situation does not allow this : 2 community organisations and limited resources, which use a single server for a number of reasons.

when i read the remarks, i am horrified to think i have to set up a server (for just 2 client computers!!) or make the workstation(s) a member of the domain

i thought i had a set-up which would work.

any help is greatly appreciated

 

[coach42]

Did you join the domain from the workstation side? If not go into Network and Dialup Connection and click on Network Identification. Then chose either Network ID or Properties and follow the prompts. Hope this helps

 

[yizhar]

HI!

W2K uses DNS as the primary name resolution service.
Adding an entry in the HOSTS file on the W2KPRO
(WINNT\SYSTEM32\DRIVERS\ETC) might help,

or a better solution is to implement an internal
DNS server on your NT server.
This needs more configuration and knowledge but improves performances and may solve problems like this and also
Outlook2000 and MSExchange slow startup problems.
You then configure your ISP DNS servers in the "Forwarders" tab in DNS configuration.
You may create a fake DNS domain name, like mycompany.local,
configure a primary ZONE on your DNS server with an entry for your server like
myserver.mycompany.com = x.x.x.x
and configure all clients (and servers) with your internal DNS server as the primary DNS, and also DNS DOMAIN NAME as
"mycompany.local".
This configuration works fine for me.

Bye

Yizhar

Yizhar Hurwitz

http://come.to/yizhar

http://teachers.sivan.co.il/yizhar