RE: Slow AD logon from remote offices .......

Hi,

I will remve the host and lmosts file to test.
How can i do FQDN lookup as you metntioned? Also, Is anything to do becasue
of no DC server place in rermote offices?


"Popeye32" wrote:

Should be able to remove the hosts and lmhosts files if using same DNS and
wins servers, that may make matters worse and a best practice to not use them
anyway. (lends itself to typo's - but also if the FSMO roles are moved around
-you may have to change them on the machines you put local files on.)

I would verify that both the US side machines and the UK machines get the
same list of server records when a lookup of the FQDN is done. I would also
verify that both see the same 3-4 wins records for the domain (1ch, 1bh,
etc...)

From there I would load something like Ethereal and monitor the traffic in
and out of a sample machine in the UK when the machine is attempting logon.
Should see it try and open the ports. Could there be firewall issues between
the two countries? Sniffer trace would see the denies if there was.

"Mugen" wrote:

Yes, They have the same DNS and WINS settings as other machines in US office
here. Machines in remote offices are Windows 2K, Windows 2K3 and XP.
Also, I manually entered domain name and IP address in Host and lmhosts file.




"Popeye32" wrote:

Have you verified you have the correct DNS suffix and WINS settings on your
sysyems? It sounds like it is having problems finding the domain. If these
are win2k3 and XP machines and still having issues, I would focus on your DNS
settings to ensure they match the same used in the US side.

"Mugen" wrote:

Hi,

We have a single domain here running Window 2K3 AD. The corporate office is
in US here running 2 DCs and also have Window 2K3 Wins server setup for
Netbios resolustion and Windows 2K3 DNS server for SRV record only (We are
not doing DNS Dynamic update). In our remote office in UK and Canada, I just
have some Windows 2000 and Windows 2003 server to join our single AD domain.
The remote offices (UK and Canada) don't have any DC, Wins or DNS server
setup. Here is the problem, when any one of these servers in remote offices
try to logon to the Domain, it takes from 55 seconds to 3 minutes to logon.
It stay in the screen of "Apply your personal settings....."
Can someone help me out what can we do to speed up the logon process.
Because everything is working fine after logon successfully. Do we need to
place a DC in each remote office to fix this problem? Or Wins and DNS Or
could be other problems? And also, if we need to do that. What kind of
setting we need to change in the server like Replication timing, router
setting for broadcast traffic etc?

Thanks.
.

Relevant Pages

  • Re: Fileserver question
    ... >> another box running both 9.0 and Windows. ... >> computers in the same room and connected to a router. ... otherwise you will need to run a DHCP server on one ... > of the machines, preferably the server, or give both machines static ...
    (alt.os.linux.suse)
  • nslookup times out on some WinXP clients
    ... Basically, nslookup times out on some Windows machines, but not on others. ... we currently have a Windows 2000 Server DNS & DHCP Server serving IP ...
    (RedHat)
  • Re: New: LanMan98 V2 Not connecting
    ... all) Windows machines, the computer name as found in the system ... essentially Windows was rejecting the connection because it hadn't ... LanMan98 appears to be one, ... uses a low-level message protocol called SMB (Server Message Block). ...
    (comp.sys.acorn.networking)
  • Re: How do I see users that logged in ?
    ... - I know W98 machines should be migrated, but there are to many hindrances: ... Each subdirectory contains sub-subdirectories like administration, drawings, ... I know you can use the $ to share in windows, ... Can you log on to the server as user X and log on localy as user Y ??? ...
    (microsoft.public.windows.server.general)
  • Re: DST Updates - fun, fun
    ... Most XP machines received the daylight savingtimeupdate ... thesystemtimeis jumping ahead an additional ... all Windows XP, sp2 computers have been patched and verified. ... all Windows 2003 Server machines ...
    (microsoft.public.windowsxp.general)