Re: DC/DNS/DFS/AD Problem???




apprentice463 wrote:
Ace Fekay [MVP] wrote:
In news:1166505078.557660.54530@xxxxxxxxxxxxxxxxxxxxxxxxxxx,
apprentice463 <apprentice463@xxxxxxx> stated, which I commented on below:
Here is the ipconfig from the server

Windows IP Configuration

Host Name . . . . . . . . . . . . : selene
Primary Dns Suffix . . . . . . . : auroranet.acsnet.ca
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : auroranet.acsnet.ca
acsnet.ca

Ethernet adapter AuroraNet:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek RTL8139 Family PCI Fast
Ethernet
NIC
Physical Address. . . . . . . . . : 00-0D-88-31-BB-FD
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.6.90
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.6.1
DNS Servers . . . . . . . . . . . : 127.0.0.1
NetBIOS over Tcpip. . . . . . . . : Disabled

Here is the ipconfig for another server in the network.
Windows IP Configuration

Host Name . . . . . . . . . . . . : HELIOS
Primary Dns Suffix . . . . . . . : auroranet.acsnet.ca
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : auroranet.acsnet.ca
acsnet.ca

Ethernet adapter AuroraNet:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Marvell Yukon 88E8001/8003/8010
PCI Gigab
it Ethernet Controller
Physical Address. . . . . . . . . : 00-0E-A6-8B-A9-B8
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.6.92
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.6.1
DNS Servers . . . . . . . . . . . : 192.168.6.90
NetBIOS over Tcpip. . . . . . . . : Disabled

See below for the rest of my reply

Ace Fekay [MVP] wrote:
In news:1166478409.977497.111550@xxxxxxxxxxxxxxxxxxxxxxxxxxx,
apprentice463 <apprentice463@xxxxxxx> stated, which I commented on
below:


To add, when I searched on "System Error, Code = (549)
STATUS_NOT_FOUND.", I found an issue with McAfee.
http://forums.mcafeehelp.com/viewtopic.php?t=56112

What type of antivirus or firewall are you using on the server or
workstations?

Ace
Yes I read the article from McAfee before I posted here.

No software firewalls on the Servers or Workstations except for the
Webserver. All incoming and outgoing traffic goes through a
Checkpoint hardware firewall. For antivirus we use Computer
Associates AV product.

btw- Why is NetBIOS disabled? There are some niceties that work with
it, such as network neighborhood, network browsing, printer browsing
on the network (not thru AD), mapped drives by single name.

My understanding is that only legacy systems pre W2K need netbios and
possibly SAMBA, not sure about SAMBA though. The only other place
that Netbios is required, that I know about, is when creating trusts
between 2 forests. If we ever require it then I will reinstate it
for creating the trust. All necessary drives/devices that each user
requires are mapped using login scripts. BTW, I just disabled
netbios about 2 days ago which was prior to our problem... got tired
of seeing all the unnecessary broadcast traffic. Considering what
you said though I believe that I will reinstate it on the DC and a
test workstation and try another capture with it reinstated to see if
the SMB error goes away. I think DNS is configured okay considering
the DCDiag and Netdiag tests but DFS on the otherhand I am not sure
about. Is there a tool that would test DFS because on a scale of 1
to 10 I know about .01

Is the DFS service enabled or disabled?
Was a DFS root configured?

More info on DFS (generic search page):
http://search.technet.microsoft.com/search/default.aspx?siteId=1&tab=0&query=DFS+2003

DFS, whether be used or not, is also related to AD directory replication.
Since you only have one DC, I wouldn't think this is an issue, however the
service needs to be running whether you've configured a DFS root or not.

Here are some issues that can cause slow performance. There were other hits
that related to SQL.

822219 - You experience slow file server performance and delays occur when
you work with files that are located on a file server:
http://support.microsoft.com/?kbid=822219&SD=tech

JSI Tip 0992. SMB message signing will slow network performance.:
http://www.jsifaq.com/SF/Tips/Tip.aspx?id=0992

JSI Tip 9731. You experience slow network performance using ADSL ...:
http://www.jsifaq.com/SF/Tips/Tip.aspx?id=9731

Slow network performance occurs if you copy files to a domain controller
that is running Windows 2000 or Windows Server 2003:
http://support.microsoft.com/kb/321098

Slow network performance occurs when you select a file on a share that uses
NTFS:
http://support.microsoft.com/kb/265396


Is the DHCP Client Service disabled? This is a *necessary* service on a DC
or any machine for that matter and controls the resolver service, whether
the mahcine is a DHCP client or not. It must be enabled.

NetBIOS, although NOT used by AD, is used by other services, such as the
neighborhood, printer browsing, etc. It is also *REQUIRED* by Exchange. Are
you running Exchange?

SAMBA is an SMB to NFS translator to allow UNIX (Mac OSx, Linux, etc) to
coexist and act like a Windows machine and participate with network
browsing, etc.

I would also change the DNS local loopback address to the actual address, in
your case 192.168.6.90. Loopback addresses can cause 41960 errors. I would
also create a reverse zone for 192.168.6.0/24.

Ace

Thanks Ace, I am not the client site right now. So some of these
answers will be from memory. Most of this was in place before I
arrived and as I mentioned before I am new to some of this so I will be
asking some dumb questions. DFS is enabled but I don't think the root
has been configured. I noticed when I sent you the ipconfig print out
that DHCP was disabled on the DC and meant to ask you if the DHCP would
be needed for DC/AD/DFS server.

Thanks for the clarification on SAMBA.

I hope to get back to the site tonight verify some of the other items

A
Little bit of an update.

The DFS Service was enabled but no root. The DFS Root has now been
defined.
I had seen most of the articles that you spoke of, although I should
mention I tend to steer away from articles that don't refer to windows
XP/2000/2003. I forgot to mention that I had already looked at
kb321098 and when I checked the registry location specified the
TcpDelAckTicks was set to 0 and TcpAckFrequency was set to 1
(kb328890). I tried different values for each of these although I
didn't stray to far from the default settings.

The DHCP client service was enabled on all machines.

I have changed the DNS local loopback address to the actual address as
suggested.

I even enabled netbios on the test workstation and the DC server.

None of the changes have made any difference so far. Unfortunately I
can only work on these problems after hours. I do have all of next
week to work on this problem because this client is shutting down from
Dec 22 to Jan.3. One thing I want to try is a new NIC.

A

.



Relevant Pages

  • Re: DC/DNS/DFS/AD Problem???
    ... Windows IP Configuration ... Here is the ipconfig for another server in the network. ... Is there a tool that would test DFS because on a scale of 1 ...
    (microsoft.public.windows.server.networking)
  • Re: DC/DNS/DFS/AD Problem???
    ... Windows IP Configuration ... Here is the ipconfig for another server in the network. ...
    (microsoft.public.windows.server.networking)
  • Re: Win2K Pro does not resolve external hosts unless given static IP
    ... I have a client with a small network of about 7 Windows 2000 Pro-based ... further configuration on my laptop, ...
    (microsoft.public.win2000.dns)
  • Re: PC Magazine: Its Time to Get a Mac
    ... I'm particularly a fan of step three (where, in order to set up an IP network printer, you tell Windows you're configuring a local printer attached to the computer). ... wizard to use the port setup wizard, and when one is done, there are two things the user has to worry about in Windows if anything goes wrong: the printer configuration and a network port configuration. ...
    (comp.sys.mac.advocacy)
  • Re: server 2003 dfs
    ... Try to review permissions and DFSconfiguration, ... We've run into a slight bump with DFS on server 2003 r2. ... Any client, including the domain controllers, in SiteB can browse to the ... network location cannot be reached" ...
    (microsoft.public.windows.server.active_directory)