|
|
This isn't causing a problem but i'm curious.
3 PC's in the list of computers list the name as the full domain name so for
example steve.mydomain.local whereas the others just appear as steve.
Any reason why?
|
|
"Steve" <Steve[ at ]discussions.microsoft.com> wrote in message
news:02304A20-661A-41BF-AC6C-CEFBCE7366B6[ at ]microsoft.com...
[Quoted Text] > This isn't causing a problem but i'm curious.
>
> 3 PC's in the list of computers list the name as the full domain name so
> for
> example steve.mydomain.local whereas the others just appear as steve.
>
> Any reason why?
Probably because the default domain suffix is missing from the others. Are
these DHCP clients? Is your DHCP server properly providing the default
domain suffix?
You should be able to correlate the machine name with the "Initializing
simple targeting cookie" entry in the WindowsUpdate.log, where the WUA
records what it thinks is the machine name. If the machine doesn't have a
default DNS suffix (as with workgroup machines, or standalone machines),
only the hostname will be recorded (and reported).
--
Lawrence Garvin, M.S., MCTS, MCP
Independent WSUS Evangelist
MVP-Software Distribution (2005-2007)
https://mvp.support.microsoft.com/profile=30E00990-8F1D-4774-BD62-D095EB07B36E
Everything you need for WSUS is at
http://technet2.microsoft.com/windowsserver/en/technologies/featured/wsus/default.mspx
And, almost everything else is at
http://wsusinfo.onsitechsolutions.com
.....
|
|
Lawrence
Thanks for the reply.
Yes they are DHCP clients. They are the same as the PC's which show the
domain suffix.
How would I check if the DHCP server is properly providing the default
domain suffix?
Thanks
Steve
"Lawrence Garvin (MVP)" wrote:
[Quoted Text] > "Steve" <Steve[ at ]discussions.microsoft.com> wrote in message > news:02304A20-661A-41BF-AC6C-CEFBCE7366B6[ at ]microsoft.com... > > This isn't causing a problem but i'm curious. > > > > 3 PC's in the list of computers list the name as the full domain name so > > for > > example steve.mydomain.local whereas the others just appear as steve. > > > > Any reason why? > > Probably because the default domain suffix is missing from the others. Are > these DHCP clients? Is your DHCP server properly providing the default > domain suffix? > > You should be able to correlate the machine name with the "Initializing > simple targeting cookie" entry in the WindowsUpdate.log, where the WUA > records what it thinks is the machine name. If the machine doesn't have a > default DNS suffix (as with workgroup machines, or standalone machines), > only the hostname will be recorded (and reported). > > > > -- > Lawrence Garvin, M.S., MCTS, MCP > Independent WSUS Evangelist > MVP-Software Distribution (2005-2007) > https://mvp.support.microsoft.com/profile=30E00990-8F1D-4774-BD62-D095EB07B36E> > Everything you need for WSUS is at > http://technet2.microsoft.com/windowsserver/en/technologies/featured/wsus/default.mspx> > And, almost everything else is at > http://wsusinfo.onsitechsolutions.com> ..... > > > > |
|
"Steve" <Steve[ at ]discussions.microsoft.com> wrote in message
news:9EF4132F-6B3C-4BFB-8FE0-2897314B1F3F[ at ]microsoft.com...
[Quoted Text] > Yes they are DHCP clients. They are the same as the PC's which show the
> domain suffix.
>
> How would I check if the DHCP server is properly providing the default
> domain suffix?
It would (should) be configured as Server Option 015 "DNS Domain Name"
or Scope Option 015 "DNS Domain Name" if you're serving multiple scopes in
different domains.
If this option is not configured, then it depends on the local PCs
configuration. Those who are members of the domain would default to using
the assigned domain name as the primary suffix to search. Those who are not
members of the domain would have no information, unless manually configured
in TCP/IP Properties | Advanced | DNS, or provided by the DHCP server.
--
Lawrence Garvin, M.S., MCTS, MCP
Independent WSUS Evangelist
MVP-Software Distribution (2005-2007)
https://mvp.support.microsoft.com/profile=30E00990-8F1D-4774-BD62-D095EB07B36E
Everything you need for WSUS is at
http://technet2.microsoft.com/windowsserver/en/technologies/featured/wsus/default.mspx
And, almost everything else is at
http://wsusinfo.onsitechsolutions.com
.....
|
|
Lawrence
Thats odd then because that option is not configured and yet all PC's are
members of the the domain. The local TCP/IP properties are set to get an IP
address automatically.
One thing may be relevant when I went to check the Option 015 I also checked
other settings and under Address Leases all the PC's that dont show the full
domain name in WSUS console show as Name. there as well. The ones that show
the full name here also show the full name in WSUS console. All that is
except 1 PC which is the only one running Vista which shows the full name in
Address Leases but the short name in WSUS!!!
I can't see what's different about those which dont show the full name and
those that don't but as its not causing any problems its myabe not worth
either of us spending any more time on it.
Thanks once again. You have been a great help to me with my various WSUS
problems which all seems to be running smoothly now. Thanks very much for
your time.
Steve
"Lawrence Garvin (MVP)" wrote:
[Quoted Text] > "Steve" <Steve[ at ]discussions.microsoft.com> wrote in message > news:9EF4132F-6B3C-4BFB-8FE0-2897314B1F3F[ at ]microsoft.com... > > > Yes they are DHCP clients. They are the same as the PC's which show the > > domain suffix. > > > > How would I check if the DHCP server is properly providing the default > > domain suffix? > > It would (should) be configured as Server Option 015 "DNS Domain Name" > or Scope Option 015 "DNS Domain Name" if you're serving multiple scopes in > different domains. > > If this option is not configured, then it depends on the local PCs > configuration. Those who are members of the domain would default to using > the assigned domain name as the primary suffix to search. Those who are not > members of the domain would have no information, unless manually configured > in TCP/IP Properties | Advanced | DNS, or provided by the DHCP server. > > > -- > Lawrence Garvin, M.S., MCTS, MCP > Independent WSUS Evangelist > MVP-Software Distribution (2005-2007) > https://mvp.support.microsoft.com/profile=30E00990-8F1D-4774-BD62-D095EB07B36E> > Everything you need for WSUS is at > http://technet2.microsoft.com/windowsserver/en/technologies/featured/wsus/default.mspx> > And, almost everything else is at > http://wsusinfo.onsitechsolutions.com> ..... > > > |
|
"Steve" <Steve[ at ]discussions.microsoft.com> wrote in message
news:0D9F8F7A-78F1-4038-B8BE-5609D6689C72[ at ]microsoft.com...
[Quoted Text] > Thats odd then because that option is not configured and yet all PC's are
> members of the the domain.
>> It would (should) be configured as Server Option 015 "DNS Domain Name"
>> or Scope Option 015 "DNS Domain Name" if you're serving multiple scopes
>> in
>> different domains.
>>
>> If this option is not configured, then it depends on the local PCs
>> configuration.
>>Those who are members of the domain would default to using
>> the assigned domain name as the primary suffix to search.
I'm doublechecking on this statement. It may be inaccurate.
> One thing may be relevant when I went to check the Option 015 I also
> checked
> other settings and under Address Leases all the PC's that dont show the
> full
> domain name in WSUS console show as Name. there as well. The ones that
> show
> the full name here also show the full name in WSUS console.
This is all consistent with the machine(s) not having properly configured
DNS suffixes.
> All that is
> except 1 PC which is the only one running Vista which shows the full name
> in
> Address Leases but the short name in WSUS!!!
Oh! HEY!... was there some reason you didn't think it significant that this
was a =VISTA= machine, when we first started troubleshooting it??? ;-)
> I can't see what's different about those which dont show the full name and
> those that don't
Other than the =ONE= machine which you're specifically having an issue with
is a VISTA machine???
--
Lawrence Garvin, M.S., MCTS, MCP
Independent WSUS Evangelist
MVP-Software Distribution (2005-2007)
https://mvp.support.microsoft.com/profile=30E00990-8F1D-4774-BD62-D095EB07B36E
Everything you need for WSUS is at
http://technet2.microsoft.com/windowsserver/en/technologies/featured/wsus/default.mspx
And, almost everything else is at
http://wsusinfo.onsitechsolutions.com
.....
|
|
Lawrence
Sorry for not mentioning one PC was running Vista but I think i've confused
the issue so I'll try to clarify.
The network consists of a server running SBS 2003 and 6 clients. 5 run XP
SP2 and 1 runs Vista.
All are DHCP clients and show on the local PC Computer properties as members
of the domain as they also do in the Client Computers section of Server
Management.
In WSUS Console, the server and 2 of the XP SP2 clients show as the full
name i.e. mypc[ at ]mydomain.local. The other XP PC's and the Vista PC just show
as mypc.
In DHCP Address leases, this is consistent with WSUS Console EXCEPT the
vista PC which shows the full name in there unlike in WSUS where it shows the
short name. The XP PC's showing the short name do so in both.
Phew!
Hope thats clearer.
Thanks again
Steve
"Lawrence Garvin (MVP)" wrote:
[Quoted Text] > "Steve" <Steve[ at ]discussions.microsoft.com> wrote in message > news:0D9F8F7A-78F1-4038-B8BE-5609D6689C72[ at ]microsoft.com... > > > Thats odd then because that option is not configured and yet all PC's are > > members of the the domain. > > >> It would (should) be configured as Server Option 015 "DNS Domain Name" > >> or Scope Option 015 "DNS Domain Name" if you're serving multiple scopes > >> in > >> different domains. > >> > >> If this option is not configured, then it depends on the local PCs > >> configuration. > > >>Those who are members of the domain would default to using > >> the assigned domain name as the primary suffix to search. > > I'm doublechecking on this statement. It may be inaccurate. > > > > One thing may be relevant when I went to check the Option 015 I also > > checked > > other settings and under Address Leases all the PC's that dont show the > > full > > domain name in WSUS console show as Name. there as well. The ones that > > show > > the full name here also show the full name in WSUS console. > > This is all consistent with the machine(s) not having properly configured > DNS suffixes. > > > All that is > > except 1 PC which is the only one running Vista which shows the full name > > in > > Address Leases but the short name in WSUS!!! > > Oh! HEY!... was there some reason you didn't think it significant that this > was a =VISTA= machine, when we first started troubleshooting it??? ;-) > > > I can't see what's different about those which dont show the full name and > > those that don't > > Other than the =ONE= machine which you're specifically having an issue with > is a VISTA machine??? > > > > -- > Lawrence Garvin, M.S., MCTS, MCP > Independent WSUS Evangelist > MVP-Software Distribution (2005-2007) > https://mvp.support.microsoft.com/profile=30E00990-8F1D-4774-BD62-D095EB07B36E> > Everything you need for WSUS is at > http://technet2.microsoft.com/windowsserver/en/technologies/featured/wsus/default.mspx> > And, almost everything else is at > http://wsusinfo.onsitechsolutions.com> ..... > > > |
|
"Steve" <Steve[ at ]discussions.microsoft.com> wrote in message
news:F743A535-51AE-4F89-B63F-2FF0968E6BE6[ at ]microsoft.com...
[Quoted Text] > Sorry for not mentioning one PC was running Vista but I think i've
> confused
> the issue so I'll try to clarify.
>
> The network consists of a server running SBS 2003 and 6 clients. 5 run XP
> SP2 and 1 runs Vista.
Cool. Next question, have you applied KB926505 to your SBS2003 server?
> All are DHCP clients and show on the local PC Computer properties as
> members
> of the domain as they also do in the Client Computers section of Server
> Management.
Check.
> In WSUS Console, the server and 2 of the XP SP2 clients show as the full
> name i.e. mypc[ at ]mydomain.local. The other XP PC's and the Vista PC just
> show
> as mypc.
Okay.... what do you get for the line "Connection-specific DNS Suffix" when
you run ipconfig on each of the XP PCs?
An example from my system is shown here:
=====================================
C:\Documents and Settings\lgarvin>ipconfig
Windows IP Configuration
Ethernet adapter Ethernet:
Connection-specific DNS Suffix . : onsitech.lmg
IP Address. . . . . . . . . . . . : 192.168.90.200
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.90.250
=====================================
> In DHCP Address leases, this is consistent with WSUS Console EXCEPT the
> vista PC which shows the full name in there unlike in WSUS where it shows
> the
> short name. The XP PC's showing the short name do so in both.
And, to confirm, your DHCP server is not configured to provide data for
Option 015 in either Server Options or Scope Options?
--
Lawrence Garvin, M.S., MCTS, MCP
Independent WSUS Evangelist
MVP-Software Distribution (2005-2007)
https://mvp.support.microsoft.com/profile=30E00990-8F1D-4774-BD62-D095EB07B36E
Everything you need for WSUS is at
http://technet2.microsoft.com/windowsserver/en/technologies/featured/wsus/default.mspx
And, almost everything else is at
http://wsusinfo.onsitechsolutions.com
.....
|
|
Lawrence
[Quoted Text] > Cool. Next question, have you applied KB926505 to your SBS2003 server?
Yes
> Okay.... what do you get for the line "Connection-specific DNS Suffix" when
> you run ipconfig on each of the XP PCs?
On XP I get:
Windows IP Configuration
Ethernet adapter Local Area Connection 2:
Connection-specific DNS Suffix . : MyDomain.local
IP Address. . . . . . . . . . . . : 192.168.0.47
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.128
and just for completness on the Vista PC (which also doesnt show the domain
name) I get
Windows IP Configuration
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . : MyDomain.local
Link-local IPv6 Address . . . . . : fe80::fc62:7b54:1e5:8025%7
IPv4 Address. . . . . . . . . . . : 192.168.0.11
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.128
Tunnel adapter Local Area Connection*:
Connection-specific DNS Suffix . : MyDomain.local
Link-local IPv6 Address . . . . . : fe80::5efe:192.168.0.11%10
Default Gateway . . . . . . . . . :
Tunnel adapter Local Area Connection* 10:
Connection-specific DNS Suffix . :
IPv6 Address. . . . . . . . . . . : 2001:0:4136:e37a:2481:143e:3f57:fff4
Link-local IPv6 Address . . . . . : fe80::2481:143e:3f57:fff4%9
Default Gateway . . . . . . . . . : ::
> And, to confirm, your DHCP server is not configured to provide data for
> Option 015 in either Server Options or Scope Options?
It wasn't when I first posted. When you previously suggested this I did
change it but have not had chance to reboot the server since. So it wasn't in
there, is now, but has not had a server reboot since I put it in.
Thanks again
Steve
"Lawrence Garvin (MVP)" wrote:
> "Steve" <Steve[ at ]discussions.microsoft.com> wrote in message
> news:F743A535-51AE-4F89-B63F-2FF0968E6BE6[ at ]microsoft.com...
>
> > Sorry for not mentioning one PC was running Vista but I think i've
> > confused
> > the issue so I'll try to clarify.
> >
> > The network consists of a server running SBS 2003 and 6 clients. 5 run XP
> > SP2 and 1 runs Vista.
>
> Cool. Next question, have you applied KB926505 to your SBS2003 server?
>
> > All are DHCP clients and show on the local PC Computer properties as
> > members
> > of the domain as they also do in the Client Computers section of Server
> > Management.
>
> Check.
>
> > In WSUS Console, the server and 2 of the XP SP2 clients show as the full
> > name i.e. mypc[ at ]mydomain.local. The other XP PC's and the Vista PC just
> > show
> > as mypc.
>
> Okay.... what do you get for the line "Connection-specific DNS Suffix" when
> you run ipconfig on each of the XP PCs?
>
> An example from my system is shown here:
>
> =====================================
> C:\Documents and Settings\lgarvin>ipconfig
>
> Windows IP Configuration
>
> Ethernet adapter Ethernet:
>
> Connection-specific DNS Suffix . : onsitech.lmg
> IP Address. . . . . . . . . . . . : 192.168.90.200
> Subnet Mask . . . . . . . . . . . : 255.255.255.0
> Default Gateway . . . . . . . . . : 192.168.90.250
> =====================================
>
> > In DHCP Address leases, this is consistent with WSUS Console EXCEPT the
> > vista PC which shows the full name in there unlike in WSUS where it shows
> > the
> > short name. The XP PC's showing the short name do so in both.
>
> And, to confirm, your DHCP server is not configured to provide data for
> Option 015 in either Server Options or Scope Options?
>
>
> --
> Lawrence Garvin, M.S., MCTS, MCP
> Independent WSUS Evangelist
> MVP-Software Distribution (2005-2007)
> https://mvp.support.microsoft.com/profile=30E00990-8F1D-4774-BD62-D095EB07B36E
>
> Everything you need for WSUS is at
> http://technet2.microsoft.com/windowsserver/en/technologies/featured/wsus/default.mspx
>
> And, almost everything else is at
> http://wsusinfo.onsitechsolutions.com
> .....
>
>
>
|
|
"Steve" <Steve[ at ]discussions.microsoft.com> wrote in message
news:9709A14C-72BB-4D55-B3B8-D06446953EB3[ at ]microsoft.com...
[Quoted Text] >> And, to confirm, your DHCP server is not configured to provide data for
>> Option 015 in either Server Options or Scope Options?
>
> It wasn't when I first posted. When you previously suggested this I did
> change it but have not had chance to reboot the server since. So it wasn't
> in
> there, is now, but has not had a server reboot since I put it in.
Rebooting the server would not be required. The DHCP client will
automatically refresh all DHCP provided information, including the now
available default DNS suffix, when the lease is up for renewal, which is at
one-half the expiration period.
I suspect, given the populated Connection-specific DNS Suffix values, that
the DHCP leases have already been renewed and those values have been
updated.
The question now is: Does anything change at the WSUS server. It may require
you to force the flushing of the targeting cookie, so that the WUA records
the new FQDN hostname of the client system in the cookie, which will then
get it transported to the WSUS server during the next reporting event.
--
Lawrence Garvin, M.S., MCTS, MCP
Independent WSUS Evangelist
MVP-Software Distribution (2005-2007)
https://mvp.support.microsoft.com/profile=30E00990-8F1D-4774-BD62-D095EB07B36E
Everything you need for WSUS is at
http://technet2.microsoft.com/windowsserver/en/technologies/featured/wsus/default.mspx
And, almost everything else is at
http://wsusinfo.onsitechsolutions.com
.....
|
|
Lawrence
No change. Those 4 PC's remain stubbonly without domain suffix.
Steve
"Lawrence Garvin (MVP)" wrote:
[Quoted Text] > "Steve" <Steve[ at ]discussions.microsoft.com> wrote in message > news:9709A14C-72BB-4D55-B3B8-D06446953EB3[ at ]microsoft.com... > > >> And, to confirm, your DHCP server is not configured to provide data for > >> Option 015 in either Server Options or Scope Options? > > > > It wasn't when I first posted. When you previously suggested this I did > > change it but have not had chance to reboot the server since. So it wasn't > > in > > there, is now, but has not had a server reboot since I put it in. > > Rebooting the server would not be required. The DHCP client will > automatically refresh all DHCP provided information, including the now > available default DNS suffix, when the lease is up for renewal, which is at > one-half the expiration period. > > I suspect, given the populated Connection-specific DNS Suffix values, that > the DHCP leases have already been renewed and those values have been > updated. > > The question now is: Does anything change at the WSUS server. It may require > you to force the flushing of the targeting cookie, so that the WUA records > the new FQDN hostname of the client system in the cookie, which will then > get it transported to the WSUS server during the next reporting event. > > -- > Lawrence Garvin, M.S., MCTS, MCP > Independent WSUS Evangelist > MVP-Software Distribution (2005-2007) > https://mvp.support.microsoft.com/profile=30E00990-8F1D-4774-BD62-D095EB07B36E> > Everything you need for WSUS is at > http://technet2.microsoft.com/windowsserver/en/technologies/featured/wsus/default.mspx> > And, almost everything else is at > http://wsusinfo.onsitechsolutions.com> ..... > > > |
|
|
|
Lawrence
No problem at all. Thanks for all your help with this and other problems
recently.
Its not casuing any problems and was always a curiosity thing.
Good luck with the exams!!!
Regards
Steve
"Lawrence Garvin (MVP)" wrote:
[Quoted Text]
|
|
|