XP Slow Logon to domain

hi there

i have just done a clean install of windows server sbe 2008

i can join pc's to the domain and i can ping the server by name or ip - but for some reason when i log on to the domain, it takes way to long before i see my desktop annd it just says "applying settings"

normally i know that your primary dns should be the  ip of the server, which it is.
what can it be? i see that routing and remote access is not configured on this server.
can that be?
also, when i installed the os, it asked to be connected to a router, which i did, but it took on the wrong ip in the wrong range.
i manually changed this on the network card to 101.0.0.5, which it was when running the old win2k server. i cant change the ip as we have a pfsense firewall which handles dhcp, internet connection's etc.

any  ideas?
stevenvanheerdenAsked:
Who is Participating?

[Webinar] Streamline your web hosting managementRegister Today

x
 
stevenvanheerdenConnect With a Mentor Author Commented:
The Solution to this problem is that Small Business Server wants to host the DHCP function.
in my case the PFSense Firewall did the DHCP and although it gave out the right settings, Logon remained very slow.
i Changed the Role of DHCP from the PFSense firewall to the SB Server and Logon's was instant.
0
 
crayollaCommented:
Are you using roaming profiles?
Generally this takes a long time when loging on/off after making significant changes to either copy of the user profile (one on the server and one on the local machine).
Check the sizes of these.
One way to indicate this is by timing the log off and log on. If they are taking a similar time you can see that this is indeed the case.
0
 
Corey HaeckerSupport Team LeadCommented:
Have you tried checking the Event Viewer on the xp client? May give you some hints under Security, Applications, or System.
0
Will You Be GDPR Compliant by 5/28/2018?

GDPR? That's a regulation for the European Union. But, if you collect data from customers or employees within the EU, then you need to know about GDPR and make sure your organization is compliant by May 2018. Check out our preparation checklist to make sure you're on track today!

 
stevenvanheerdenAuthor Commented:
hi

no there is no roaming profiles being used here - for now.
i have only  a single test pc connected to the clean install on the server.

i have 3 errors in the event ciewer on the xp pc

1 is this

Event Type:      Warning
Event Source:      DnsApi
Event Category:      None
Event ID:      11165
Date:            2010/03/28
Time:            09:56:34 AM
User:            N/A
Computer:      STEVENLAPTOP
Description:
The system failed to register host (A) resource records (RRs) for network adapter
with settings:

   Adapter Name : {230714B1-2744-47CF-BF18-0A40B7EDAC6F}
   Host Name : stevenlaptop
   Primary Domain Suffix : devonvalley.local
   DNS server list :
           101.0.0.5, 101.0.0.1
   Sent update to server : <?>
   IP Address(es) :
     101.0.0.131

 The reason the system could not register these RRs was because the DNS server contacted refused the update request. The reasons for this might be (a) you are not allowed to update the specified DNS domain name, or (b) because the DNS server authoritative for this name does not support the DNS dynamic update protocol.

 To register the DNS host (A) resource records using the specific DNS domain name and IP addresses for this adapter, contact your DNS server or network systems administrator.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 2a 23 00 00               *#..    


and this one


Event Type:      Error
Event Source:      W32Time
Event Category:      None
Event ID:      29
Date:            2010/03/28
Time:            09:37:10 AM
User:            N/A
Computer:      STEVENLAPTOP
Description:
The time provider NtpClient is configured to acquire time from one or more time sources, however none of the sources are currently accessible.  No attempt to contact a source will be made for 119 minutes. NtpClient has no source of accurate time.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.


and then yhis one...

Event Type:      Error
Event Source:      Userenv
Event Category:      None
Event ID:      1054
Date:            2010/03/28
Time:            09:38:17 AM
User:            NT AUTHORITY\SYSTEM
Computer:      STEVENLAPTOP
Description:
Windows cannot obtain the domain controller name for your computer network. (The specified domain either does not exist or could not be contacted. ). Group Policy processing aborted.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

0
 
Corey HaeckerConnect With a Mentor Support Team LeadCommented:
The problem is definitley with your DNS server. Is set to allow dynamic updates?

Also, see if anything here applies
http://www.eventid.net/display.asp?eventid=11165&eventno=1633&source=DnsApi&phase=1 
0
 
gcastillo31Commented:
HELLO, I HAVE THE SAME PROBLEM, VERIFY YOUR FIRST DNS IS YOUR ACTIVE DIRECTORY SERVER AND PUT IN WINS YOUR ACTIVE DIRECTORY SERVER.

GOOD LUCK
0
 
stevenvanheerdenAuthor Commented:
Thanks guys

i just realized that i had a slip with installation.
i'm busy reinstalling the server os now.

will post back to you guys soon.

thanks so far
0
 
stevenvanheerdenAuthor Commented:
the other thing i wanted to ask...

we have a pfsense firewall running dhcp and a few other services.

after the installation of sbe 2008 is it safe just to remove the dhcp role from the server without compromising other services?
0
 
SnowWolfCommented:
101.0.0.5 is not a private but a public IP address. Please check this with the re-install.
0
 
stevenvanheerdenAuthor Commented:
hi, yes i know this, but the network has been setup and been running like this for years by the previous company.
changing this will be a configuration nightmare as they have firewalls, 2 public wireless network connections wiith fallover configs and a whole lot of other stuff.
keeping it this way will be simpler.
0
 
shauncroucherCommented:
using public ips on a local internal network is a really terrible idea, if there is any opportunity to put this right, would really be worth investing the time!

shaun
0
All Courses

From novice to tech pro — start learning today.