Reputation
6,406
Top tag
Next privilege 10,000 Rep.
Access moderator tools
Badges
2 47 88
Impact
~586k people reached

Mar
27
awarded  Notable Question
Feb
17
awarded  Popular Question
Feb
6
awarded  Famous Question
Jan
23
awarded  Notable Question
Jan
15
awarded  Popular Question
Jan
13
comment With no password expire notification at logon in Windows 7, how are you configuring password expire notification?
I think everyone misses the balloon notification about resetting passwords and even if it is enabled you still need some mechanism in place to let people know their password will expire in order to reduce the number of support calls for people who need their password reset. The password reset prompt after expiry in Windows 7 also doesn't seem to work reliably.
Jan
10
awarded  Notable Question
Jan
8
awarded  Yearling
Jan
5
awarded  Revival
Dec
22
awarded  Notable Question
Dec
11
awarded  Notable Question
Nov
26
awarded  Benefactor
Nov
26
comment Domain computer cannot resolve internal hostnames, but nslookup can
You get the bounty. It may not have solved the problem (I can't know now as I had to take drastic action), but you did put something down as an answer, and provided links to useful material - I didn't know about node type before and now I do, so thanks.
Nov
24
awarded  Notable Question
Nov
22
comment Domain computer cannot resolve internal hostnames, but nslookup can
In the end time ran out for investigation, and I had to take the drastic action of rebuilding the effected laptops. Bith are now functioning fine getting their settings from DHCP, as they were before, and no change to networking configuration or DNS. Still scratching my head, but in the end I spent more time investigating than it took to re-image both laptops and restore the backed up user data. Sometimes the best way to serve your users is to just get the job done, even if it isn't in an intellectually satisfying way.
Nov
21
awarded  Notable Question
Nov
20
comment Domain computer cannot resolve internal hostnames, but nslookup can
Hosts file is unchanged from default with Windows install. There are two computers on the network I am aware of with this problem. One has been made to workaround the issue by adding common internal hosts to the hostfile, buit clearly that isn't sustainable for any length of time. The network settings for all clients are set to "Register this connection's addresses in DNS" - the same settings are in place for all other clients on the network.
Nov
19
comment Domain computer cannot resolve internal hostnames, but nslookup can
I already tried removing the computer from the domain - but since the computer cannot locate the domain in DNS it is unable to do so.
Nov
19
comment Domain computer cannot resolve internal hostnames, but nslookup can
I also tried setting the network interface to use a different DNS server (in a different subnet) but getting the same results. That really looks like it is something on the client causing the problem.
Nov
19
comment Domain computer cannot resolve internal hostnames, but nslookup can
No - listening on all IP addresses. And it does respond to nslookup from the client (and other computers in the same subnet are working ok). Pretty sure that local Windows is not processing DNS lookups to computers in the domain either using a FQDN or bare hostname.