R
Richie Broome
I have a group of people in and one of them has a Windows
2000 Pro laptop that is joined to their own domain. They
do NOT want to be joined to my domain. I go in for my NT
4.0 domain and give them a static ip address, gateway,
dns, and wins (which works for everyone else that has XP
pro laptops) to access our network shares and printers
after being prompted for a username/password.
In his case when i try to go to a share be by name or the
ip addess of the machine I get a message.
\\machinename is not currently accessible
There are currently no login servers availible to service
the login request.
Anyone know why this works with XP but not 2000 pro?
2000 Pro laptop that is joined to their own domain. They
do NOT want to be joined to my domain. I go in for my NT
4.0 domain and give them a static ip address, gateway,
dns, and wins (which works for everyone else that has XP
pro laptops) to access our network shares and printers
after being prompted for a username/password.
In his case when i try to go to a share be by name or the
ip addess of the machine I get a message.
\\machinename is not currently accessible
There are currently no login servers availible to service
the login request.
Anyone know why this works with XP but not 2000 pro?