Jump to content
Posted 11 November 2014 - 08:30 PM
Posted 11 November 2014 - 08:59 PM
Do the actual computer names change, or just their identity on the network?
Posted 11 November 2014 - 09:35 PM
Posted 11 November 2014 - 09:40 PM
Assuming this is a domain network how many servers do you have and what roles are assigned to each?
Posted 11 November 2014 - 09:55 PM
Posted 11 November 2014 - 09:59 PM
Posted 11 November 2014 - 10:09 PM
sounds dns related, i dind it odd that the computer names would eb changing because that requires a restart and the SID of the machine would eb changed in AD so this makes me think its DNS.
Posted 12 November 2014 - 03:35 AM
That's what I was thinking Johnny, If scavenging hasn't been performed there is likely old dns entries in the server. It could also be if he changed the "network name" and did not join the computers to the "new" domain that could cause issues as well.
Posted 12 November 2014 - 09:10 AM
Got some new information - Server is possible Windows Small Business Server 2008. Seems that last month after a Microsoft update, a few days past and the client computers started responding slowly. The tech came in and created a new network for the computers to connect on the server - which corrected the issue... somewhat. One computer does not log into the network automatically - also it will create its own network. When it does log in, once it goes into safe mode and comes out it has forgotten the network. On top of this issue, every computer that signs in asks if the New Network should be saved as Work, Home, or Public Network. Everytime. So the settings are not being saved by the sounds of it. SO Could this be the need to scavenge the DNS records to correct the issue with one computer? Or should the one computer be removed and re-added to the server? And what about the constant issues of first login asking for network type to be saved? Exactly what happened here? It seems like improper creation of network and re-adding the computers said network. Since I am unfamiliar with their network, I suggested they take my educated guess to their IT person to see if it will help, but to contact me if there is a need for further brainstorming.
Edited by Toten0Maske, 12 November 2014 - 09:32 AM.
Posted 12 November 2014 - 11:37 AM
Exactly what did this tech do to create this new "network"? Rename the domain?
Computer names don't change by themselves which begs the question of how are you determining these machine names are changing? Using ping or nslookup?
Posted 12 November 2014 - 11:45 AM
Posted 12 November 2014 - 12:11 PM
I'm with Sneakycyber on this... JohnnyJammer is close as well..
It really does sound dns related. Probably if the is a reverse dns zone set up in your dns, then it may well have some very old records in it (multiple names against each IP address). Setting up scavenging on the server and all zones will eventually sort it out.
If clients get reattached to the domain, by removing them from the domain totally and then rejoining them, the SID (of the computer object in AD) will change and the new identity of the computer will be unable to delete old records registered by it previous identity.
Minor correction to something johnnyJammer said.. Renaming a computer will not change its SID in AD, as long is it is not dis-joined from the domain in the process...
As it's SBS 2008, I doubt that other name resolution methods (wins) would be interfering.
Posted 12 November 2014 - 07:23 PM
If the tech created a new domain all work stations have to be rejoined to the domain. Appears this did not happen. That is not creating a new "network". It really sounds like the tech left things worse than before.
" One computer is he main culprit by the sounds of it, once it goes to sleep and wakes up it cannot access the network and refuses to access the new network/domain."
This is silly. It is a simple and well known fix of disable power management on the network interface to have this behavior stop.
" But in reality it seems that they lose connection to the network and create a new network on their own."
This would only happen if they couldn't reach the dhcp server [SBS] and ended up with a apipa ip address [169.254.x.x]. They wouldn't have internet or server access.
All of this is conjecture though since we really don't have any facts to work with. Perhaps a ipconfig /all from the server and a workstation could be provided which will tell us more about the configuration.
Posted 12 November 2014 - 10:19 PM
yes X64, didnt have much info to go off when i commented lol so thought they where being rejoined!.
Anyway i think he is talking about setting up a new DHCP scope.
thats why they forget the network portion, so basically the IT fella should have created the proper DNS settings in the DHCP scope and allowed authenticated devices to set the dns records otherwise you will be a busy fellow doing it manually.
make sure he set the basic ones up like 003 (Router), 006 (DNS Server), 015 (DNS Domain name (fully qualified domain name)), 044 (WINS optional), _
Edited by JohnnyJammer, 12 November 2014 - 10:19 PM.
Posted 13 November 2014 - 12:35 PM
A simple test: do a nslookup SBSname from a workstation
0 members, 0 guests, 0 anonymous users