BhanaD2
asked on
Windows XP "Running Startup Scripts"
1 am running a Windows SBS 2008 with 6 Workstations (Windows XP) on a domain.
Windows SBS Configuration:
Server IP: 192.168.3.2
Subnet: 255.255.255.0
Default Gateway: 192.168.3.1
DHCP: 192.168.3.2
Preferred DNS Server: 192.168.3.2
5 workstations Startup reasonably OK , one Workstation takes 15 minutes "Running Startup Scripts"... How can this be fixed ?
Regarsd
Dal
Windows SBS Configuration:
Server IP: 192.168.3.2
Subnet: 255.255.255.0
Default Gateway: 192.168.3.1
DHCP: 192.168.3.2
Preferred DNS Server: 192.168.3.2
5 workstations Startup reasonably OK , one Workstation takes 15 minutes "Running Startup Scripts"... How can this be fixed ?
Regarsd
Dal
what is in the startup script ??
ASKER
How can I tell ?
ASKER
JapyDooge
There is only one Windows SBS 2008 Server (DNS), HOW CAN i TELL IF dns FORWARDING HAS BEEN SETUP ?
There is only one Windows SBS 2008 Server (DNS), HOW CAN i TELL IF dns FORWARDING HAS BEEN SETUP ?
Perhaps you can try one of the following:
Review the EventLog
Reformat the Machine
Check the Drivers are installed
run msconfig and check the startup items.
Disable Windows Search, or take note of the Disk Activity
Use Task Manager and look for CPU / Memory of Processes that are using
are very busy, Also look at their I/O Activity.
Check the network by pinging the other devices an take notice of the response times.
Hope that Helps.
Review the EventLog
Reformat the Machine
Check the Drivers are installed
run msconfig and check the startup items.
Disable Windows Search, or take note of the Disk Activity
Use Task Manager and look for CPU / Memory of Processes that are using
are very busy, Also look at their I/O Activity.
Check the network by pinging the other devices an take notice of the response times.
Hope that Helps.
By default it's not, but you might have multiple DNS servers (for example, the router/modem from your ISP on 192.168.3.1).
Try an IPCONFIG /ALL on the XP client to see what DNS servers it uses.
The XP client should only use the SBS 2008 server as DNS server (192.168.3.2).
The prefered configuration would be:
Clients on DHCP, given out by the SBS Server wich gives only the IP of the SBS Server as DNS.
DHCP in the modem/router disabled.
A DNS forward on the SBS Server to the modem/router, so that DNS entries that cannot be requested from the server (for example, www.google.com) will be requested at the modem/router.
It's also possible to directly enter the internet service provider's (or other if prefered) DNS servers here, but then you have to create a fixed DNS entry with the name of the modem/router if you want to reach it by hostname from your lan.
Try an IPCONFIG /ALL on the XP client to see what DNS servers it uses.
The XP client should only use the SBS 2008 server as DNS server (192.168.3.2).
The prefered configuration would be:
Clients on DHCP, given out by the SBS Server wich gives only the IP of the SBS Server as DNS.
DHCP in the modem/router disabled.
A DNS forward on the SBS Server to the modem/router, so that DNS entries that cannot be requested from the server (for example, www.google.com) will be requested at the modem/router.
It's also possible to directly enter the internet service provider's (or other if prefered) DNS servers here, but then you have to create a fixed DNS entry with the name of the modem/router if you want to reach it by hostname from your lan.
ASKER
JapyDooge
I checked and the Workstation is using the DNS setting from the Windows SBS 2008 server ( 192.168.3.2), this PC was fine up until today , in fact it has been 30 minutes on " Running Starup Scripts" all other 5 PC'S in the office are fine.
I checked and the Workstation is using the DNS setting from the Windows SBS 2008 server ( 192.168.3.2), this PC was fine up until today , in fact it has been 30 minutes on " Running Starup Scripts" all other 5 PC'S in the office are fine.
But is it only using 192.168.3.2, or multiple DNS servers?
Can you post a complete ipconfig /all ? :)
Can you post a complete ipconfig /all ? :)
ASKER
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.3.15
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.3.1
DHCP Server . . . . . . . . . . . : 192.168.3.2
DNS Servers . . . . . . . . . . . : 192.168.3.2
IP Address. . . . . . . . . . . . : 192.168.3.15
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.3.1
DHCP Server . . . . . . . . . . . : 192.168.3.2
DNS Servers . . . . . . . . . . . : 192.168.3.2
Hmm ok so only one DNS server. I was expecting to see both :)
Then that is not your problem.
What you can try:
- Move the system to another OU
- Give that OU no logon scripts
- Create a script the same as the logonscript, but with 'echo line 1', 'echo line 2', or something like that before each line
- Logon (should be fast, without logon scripts)
- Run the script and see where it takes so long
Then that is not your problem.
What you can try:
- Move the system to another OU
- Give that OU no logon scripts
- Create a script the same as the logonscript, but with 'echo line 1', 'echo line 2', or something like that before each line
- Logon (should be fast, without logon scripts)
- Run the script and see where it takes so long
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Doing this now, removing from Domain and re-adding
ASKER
Graet Stuff
Set the DNS server of the machines to the domain controller only and configure the domain controller's DNS server to forward requests: http://technet.microsoft.com/en-us/library/cc754941.aspx