Loading ...|
Jan
17
|
I recently was doing some final testing after installing a number of BladePC’s and I was pretty sure that I had connected to blade-003 via an RDP connection only to find the file that I was looking for wasn’t in the C:\Temp location at all – and I was certain that the Altiris Console had just reported the File Copy job that I had just started had gone through clean…… So what was going wrong?
It turned out that when I checked the host name of the Blade I was actually on blade-051 and not 003 after all (we were still just finalizing the images and hadn’t added BGInfo at this stage, so it wasn’t immediately obvious)
As I started to dig in to this with the local Admin it became clear that quite a lot of changes had happened to the system in the past few months and there was a still a lot going on, but the upshot of it was that the DHCP and IP address info I had received on my Laptop was inconsistent with what the servers were using.
The Altiris Server was using:
And the DHCP info that my Laptop was using was:
It looked like everything would work correctly if I had used the FQDN or long name to connect to the blade, but when using the short name it resolved this from an older server that was inconsistent with the realities in the Network
*TIP* When you change the Primary and/or Secondary DNS or WINS server always take some time to check they all have the correct info – AND – make sure you update the DHCP scopes as well as all the Servers?
Don’t forget that AD itself relies on this being correct or you could face even bigger issues?
January 19th, 2009 at 1:28 pm
WINS? Are you kidding me? Time to take your Infrastructure Admin/Architect out behind the boathouse and put him out of his misery. Or at least show him how to set the default domain in DHCP.