DC/DNS/DFS/AD Problem???



I started looking after a small network for a small company about 5
weeks ago. I noticed the problem I am going to describe about 2 weeks
but it may have existed longer. The network is a 100 Mb Ethernet with
3 servers and 12 workstations. The workstations are all Windows XP SP2
and the servers are all Windows Server 2003 R2. There is a Web server,
a database server and a domain controller/DNS / File server, AD is
enabled and netbios is disabled. About 2 or 3 weeks ago I noticed
that I could no longer copy files to or from the DC/File server. I
have tried using xcopy/copy from a command prompt and using windows
explorer. Also when I use remote desktops to remote onto the DC/DNS/
File server it is quite slow and quite often it loses it connection.
If I sit at the console of the DC/DNS/File server everything appears to
function at normal speed except for the file transfers. When I remote
onto the web server and the database server I have no problems or
rather they do not behave like the server in question and if I transfer
files between any of the other member machines, servers or
workstations, I have no problems. Since the DNS is on the machine in
question, I thought that might be the problem but when I run DCdiag and
Netdiag, neither complains about any problems or maybe I am not running
the right tests? I have downloaded MS's Network Monitor 3.0, nice tool
and lots of info but I am definitely a nubie when it comes to
interpeting the captures.

What I have noticed from the captures is that in the Command
prompt/xcopy and Windows Explorer captures I have a DFS Protocol with
DFS in the Description followed by an SMB error that has an SMB
protocol with a description of SMB:R; Transact2, Open2 - NT Status:
System Error, Code = (549) STATUS_NOT_FOUND. Unfortunately as I said I
am a nubie when it comes to this I don't know what it's trying to tell
me.

Any and all help gratefully accepted.

.



Relevant Pages

  • RE: Printing from Win9x clients stops
    ... Open Server Management. ... then right-click the name of the computer running Windows Small Business ... >From the client computer: ... The Select Network Component Type ...
    (microsoft.public.windows.server.sbs)
  • RE: Printing from Win9x clients stops
    ... The printers with 9x drivers on the server appeared automatically in the ... > then right-click the name of the computer running Windows Small Business ... > From the client computer: ... The Select Network Component Type ...
    (microsoft.public.windows.server.sbs)
  • Re: random lockouts
    ... >> I've got a network with several Windows 2000 Servers and ... >> about 150 Windows 98 clients. ... >This problem occurs because the Windows 2000-based server ... >because the session that is reused is against a DFS ...
    (microsoft.public.win2000.security)
  • Questions Relating to Administering Windows 2000 Server
    ... installed the network client on the target computer. ... Sarah has been attempting to install Windows 2000 ... Server for two days. ... Sarah has checked the cables and hard drives. ...
    (microsoft.public.cert.exam.mcse)
  • Questions Relating to Administering Windows 2000 Server
    ... installed the network client on the target computer. ... Sarah has been attempting to install Windows 2000 ... Server for two days. ... Sarah has checked the cables and hard drives. ...
    (microsoft.public.cert.exam.mcse)