Re: Unable to access local workstations from SBS 2003

Hi,

1. Can you ping the client PC name rather than IP from the server?

2. Can you PING the client PC names from the other PCs?

3. Check that the Domain Admins group is a member of the local group Administrators on the client PCs (computers not part of the domain will not have this association)

4. Ensure SBS DNS is pointed to by clients

5. Ensure there is no local HOSTS and LMHOSTS files on the client PCs with duplicate/old names in there

6. Ensure client PCs get their DHCP IPs (inc DNS IP, default gateway etc) from the SBS box (have seen strange issues requiring a release/renew on client PC before odd behaviour disappears)

7. Have you tried temporarily disabling the XP firewall on the client PCs



Tom wrote:
AT the SBS server or via Remote Desktop Control, I'm logged in as the domain administrator. Everytime I attempt to access a client on the network, I get the unable to access message that I provided a couple of posts ago. Does this help?

"aus" wrote:


Hah, this is getting confusing. If you are logged on as the domain administrator can you move files about? Not sure why you would specify the UNC computer path - browse to the server (e.g. Network Places/Entire Network), find a server share (say, Client Apps), right click 'Copy' some folder/files and right click past to the local C: drive - what happens?


Tom wrote:

Aus,
1) All workstations and laptops are WinXP SP2+ (all uptodate w/ all fixes etc.).
2) Yes, all clients were removed from the old domain and rejoined to the new domain which is the same name but I did remove/add each client from the domain AT the client.
3) Recently, I did focus on the DNS of the server as a possible issue. So I made each client point to the DNS (internal IP address) of the server. Same problem as before, that is, there has been no change on this area.
4) Relative to the "..computer name is not in Win2K3" I mean that the laptop computer name, eg DCF9R51 (Dell name), is not part of the "Computers" in Active Directory. But the Local01 computer name IS part of Active Directories computers. Hence, it 'appears' that this is not the issue to solve or spend time in. But, I'm open...
5) I'm sure the clients are part of the domain since our Internet access is through the server and I can get to the Internet from all clients.
6) Yes, I can browse and function as part of the domain. Just can't copy/paste/move FROM the server to a workstation via \\Local01.
Hope this helps!
Tom


"aus" wrote:



Hi, so all the clients were *definitely* rejoined to the new domain - and I think with moving to a new server with the same domain name you have to join a workgroup temporarily then back to the domain.

**The client DNS address must be set to the SBS IP address for proper operation - otherwise strage things happen. This is not optional really.** What are your client PCs? - windows 2000/XP?

To be clear - you want to manipulate files stored on any PC in the domain but from the server (i.e. sitting at the server itself)?

Im not sure I understand: "Now, to answer your specific question on "Is the laptop part of the domain?" Yes, because I can login but the computer name is not in Win2K3."

You are not logging into the domain if the computer has not joined the domain - Im not sure what the computer not being in Win2k3 means? Unless it is Windows 95/98 it will have a computer account - otherwise it is definitely not part of the domain.


NOTE: a computer that is NOT part of a domain can browse and function as if it is part of the domain as long as it has a Username/Password that exists on the server. This hower fails for certin domain functions hence me asking to verify domain membership.



Tom wrote:


Aus,
I'm able to do just about anything from the laptop or any other workstation on the domain: logon, WinExplore, delete but, evidently, not copy/move FROM the server. Hence, from all appearances, we're able to do network connectivity but NOT the transfer of files. I even tried settings the DNS to my server's internal IP address and that didn't work. Now, to answer your specific question on "Is the laptop part of the domain?" Yes, because I can login but the computer name is not in Win2K3. However, the workstation is able to login to the domain AND it's computer name is part of the domain and I have the same issue.... can't copy/past from the server or do a \\Local01

from the server TO The workstation. 

Other ideas?


"aus" wrote:




When you connect to any Windows box it checks to see if you have a user name and password that it knows - either in its local user database or the servers user database (if in a domain). If there is no match then ther is no connection allowed.

Is the laptop definitely part of the domain? (when logging onto the laptop the domain name is definitely displayed - click the Options button if you dont see the domain box). Have you tried logging into the laptop as another domain user then trying to connect?

Note if you kept the same domain and server name you still need to rejoin to the new domain even if the name is the same.



Tom wrote:



We just installed SBS 2003 replacing a Windows 2003 Server as our main server. Now, FROM the SBS2003 server I can't get to the local workstations. That is, if I do a "\\Local01" from the servers Windows Explorer, I get "\\Local01 is not accessible. You might not have permissions to use this network resource... Logon Failure: User has not been granted the requested logon type at this computer."
I'm setup as a Power User on the server. I can browse/explore the server folders from the workstation, but I can't get TO the workstation (or copy/paste) from the server. We have a small network of less than 10 users.
What do I need to do? Seems simple as we were fine before the migration

from Win2K to Win2K3. [We replaced the old server with the same server name


and domain name, reconnected the workstations to the new domain and thought we were fine until THIS....]
Tom 

.