Solved

XP & Copiers not connecting to Server 2012

Posted on 2014-09-12
18
48 Views
Last Modified: 2015-06-08
we recently restarted the server at a client, windows 2012 server
the next day a windows xp system was not able to connect to server resources or reconnect to the domain, where full ip connectivity and name resolution was working properly.

also the copier which scans to a server share and a wide format printer which does the same was not able to scan to the server, both doing so with smb.

i'm guessing this to be an issue with smb protocol.

 we gave a loaner windows 7 system and that resolved that issue for now and changed the copier to use ftp vs smb. went to alternate win 7 pcs for the wide format to scan to ..

still having an issue, thinking its an smb thing but not certain. only thing that happened was a server reboot the night before then it was friggin Armageddon the next day.

any help you could provide would be appreciated
0
Comment
Question by:jlavery
  • 9
  • 5
  • 3
  • +1
18 Comments
 
LVL 4

Expert Comment

by:Dimarc67
Comment Utility
Any chance there were new MS updates waiting for the system restart to complete their installation?  If so, check the installed updates to ensure nothing might be related to the issues.
0
 
LVL 13

Expert Comment

by:Michael Machie
Comment Utility
Is your crashed Server a DC? If so, make sure to do a full power down and then a cold boot to verify authentication to the DC is working. What is sounds like is that nothing is authenticating properly.

Scans fail - can't authenticate
Can't log on to PCs - can't authenticate
Cannot connect to the Domain - authentication issues

Pinging the Server IP is good I assume? Are mapped drives working?

Please give more info on how you were able to get things working on the loaner PCs. Are they Domain computers or on a separate workgroup? This will help us to identify whether it is connectivity or authentication related. Can you ping the IP of the Server from the problem PCs?
0
 

Author Comment

by:jlavery
Comment Utility
loaner pc was a windows 7 pro.. connected to the domain just fine.
all other pcs on the network, all windows 7 are working properly, connecting to server resources without issue

connectivity across the board is working great. ping server name and domain name without issue.

server didn't crash, it was a planned reboot. they lost electric and a pc connected to a database lost connection locked a record. server and all backend network equipment on ups power and protection...
0
 
LVL 17

Expert Comment

by:WORKS2011
Comment Utility
Did you check DHCP and DNS to make sure there aren't any conflicting records. WIN7 resolves conflicts better than XP.

I would do a ipconfig /flushdns on the server and XP and test.
0
 

Author Comment

by:jlavery
Comment Utility
no updates run recently

flush of dns did not help unfortunelately
0
 
LVL 13

Expert Comment

by:Michael Machie
Comment Utility
Remove all affected pcs from the domain and then re-add them. The profiles for Users will not be affected.
0
 

Author Comment

by:jlavery
Comment Utility
did that with the xp system.. removed from the domain.. added to a workgroup, tried to re add to the domain.. wouldn't go in..
0
 
LVL 13

Expert Comment

by:Michael Machie
Comment Utility
If it wont join the domain, what is the message exactly? You will receiblve a message upon failure. You may want to retry joining the Domain using DomainName.local . Sometimes the local is required.
0
 

Author Comment

by:jlavery
Comment Utility
when it was connected to the domain when accessing network resources we would get the specified network name is no longer available. connectivity was solid, name resolution was solid for the server name and the domain name

trying to connect it to the domain after the fact, I'm sorry but I don't have that message any longer. we would try general name abc, as well as abc.local when trying to join. both produced the login to domain prompt, but both would eventually fail.
0
What Security Threats Are You Missing?

Enhance your security with threat intelligence from the web. Get trending threat insights on hackers, exploits, and suspicious IP addresses delivered to your inbox with our free Cyber Daily.

 

Author Comment

by:jlavery
Comment Utility
some results:

PS C:\Users\administrator.HCC> get-SMBserverconfiguration


AnnounceServer                  : False
AsynchronousCredits             : 64
AutoShareServer                 : True
AutoShareWorkstation            : True
CachedOpenLimit                 : 5
AnnounceComment                 :
EnableDownlevelTimewarp         : False
EnableLeasing                   : True
EnableMultiChannel              : True
EnableStrictNameChecking        : True
AutoDisconnectTimeout           : 0
DurableHandleV2TimeoutInSeconds : 30
EnableAuthenticateUserSharing   : False
EnableForcedLogoff              : True
EnableOplocks                   : True
EnableSecuritySignature         : True
ServerHidden                    : True
IrpStackSize                    : 15
KeepAliveTime                   : 2
MaxChannelPerSession            : 32
MaxMpxCount                     : 50
MaxSessionPerConnection         : 16384
MaxThreadsPerQueue              : 20
MaxWorkItems                    : 1
NullSessionPipes                :
NullSessionShares               :
OplockBreakWait                 : 35
PendingClientTimeoutInSeconds   : 120
RequireSecuritySignature        : True
EnableSMB1Protocol              : True
EnableSMB2Protocol              : True
Smb2CreditsMax                  : 2048
Smb2CreditsMin                  : 128
SmbServerNameHardeningLevel     : 0
TreatHostAsStableStorage        : False
ValidateAliasNotCircular        : True
ValidateShareScope              : True
ValidateShareScopeNotAliased    : True
ValidateTargetName              : True
EncryptData                     : False
RejectUnencryptedAccess         : True
0
 
LVL 17

Expert Comment

by:WORKS2011
Comment Utility
did you rename the computers something different or use the old names. The SID is likely the problem if you used the same name. Remove the computers from the domain again delete the computer names from Active Directory and add back. Or rename the computers before adding back to the domain.
0
 

Author Comment

by:jlavery
Comment Utility
yep tried that as well. changed the pc name.. removed the old from ad.. even added the new one in ad.. still didn't work..

again, issue not localized to xp, copiers that scan to the server are also affected. they use smb protocol..
0
 
LVL 17

Expert Comment

by:WORKS2011
Comment Utility
Not sure I would mix troubleshooting with copiers and workstations? What happens when you manually place the DNS server IP in the workstation NIC and try to connect to the domain?

Once the workstations are back online worry about the copier. may even add the DNS setting on the NIC of the copier as well.
0
 

Author Comment

by:jlavery
Comment Utility
on the workstation we set it to static from dynamic, didn't resolve the issue.

not mixing, but they were experienced at the same time, so can't ignore that fact of it.. and the possibility that it has nothing to do with the workstation itself and maybe something related to how both types of devices communicate with the server.
0
 
LVL 17

Expert Comment

by:WORKS2011
Comment Utility
then you have a DNS problem or DHCP

regarding a copier and workstation yes they are on the same network but they are two completely different pieces of equipment. It's more likely the copier will work after you repair the workstation then the other way around.

turn off the firewall on the PC
0
 
LVL 17

Expert Comment

by:WORKS2011
Comment Utility
what does nslookup tell you on the XP machine
0
 

Accepted Solution

by:
jlavery earned 0 total points
Comment Utility
it was an smb protocol ver support issue
when we made adjustments at the server to allow for earlier version support of smb
0
 

Author Closing Comment

by:jlavery
Comment Utility
other suggested options did not resolve the issue
0

Featured Post

Windows Server 2016: All you need to know

Learn about Hyper-V features that increase functionality and usability of Microsoft Windows Server 2016. Also, throughout this eBook, you’ll find some basic PowerShell examples that will help you leverage the scripts in your environments!

Join & Write a Comment

I don't know if many of you have made the great mistake of using the Cisco Thin Client model with the management software VXC. If you have then you are probably more then familiar with the incredibly clunky interface, the numerous work arounds, and …
What to do when Windows Update is not working correctly? What tools can I use to detect the cause of the malfunction problem? What does this numeric error code mean? These and other questions that you have been asking in the past are answered here (…
In this Micro Tutorial viewers will learn how to use Boot Corrector from Paragon Rescue Kit Free to identify and fix the boot problems of Windows 7/8/2012R2 etc. As an example is used Windows 2012R2 which lost its active partition flag (often happen…
This tutorial will walk an individual through the process of installing of Data Protection Manager on a server running Windows Server 2012 R2, including the prerequisites. Microsoft .Net 3.5 is required. To install this feature, go to Server Manager…

771 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

12 Experts available now in Live!

Get 1:1 Help Now