+ Post New Thread
Page 3 of 4 FirstFirst 1234 LastLast
Results 31 to 45 of 47
Windows Thread, Nightmare in a network in Technical; Originally Posted by MGSTech I don't suppose the workstations were cloned (ghosted) without sysprep being run? Duplicate SID's? Try running ...
  1. #31
    IanT's Avatar
    Join Date
    Aug 2008
    Location
    @ the back of my server racks farting.....
    Posts
    1,891
    Thank Post
    2
    Thanked 118 Times in 109 Posts
    Rep Power
    60
    Quote Originally Posted by MGSTech View Post
    I don't suppose the workstations were cloned (ghosted) without sysprep being run?

    Duplicate SID's?

    Try running Sysprep and select reseal then rename the workstation (delete the COMPUTER account in AD BEFORE renaming PC...
    or just run the handy MS Sysinternal tool called NewSID

  2. #32

    sparkeh's Avatar
    Join Date
    May 2007
    Posts
    6,731
    Thank Post
    1,272
    Thanked 1,644 Times in 1,100 Posts
    Blog Entries
    22
    Rep Power
    505
    Quote Originally Posted by IanT View Post
    or just run the handy MS Sysinternal tool called NewSID
    Does nobody read an entire thread now?
    This has already been brought up a few times.

  3. #33
    IanT's Avatar
    Join Date
    Aug 2008
    Location
    @ the back of my server racks farting.....
    Posts
    1,891
    Thank Post
    2
    Thanked 118 Times in 109 Posts
    Rep Power
    60
    Well spotted, give ya self a pat on the back

  4. #34

    powdarrmonkey's Avatar
    Join Date
    Feb 2008
    Location
    Alcester, Warwickshire
    Posts
    4,859
    Thank Post
    412
    Thanked 777 Times in 650 Posts
    Rep Power
    182
    Quote Originally Posted by sparkeh View Post
    Does nobody read an entire thread now?
    This has already been brought up a few times.
    Nope, just lately it seems acceptable to judge a thread on the three latest posts, or if you were involved in the thread earlier on but missed a load of posts, the last one is authoritative.

  5. #35


    Join Date
    May 2009
    Location
    UK
    Posts
    2,105
    Thank Post
    256
    Thanked 450 Times in 251 Posts
    Rep Power
    141
    ok, sorry I got tracked on (as we all do!) onto other problems.... never a quiet day!

    The server reboot did the trick, and replication kicked back in.

    I can now add things to the domain again, so that part is solved. Part of the printers issue is also solved by this.

    I missed something blatant in the networked printer... It's a networked printer on a domain, being accessed by laptops that are not on the domain (They will be soon, new network etc....)

    For those who haven't had their coffee yet, to access anything on a domain server, you need credentials on that domain to access it. I will need to setup a startup batchfile that maps a drive with domain credentials, which will give it the credentials to access the printer!

    Apparently it used to work before, but somehow I doubt it, as I don't see how you can ignore domain authentication.

    The only remaining problem now, is sporadic domain workstations being unable to connect to the domain. I strongly suspect this is something to do with either the DNS being screwy, which I'm ignoring as will getting a brand new managed network with all the trimmings in 3 weeks time, so to put effort into fixing that now would be a waste of my time.

    OR, it's something to do with the SID's. I cannot see the images they used to build the workstations with at the moment, as they were stored on the NAS, which is dead......
    BUT having met one of my predecessors, and read the CV of the other one (silly silly man.... network manager with 5 years experience, and forgot to clean out his personal files from his workstation.....) I strongly suspect they didn't use Sysprep.

    How could the SID's cause this trouble? I'm still stuck with Winsuite, and due to the age of winsuite, it's a fair bet to say it uses SID's to identify the stations. Cannot be 100% sure, but it's a fair guess.

  6. #36
    ahuxham's Avatar
    Join Date
    Apr 2008
    Posts
    1,122
    Thank Post
    76
    Thanked 138 Times in 109 Posts
    Rep Power
    30
    Quote Originally Posted by neilfisher View Post
    How could the SID's cause this trouble? I'm still stuck with Winsuite, and due to the age of winsuite, it's a fair bet to say it uses SID's to identify the stations. Cannot be 100% sure, but it's a fair guess.
    As Sparkeh has pointed out, SID's mean nothing, the won't be identified by Winsuite, and shouldn't cause any problems on the domain.

    Just run NewSID just to be sure, Edugeek admin bar by "mattx" has NewSID bundled, just find his signature on the forums, shouldn't be hard, he's everywhere.

  7. #37

    Join Date
    May 2006
    Location
    West Bromwich
    Posts
    2,190
    Thank Post
    299
    Thanked 215 Times in 185 Posts
    Rep Power
    56
    Are you going to be using the same clients on this new network? If so you may be able to set up and configure RIS on the 2nd DC and create an image of one of the clients (if they are mostly the same type). You can then deploy your new image, just the way you want it but also utilise the image after the infrastructure is rebuilt since the image will still be current.

    This would also alleviate potential viruses (you mentioned AV being out of date) on the clients and bring your clients machines bang up to date with updates, but should also remove the duplicate SIDs. Pre-Stage the machines and the naming will also be sorted.

  8. #38

    Join Date
    Dec 2009
    Posts
    264
    Thank Post
    6
    Thanked 31 Times in 29 Posts
    Rep Power
    15
    Quote Originally Posted by neilfisher View Post
    ok, sorry I got tracked on (as we all do!) onto other problems.... never a quiet day!

    The server reboot did the trick, and replication kicked back in.

    I can now add things to the domain again, so that part is solved. Part of the printers issue is also solved by this.

    I missed something blatant in the networked printer... It's a networked printer on a domain, being accessed by laptops that are not on the domain (They will be soon, new network etc....)

    For those who haven't had their coffee yet, to access anything on a domain server, you need credentials on that domain to access it. I will need to setup a startup batchfile that maps a drive with domain credentials, which will give it the credentials to access the printer!

    Apparently it used to work before, but somehow I doubt it, as I don't see how you can ignore domain authentication.

    The only remaining problem now, is sporadic domain workstations being unable to connect to the domain. I strongly suspect this is something to do with either the DNS being screwy, which I'm ignoring as will getting a brand new managed network with all the trimmings in 3 weeks time, so to put effort into fixing that now would be a waste of my time.

    OR, it's something to do with the SID's. I cannot see the images they used to build the workstations with at the moment, as they were stored on the NAS, which is dead......
    BUT having met one of my predecessors, and read the CV of the other one (silly silly man.... network manager with 5 years experience, and forgot to clean out his personal files from his workstation.....) I strongly suspect they didn't use Sysprep.

    How could the SID's cause this trouble? I'm still stuck with Winsuite, and due to the age of winsuite, it's a fair bet to say it uses SID's to identify the stations. Cannot be 100% sure, but it's a fair guess.

    Now you appear to have your DC's reconnected I'd take the time to try to push one of them out the domain for a rebuild. (make sure to do a system state backup first).

    If the reboot had failed you could have tried a Non Authoritative Restore. This is done by changing the Burflags key in the registry. (plenty of internet articles about it)

    Also might be worth checking that you have sites and services setup correctly. Are your 2 DC's listed under the same site? If not what sort of replication time do they have?

  9. #39

    Join Date
    Dec 2009
    Posts
    603
    Thank Post
    8
    Thanked 36 Times in 34 Posts
    Rep Power
    17
    Actually quite easy to add Domain Printers to Workgroup laptops

    Boot up Laptop

    Printers > add local Port > Insert Printer IP > Point to drivers .. Jobs a gooden

  10. #40

    mattx's Avatar
    Join Date
    Jan 2007
    Posts
    9,240
    Thank Post
    1,058
    Thanked 1,068 Times in 625 Posts
    Rep Power
    740
    Quote Originally Posted by ahuxham View Post
    As Sparkeh has pointed out, SID's mean nothing, the won't be identified by Winsuite, and shouldn't cause any problems on the domain.

    Just run NewSID just to be sure, Edugeek admin bar by "mattx" has NewSID bundled, just find his signature on the forums, shouldn't be hard, he's everywhere.
    What are you saying ? I get about a bit.....?

  11. #41
    ahuxham's Avatar
    Join Date
    Apr 2008
    Posts
    1,122
    Thank Post
    76
    Thanked 138 Times in 109 Posts
    Rep Power
    30
    Quote Originally Posted by mattx View Post
    What are you saying ? I get about a bit.....?
    You're reminding me of David Cameron everyday, everywhere I turn you're/he's there (somewhere)

  12. #42

    mattx's Avatar
    Join Date
    Jan 2007
    Posts
    9,240
    Thank Post
    1,058
    Thanked 1,068 Times in 625 Posts
    Rep Power
    740
    Quote Originally Posted by ahuxham View Post
    You're reminding me of David Cameron everyday, everywhere I turn you're/he's there (somewhere)
    But he's an Eton Boy !! I'm your common type.....

  13. #43


    Join Date
    May 2009
    Location
    UK
    Posts
    2,105
    Thank Post
    256
    Thanked 450 Times in 251 Posts
    Rep Power
    141
    another little update.... I'll need to leave it a couple days, but it looks like it was all down to a borked AD replication. Since rebooting both servers, the domain workstations have started behaving themselves.

    All is well again!

    Just need to get my NAS up and running again.

  14. #44

    Join Date
    Aug 2005
    Location
    London
    Posts
    3,154
    Thank Post
    114
    Thanked 527 Times in 450 Posts
    Blog Entries
    2
    Rep Power
    123
    Quote Originally Posted by 2097 View Post
    Actually quite easy to add Domain Printers to Workgroup laptops

    Boot up Laptop

    Printers > add local Port > Insert Printer IP > Point to drivers .. Jobs a gooden
    Well, for some values of "good" ...

    At minimum, I'd want you to use the DNS name for the printer - that makes it possible to change the IP at some time in the future without having to revisit every laptop.

    It also means you lose any kind of queue control on the printer - if 2 people try to print at the same time then one will lose and there's no nice tidy way of queuing jobs for later.

    You've also got no way of charging users - the job is going straight to the printer and bypassing any quota software etc.

    If none of those things is an issue then it's a good way to work :-)

  15. #45


    Join Date
    May 2009
    Location
    UK
    Posts
    2,105
    Thank Post
    256
    Thanked 450 Times in 251 Posts
    Rep Power
    141
    custom drivers. It's a large networked photocopier with some funky drivers, so would involve going round and installing them all again on every individual laptop. and I'm not sure it's one of those printers you want to install on 40 odd different machines.

SHARE:
+ Post New Thread
Page 3 of 4 FirstFirst 1234 LastLast

Similar Threads

  1. AOL nightmare
    By suesmate in forum How do you do....it?
    Replies: 3
    Last Post: 10th July 2007, 10:44 AM
  2. proxy nightmare
    By alonebfg in forum Wireless Networks
    Replies: 15
    Last Post: 20th November 2006, 05:48 PM
  3. New server nightmare
    By dezt in forum Wireless Networks
    Replies: 10
    Last Post: 16th November 2006, 07:21 PM
  4. Nightmare
    By mrforgetful in forum ICT KS3 SATS Tests
    Replies: 6
    Last Post: 16th May 2006, 02:27 PM
  5. Nightmare Scenario
    By kingswood in forum Wireless Networks
    Replies: 4
    Last Post: 15th September 2005, 07:27 AM

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •