kiritk
asked on
Cannot access \\ip adress\C$ from Win2k3 server to Win2k server- workgroup
I cannot access \\ip adress\C$ from Win2k3 server to Win2k server, which is justin workgroup mode.
I can access from Win2k server to that workgroup win2k server box, but not from any win2k3 server.
I can ping\access from workgroup box to win2k3 server, but not viceversa.
In says, you are not authorized to logon using this account......something like this error.
I am trying to use local win2k server -local adminitartor login or admin priviledge login and it errors.
please help.
Thanks
I can access from Win2k server to that workgroup win2k server box, but not from any win2k3 server.
I can ping\access from workgroup box to win2k3 server, but not viceversa.
In says, you are not authorized to logon using this account......something like this error.
I am trying to use local win2k server -local adminitartor login or admin priviledge login and it errors.
please help.
Thanks
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
arnold
\\ip adress\C$ is an administrative share. Only a user with administrators rights can access this share from remote computer. You said you attempted the access from a win2k3 local administrator account. Ref Rido78, does the win2k3 local administrator account exist on the win2k box and does it have administrative rights?
ASKER
Thanks for the response.
Remember, the machine i am trying to connect to is win2000 server standalone box, it's not part of any domain, just workgroup. Box has 2 NICs and one going to another win2000 server and second NIC connected to Win2003 Server.
I can connect with \\ip address\c$ from win2000 sever domain machine to win2000 workgroup machine-no problem.
But, i CANNOT connect from win2003 server domain machine to win2000 workgroup machine.
Note: When i say domain machine, i only mean member of another domain, not domain controller. In fact, the domain controller behaves the same way, too.
The local admin account is created on win2000 workgroup box. i am trying to use same local admin account to map the admin share.
Help... Its driving me crazy.
Remember, the machine i am trying to connect to is win2000 server standalone box, it's not part of any domain, just workgroup. Box has 2 NICs and one going to another win2000 server and second NIC connected to Win2003 Server.
I can connect with \\ip address\c$ from win2000 sever domain machine to win2000 workgroup machine-no problem.
But, i CANNOT connect from win2003 server domain machine to win2000 workgroup machine.
Note: When i say domain machine, i only mean member of another domain, not domain controller. In fact, the domain controller behaves the same way, too.
The local admin account is created on win2000 workgroup box. i am trying to use same local admin account to map the admin share.
Help... Its driving me crazy.
I'm getting a bit confused, so I'm suggest to use the following names for the machines:
- W2003-d = Windows 2003 server in domain
- W2000-d = Windows 2000 server in domain
- W2000-w = Windows 2000 server in workgroup-mode.
You want to connect to the W2000-w machine. You succeed when you try to connect from the W2000-d machine but you fail when you connect from the W2003-d machine. The W2000-w machine is connected to the other machines using a crosslink-cable or a hub/switch (no routers whatsoever) Am I correct?
If so, then I wonder if both W2000-d and W2003-d are in the same domain, same forrests or have another trustrelationship. Furthermore I would like to know what the IP-adresses and subnets are from both NIC's in the W2000-w machine and the routingtable (ROUTE PRINT) would be usefull as well.
- W2003-d = Windows 2003 server in domain
- W2000-d = Windows 2000 server in domain
- W2000-w = Windows 2000 server in workgroup-mode.
You want to connect to the W2000-w machine. You succeed when you try to connect from the W2000-d machine but you fail when you connect from the W2003-d machine. The W2000-w machine is connected to the other machines using a crosslink-cable or a hub/switch (no routers whatsoever) Am I correct?
If so, then I wonder if both W2000-d and W2003-d are in the same domain, same forrests or have another trustrelationship. Furthermore I would like to know what the IP-adresses and subnets are from both NIC's in the W2000-w machine and the routingtable (ROUTE PRINT) would be usefull as well.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.