1

I have a workstation that works fine when not connected to the domain but once connected it has an EXTREMELY slow load time.

I have removed it from the domain (and from AD/DNS) then rejoined, it works fine until the 1st reboot.

I’ve checked the firewall settings, NIC drivers, the AV settings (even removed the AV and that had no impact). It’s registering with the ?DNS just fine? and creating the account within AD.

When I ping the AD/DNS server it reaches and there’s no latency issues - until the reboot, that’s when only 50% of the packets make it.

Any suggestions?

I really do not want to blow the system and start fresh.

details: DC/DNS/DHCP/AD is SBS 2003, the workstation is Win 7 x64

3 Spice ups
2

Where does it get stuck on? It could very likely be a roaming profile attempting to set itself up for the account you are trying to log into.

3

It hangs prior to login but it hangs even more for each domain profile and only on this system.

4

Might be it is looking for a logon script this isn’t there any more or one that does a lot.

5

Anything show up in your event logs?

6

Have you checked the wiring between that machine and the switchs.

It does sound like it could be a routing issue. You can easily check this by using a working network cable.

of course there is always the Win 7 autotuning issues which can illustrate themselves as a delayed login time:

7

I’ve seen a GPO such as deployed printers do this.

8

@frank - nothing has changed to the login script (forgot to mention I did check this)

@mhache - just that it takes a long time to log in

@Zebadee - I have rebooted the switch that controls this system and that did not help - I have not tested the cable but I did check the ends when rebooting and it seems fine - the system connects to the network and internet fine when not actually joined to the domain, though it takes a while to actually join compared to other systems I’ve joined here

@bob - its in the same OUs as other win 7 machines and we do not deploy printers through GPO (done through login)

9

  1. When you ping your AD/DNS server, are you pinging by name or ip address?

  2. Does changing to 8.8.8.8 help the internet connection at all?

  3. Is the DNS service running. Win+R, service.msc, enter, search dns, make sure its started.

10

Anything in event viewer?

According to description (with ruled-out possible causes as explained in previous posts), it looks like at least one GPO is causing issues or user profile is corrupted.

Is it happening for all domain users on that workstation or just one?

Try to filter out all GPOs that are applied to that machine and user(s), see if there are any changes.

Enable GPOs one by one (gpupdate /force and reboot afterwards) until you find the one that is causing problems.

As a last possibility, run disk scan, once I had similar issue and domain user profile was on problematic part of HDD. Spent three days in testing/troubleshooting :slight_smile:

11

@ Justin I’ve pinged by both, I’ve not tried added 8.8.8.8 and I’d assume DNS to be running given all other systems are running fine by name and IP

@Milan it’s happening to just that workstation with all profiles - though I find it hard to believe that it’s a GPO because it’s in the same OU as all other win 7 systems - I will try to purge the settings on the system

I did not try a scan disk but I am not ruling anything out so I will try that as well

12

If you do not find the cause of the issue, do the full backup of workstation, rebuild OS and join it to the domain.

If you have any user data saved locally, they can be recovered from the Windows backup.

1 Spice up
13

not a settings issue - just a failing NIC. All problems went away when I popped a new one in and started using that one.

14

Glad to hear that issue is resolved. As one former colleague said: “stick to the basics” :slight_smile:

1 Spice up
15

yes, I meant to post back sooner but it slipped my mind.

I figured given it was having some latency issues (though ironically not as many) while on the local system account that it didn’t necessarily have to relate to the domain

16

Disabling TCP offloading options on Broadcom and Realtek NIC’s resolve packett loss/disconnect issues too.