Problem regarding imaging and netbios name


Recommended Posts

hello gang,

i have a new problem which seems to have stumped me. I recently updated an already created image (Ghost), created a new image of that system then rolled it out to approx 30 client computers. the procedure i use is this:

1 Install O/S and apps

2 Configure (using a specifically created admin account) profile to copy to default user

3 run sysprep (with the option left on to regenerate sids)

4 and whilst the computer is DOWN (as in before it boots to create new sids and follow my sysprep.inf answer file) i ghost that image.

So theorectically i can rollout fresh images that havent finshed initializing or joined domains yet, to ensure these are REALLY individual images. sysprep then continues and domain attachment is automated via sysprep.inf so i end up with computers ready to rock and roll.

My problem now stems from the fact that on my LAST set of images, the netbios name seems to have been copied across to every image. Now this is peculiar as when i look at each computer in the my computer properties, computer name, more, netbios name, it actually says the computer unique name. As expected ofcourse. But when i ping a recently imaged computer from another computer with the command "ping -a NEWIMAGE1" i recieve a reply from the correct ip adress, but of the netbios name of the host image computer before sysprep was run on it.

Let me say that bit again, the host image (the computer my image was created from) had a computer name of 'Image010306Builda', and such a netbios name of the same up 2 15 characters ofcourse. Sysprep was run on this computer to regerate sids and the like. When this computer shutdown after sysprep i imaged it. My new images all got new computer names (during the sysprep procedure). But now when i interogate these computers they have the same netbios name as the originaal host computer, whilst their own netbios name configuration IS their own (correct) dns computer name.

i cant seem to find the cause of this. I had a WINs server in operation but removed it for clarity sake, it did not have any records regarding my issue anyway.

Any help please, especially from S.O.E admins or anyone really. Thanks alot guys.

Hi amfony,

This may sound strange but we had exactly the same issue at our DR site recently.

You'll find all the machines are pinging via WINS instead of DNS i.e. WKS001 instead of WKS001.domain.co.uk)

Anyway, the fix the engineering team implemented was to script in an "ipconfig /release" and "ipconfig /release" upon the final boot (after our image was rolled and had at least once booted into windows).

Try that on one machine and then try pinging...you should be able to via DNS and resolve name correctly.

What I couldn't understand was a reboot was NOT resolving the issue...it required a forced ipconfig release and renew. Very strange indeed.

Please post an update here whatever the outcome.

Many thanks

i tried but no dice. under every circumstance i get the same reply. i even ran sysprep again on a image client machine, removed ut from domain, uninstalled the nic, rebooted, searched registry, i disabled netbios expliocilty from the nic, (its disabled by dhcp by default) and no dice. i am at a loss

Where are you resolving these names from? Your machine? Every other machine on the network? Where?

Sounds like you have a cached entry or lmhost/host entry in where ever your trying to access these machines from.. What does a nbtstat -A IPADDRESS of the machine in question show?

What does your cache show on the machine your doing these queries from? nbtstat -c

What does the machine in question show for nbtstat -n show?

Sorry for the late reply guys! but i am back now

Sorry budman i should have been more specific, from the newly created image (lets name it CLTIMG) when i ping it self, i get returned its proper "dns" fqdn (and proper address), when i type the command "ping -a IPADDRESS OF SELF" i get the CORRECT DNS name relpy again. Now this is what i expect as i have disabled netbios via DHCP options.

When i ping from ANOTHER (any other) computer to the CLTIMG via its proper name, i get a correct and legitmate dns response (my ddns is working fine and all records are correct for the new images), from anyother computer when i type "ping -a IPADDRESSOFCLTIMG" i get resolved back "ORIGINALIMG" (being the image i copied to rollout to client machines) and the ip address of the CLTIMG box.

Sorry if i am not very clear, but when resolving from it self, the CLTIMG thinks everything is ok. When resolving netbios from another computer it gives me the wrong computername.

I did go through pretty much nbtstat had to aoffer me budman and to confuse me even further when i typed "nbtstat -a CLTIMGIPADDRESS" i get the CORRECT netbios name returned to me.

in the cache if the CLTIMG i get nothing the domain name (which is wierd as i shudnt have any entries here is my netbios is disabled) and nbtstat -n gives me once again my correct computer name.

Interesting no?

I am thinkning along the lines that sysprep itself didnt quite work as supposed to rather then any configuration errors. What is your line of thniking budman? and others ofcourse?

Thanks guys and sorry again about the late reply

I've built plenty of machines and joined them to a domain for tweaking before ghosting, BUT I always remove them from the domain and remove the comp account in AD prior to actually making the image. I havent seen any odd issues form doing so and usually use sysprep to have them prompt for a new name prior to joining the domain on first boot after applying the image...

The problem as it sounds to me is more of a DNS issue than a workstation issue... Maybe try removing the DNS entry for the particular machine that your pinging then renew the IP of that machine and have a new DNS record created. Then of course ping it from somethign else... OR, maybe remove the problem machine from the domain, remove the comp account in AD, rename it and rejoin the domain... Either of these will basically allow DHCP to update DNS with a new record for that machine, and hopefully resolve your problem.

ok that could be the problem, the fact that i DONT remove the computer from the domain b4 sysprep-ing. I was under the assumption that a reseal on sysprep was the equivalent of "making the system ready to be used by end users", and therefore assumed all naming and domain membership was revoke and nullified before sysprep was finshed its job. As well as re-sid-ing.

Now ill have to test this tomorrow, but just a thought. I too, have built plenty of computers, it seems in error with my mistake regarding the domain. But i have now in a prodcution environemnt 95% of my images running well. As in NOT WITH THIS PROBLEM. i dont feel that my procedure this time was any different from the other systems i have built then imaged.

I called micro$oft, with a capital SOFT, and i explained my issue, as soon as i mentioned "3rd party deployment application" they washed theirs hands of the problem and said "we cant guarentee anything with 3rd party products".

As for UnaBonger, the records i have delted and to no avail, the first post actually refers to new ip lease and that was no dice either.

Im back wit the results, I did create a new image with removing the domain, this didnt seem to fix it.

I have recoursed back to creating a brand new installation of XP from my custom install CD. Customised, removed from domain as suggested in this thread and imaged. This works.

Unfortunatley i cannot pin point the problem, but a work around will do until i get more time to investigate. Thanks for all your help guys with this issue.

Sincerley

Amfony

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Here are the top 5 features people still want in Microsoft Teams by Usama Jawad Microsoft Teams is one of the most popular online communication and collaboration tool out there, especially in enterprise environments. Although it receives new features fairly regularly, customers are always clamoring for more, which makes sense given the fact that there are lots of usage scenarios that require coverage when you have millions of users. Back in 2022, we listed the top 10 features that people wanted in Microsoft Teams, and the Redmond tech did roll out some of them globally in the past years. Examples of those include the ability to use multi-tenant accounts and delete private messages. Now, it's time to revisit the same topic in a similar fashion with a list of the top five requests. It is important to note that these feature requests highlighted below are based on the dedicated Feedback portal, are ranked by upvotes, and only include those which have not yet been fulfilled by Microsoft: Enable us to move channels from one team to another (39,451 upvotes): This is similar to what was being requested back in 2022, but Microsoft is still ideating on how to implement this functionality. The item is still in the backlog and the scope and design of the solution are yet to be figured out, and the company is asking for further feedback and ideas in this area. Include Office 365 group calendar (26,998 upvotes): Again a request carrying on from our previous coverage. At that time, Microsoft said that this feature is a priority for it and users will see incremental updates soon. However, the enhancement has now been deprioritized and has been entered in the consideration phase again. The effort to implement this solution would require cross-functional collaboration which doesn't seem to be possible right now, but Microsoft hasn't updated its response in two years. Allow export of Teams chat history (13,685 upvotes): A similar request is present in our previous coverage, but Microsoft says that the ask is still under review, despite vehement support. Enable conversations to move to different channels (13,540 upvotes): In our 2022 coverage, Microsoft suggested workarounds to implement this behavior and its response is almost the same right now. The company is still asking for feedback about why you would want this feature, and people aren't too happy with Microsoft's pace on the issue. Enable access to email from left tab panel (12,265 upvotes): Interestingly, Microsoft has flat out declined this request after internal consideration. That's all for now. It is great to see that many items from our 2022 have been completed and rolled out to customers but the feature requests in this list do indicate that Microsoft sometimes takes years to implement Teams functionality even when the demand is seemingly high. In fact, it can even decline highly-upvoted customer requests without providing detailed justification. What feature do you think is still missing in Microsoft Teams? Let us know in the comments section below and let Redmond know your thoughts in the Feedback portal here!
    • only the copilot pc version went rtm in june. I think rtm was in september, so probably 2 months away.
    • 26200 25H2 is shaping up to be a very solid and stable release, hardly any issues with it here on 3 different configurations of computers
    • Samsung Galaxy S25+ 512GB is $220 off for powerful AI and a pro-grade camera by Paul Hill Are you in the market for a premium Samsung phone? If so, check out the Samsung Galaxy S25+ with 512GB of storage. It’s on Amazon right now for just $899, down 20% from its $1,199.99 list price, representing a significant $220.99 saving. This unlocked device is marked as the number 1 new release by Amazon in the Cell Phones category. If you’re interested, act fast as it’s a limited-time deal. The Galaxy S25+ comes packed with AI features under the umbrella of Galaxy AI. Capabilities include Multiple Tasks with One Ask which brings Google Gemini integration for multi-app commands, Now Brief which proactively gives you information you need to start the day, Audio Eraser to remove distracting sounds from your videos, and advanced portrait features. Powering these features is the Qualcomm SM8750-AB Snapdragon 8 Elite (3 nm) processor which handles all sorts of tasks efficiently including gaming, translation, and photo editing. Alongside the processor is 512GB of storage and 12GB of RAM. The S25+ uses a 6.7-inch QHD+ ProScaler Display which delivers vibrant visuals thanks to its use of Dynamic AMOLED 2X with 3,120 x 1,440 resolution and 120Hz refresh rate. Regarding camera setup, the S25+ has an AI camera with 50MP main sensor, 12MP ultrawide, and 10MP telephoto with OIS. There is also a 12MP front camera. This camera setup is capable of 8K video recording, which is impressive. Finally, you get long battery life with the 4,900 mAh and 45W fast charging support so you don’t need to wait long for it to recharge. If you’re an Android user looking to upgrade to a flagship phone without paying the full price, this deal is for you. If you have an eligible phone to trade in, there is an option to do so to claim up to $725 on the upgrade with Amazon.com Gift Card credit. If you’re excited by AI, but your current phone doesn’t support many AI features, this phone could also be a smart choice. Its display is also great for media consumption, and the processor is robust. Finally, if you have a lot of files to store, the 512GB of storage should be ample. Samsung Galaxy S25+ (Icyblue): $899 (Amazon US) / MSRP $1,199.99 This Amazon deal is US-specific and not available in other regions unless specified. If you don't like it or want to look at more options, check out the Amazon US deals page here. Get Prime (SNAP), Prime Video, Audible Plus or Kindle / Music Unlimited. Free for 30 days. As an Amazon Associate, we earn from qualifying purchases.
    • Sniffnet 1.4.0 by Razvan Serea Sniffnet is a network monitoring tool to help you easily keep track of your Internet traffic. Whether you want to gather statistics, or you need to inspect more in depth what's going on in your network, this app will get you covered. Sniffnet is a technical tool, but at the same time it strongly focuses on the overall user experience: most of the network analyzers out there are cumbersome to use, while one of Sniffnet's cornerstones is to be usable with ease by everyone. Furthermore, Sniffnet is completely free and open-source, dual-licensed under MIT or Apache-2.0: if you are interested you can find the full source code on GitHub. Last but not least, this application is totally developed in Rust: a modern programming language to build efficient and reliable software, emphasizing performance and safety. Sniffnet key features choose a network adapter of your PC to inspect select a set of filters to apply to the observed traffic view overall statistics about your Internet traffic view real-time charts about traffic intensity keep an eye on your network even when the application is minimized export comprehensive capture reports as PCAP files identify 6000+ upper layer services, protocols, trojans, and worms find out domain name and ASN of the hosts you are exchanging traffic with identify connections in your local network discover the geographical location of the remote hosts save your favorite network hosts inspect each of your network connections in real time set custom notifications to inform you when defined network events occur choose the style that fits you the most, including custom themes support ... and more! Sniffnet 1.4.0 changelog: New features Import PCAP files (#795 — fixes #283) Enhanced notifications (#830 — fixes #637) Donut chart reporting overall traffic statistics (#756 — fixes #687) Added support for ARP protocol (#759 — fixes #680) Identify and tag unassigned/reserved "bogon" IP addresses (#678 — fixes #209) Show data agglomerates in Inspect page table (#684 — fixes #601) Added Traditional Chinese (Taiwan) translation 🇹🇼 (#774) Added Indonesian translation 🇮🇩 (#611) A Docker image of Sniffnet is now available (#735) Improvements Added new themes A11y (Night) and A11y (Day) based on palettes optimized for Accessibility (#785 — fixes #786) Do not apply new notification thresholds while user is typing them (#777 — fixes #658) Show more information when domain name is short (#720 — fixes #696) Avoid directory traversal when selecting file name for PCAP exports (#776 — fixes #767) Add icon to window title bar (#719 — fixes #715) Update footer buttons and links (#755 — fixes #553) Handle errors to reduce the number of possible crash occurrences (#784) Updated some of the existing translations to v1.3: Portuguese (#690) Ukrainian (#692) Spanish (#805) Fixes Fix crates.io package for Windows (#718 — fixes #681) Fix crash when inserting characters longer than one byte in the text input for byte threshold notification setting (#747 — fixes #744) Remove pre-uninstall script on Linux (fixes #644) Fix typo in Russian translation (fixes #730) Minor fix to service determination algorithm in case of multicast and broadcast traffic Download: Sniffnet 64-bit | Sniffnet 32-bit ~15.0 MB (Open Source) Link: Sniffnet Home Page | Other operating systems | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
  • Recent Achievements

    • Collaborator
      Mighty Pen went up a rank
      Collaborator
    • Week One Done
      emptyother earned a badge
      Week One Done
    • Week One Done
      DarkWun earned a badge
      Week One Done
    • Very Popular
      valkyr09 earned a badge
      Very Popular
    • Week One Done
      suprememobiles earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      567
    2. 2
      +FloatingFatMan
      189
    3. 3
      ATLien_0
      176
    4. 4
      Skyfrog
      112
    5. 5
      Xenon
      110
  • Tell a friend

    Love Neowin? Tell a friend!