Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden using our free interactive tool and use it to determine the right price for your IT services. Start calculating Now!
Problems accessing shares via IP Address only
Hello Techs,
I have 7 Windows 2008 R2 servers. All are Virtual on VMWare.
I have this wierd issue,
When i access the server share using "\\<servername>" it opens fine without asking for a password.
Howeve, when from the same server i try accessing it using IP "\\<IP Address>", it pops up for the password.
Strange thing is that:
From Server1, i am able to access the "\\<IP Address>" for Server2 and Server3. However, others 7 servers are not working.
All are on the same domain.
Not sure what to do ?
I have 7 Windows 2008 R2 servers. All are Virtual on VMWare.
I have this wierd issue,
When i access the server share using "\\<servername>" it opens fine without asking for a password.
Howeve, when from the same server i try accessing it using IP "\\<IP Address>", it pops up for the password.
Strange thing is that:
From Server1, i am able to access the "\\<IP Address>" for Server2 and Server3. However, others 7 servers are not working.
All are on the same domain.
Not sure what to do ?
Do more with
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Did you add a share to the IP name? If not, it may be trying to access C$ which will require a password.
Here is the detail John.
Server1 - 192.168.1.20
Server2 - 192.168.1.21
Server3 - 192.168.1.22
Server4 - 192.168.1.23
Server5 - 192.168.1.24
Server6 - 192.168.1.25
Server7 - 192.168.1.26
Server8 - 192.168.1.27
When i Go to Server8 and Open Run and Type
"\\Server1"(No Folders after the server name nor "\") to 8, it opens
When i Type the IP of Server1 and Server 2 like "\\192.168.1.20" and 21, it opens.
However, all other IPs are prompting for Username/Password and it says "Logon Error: Unknown Username or Bad Password"
Now
I went to Server4 and Open the RUN and type:
"\\Server1"(No Folders after the server name nor "\") to 8, it opens
When i Type the IP of Server1, 2, 3 and 8 like "\\192.168.1.20" 21, 22, and 27 it opens.
However, all other IPs are prompting for Username/Password and it says "Logon Error: Unknown Username or Bad Password"
Not sure what you are trying to point as "Share to the IP Name"
Server1 - 192.168.1.20
Server2 - 192.168.1.21
Server3 - 192.168.1.22
Server4 - 192.168.1.23
Server5 - 192.168.1.24
Server6 - 192.168.1.25
Server7 - 192.168.1.26
Server8 - 192.168.1.27
When i Go to Server8 and Open Run and Type
"\\Server1"(No Folders after the server name nor "\") to 8, it opens
When i Type the IP of Server1 and Server 2 like "\\192.168.1.20" and 21, it opens.
However, all other IPs are prompting for Username/Password and it says "Logon Error: Unknown Username or Bad Password"
Now
I went to Server4 and Open the RUN and type:
"\\Server1"(No Folders after the server name nor "\") to 8, it opens
When i Type the IP of Server1, 2, 3 and 8 like "\\192.168.1.20" 21, 22, and 27 it opens.
However, all other IPs are prompting for Username/Password and it says "Logon Error: Unknown Username or Bad Password"
Not sure what you are trying to point as "Share to the IP Name"
The security seems to vary a bit by server and with NO folder share (just Server) the server will interpret the request as C$ (or D$ whatever) and insist on a password. So what you see is normal so far as I can see.
@Vicky This sounds like cached credentials issue. You can cache the credentials for network shares that are tied to either hostname or IP address. You can manager your credentials in the Windows Credential Manager.
Mapped drives can also have this effect or having other network connections established to the server already. To check if you have connections established you can run net use with no parameters and it will show you all your connections. You can then use net use again to delete any connections if necessary and then try connecting to the share again.
My guess though is the cached credentials.
Mapped drives can also have this effect or having other network connections established to the server already. To check if you have connections established you can run net use with no parameters and it will show you all your connections. You can then use net use again to delete any connections if necessary and then try connecting to the share again.
My guess though is the cached credentials.
@John,
I agree, but the problem here is that
Even if i try "\\<IP Address>\<FolderName>" still it is the same.
Asking for the credentials and throws an error.
@Jeremy,
I have already tried Net Use command and it shows about only one server. nothing else.
I agree, but the problem here is that
Even if i try "\\<IP Address>\<FolderName>" still it is the same.
Asking for the credentials and throws an error.
@Jeremy,
I have already tried Net Use command and it shows about only one server. nothing else.
Also,
here is what i did and found.
Logged into Server4 and server8
Tried Accessing the "\\<IP Address of Server4>" from SERVER8
Tried Accessing the "\\<IP Address of Server8>" from SERVER4
Found that the moment it fails to authenticate me, it generates an event in security log:
Event ID 4625, Source - Microsoft-Windows-Security
here is what i did and found.
Logged into Server4 and server8
Tried Accessing the "\\<IP Address of Server4>" from SERVER8
Tried Accessing the "\\<IP Address of Server8>" from SERVER4
Found that the moment it fails to authenticate me, it generates an event in security log:
Event ID 4625, Source - Microsoft-Windows-Security
Log Name: Security
Source: Microsoft-Windows-Security-Auditing
Event ID: 4625
Task Category: Logon
Level: Information
Keywords: Audit Failure
User: N/A
Computer: server4
Description:
An account failed to log on.
Subject:
Security ID: NULL SID
Account Name: -
Account Domain: -
Logon ID: 0x0
Logon Type: 3
Account For Which Logon Failed:
Security ID: NULL SID
Account Name: Administrator
Account Domain: MYDOMAIN
Failure Information:
Failure Reason: Domain sid inconsistent.
Status: 0xc000006d
Sub Status: 0xc000019b
Process Information:
Caller Process ID: 0x0
Caller Process Name: -
Network Information:
Workstation Name: SERvER4
Source Network Address: 192.168.1.27
Source Port: 53690
Detailed Authentication Information:
Logon Process: NtLmSsp
Authentication Package: NTLM
Transited Services: -
Package Name (NTLM only): -
Key Length: 0
This event is generated when a logon request fails. It is generated on the computer where access was attempted.
The Subject fields indicate the account on the local system which requested the logon. This is most commonly a service such as the Server service, or a local process such as Winlogon.exe or Services.exe.
The Logon Type field indicates the kind of logon that was requested. The most common types are 2 (interactive) and 3 (network).
The Process Information fields indicate which account and process on the system requested the logon.
The Network Information fields indicate where a remote logon request originated. Workstation name is not always available and may be left blank in some cases.
The authentication information fields provide detailed information about this specific logon request.
- Transited services indicate which intermediate services have participated in this logon request.
- Package name indicates which sub-protocol was used among the NTLM protocols.
- Key length indicates the length of the generated session key. This will be 0 if no session key was requested.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<EventData>
<Data Name="SubjectUserSid">S-1-0-0</Data>
<Data Name="SubjectUserName">-</Data>
<Data Name="SubjectDomainName">-</Data>
<Data Name="SubjectLogonId">0x0</Data>
<Data Name="TargetUserSid">S-1-0-0</Data>
<Data Name="TargetUserName">Administrator< /Data>
<Data Name="TargetDomainName">MYDOMAIN</Da ta>
<Data Name="Status">0xc000006d</Data>
<Data Name="FailureReason">%%2314</Data>
<Data Name="SubStatus">0xc000019b</Data>
<Data Name="LogonType">3</Data>
<Data Name="LogonProcessName">NtLmSsp </Data>
<Data Name="AuthenticationPackageName">NTL M</Data>
<Data Name="WorkstationName">SERVER8</Data >
<Data Name="TransmittedServices">-</Data>
<Data Name="LmPackageName">-</Data>
<Data Name="KeyLength">0</Data>
<Data Name="ProcessId">0x0</Data>
<Data Name="ProcessName">-</Data>
<Data Name="IpAddress">192.68.1.27</Data>
<Data Name="IpPort">53690</Data>
</EventData>
</Event>
I have already tried Net Use command and it shows about only one server. nothing else.Understood. But have you checked the Credential Manager? Clear out any cached for the servers you're try to connect to.
@Jeremy
Yes, nothing is there too.
Also, just saw a strange thing on the server. i downloaded psGetSid on SERVER8, and found following:
Yes, nothing is there too.
Also, just saw a strange thing on the server. i downloaded psGetSid on SERVER8, and found following:
On the SERVER8
C:\Users\loladmin\Desktop\PSTools>Ps Getsid \\*
PsGetSid v1.44 - Translates SIDs to names and vice versa
Copyright (C) 1999-2008 Mark Russinovich
Sysinternals - www.sysinternals.com
Enumerating domain...
\\LOLWORK:
Couldn't access LOLWORK:
The network name cannot be found.
Make sure that the default admin$ share is enabled on LOLWORK.
\\SERVER1:
SID for \\SERVER1:
S-1-5-21-1284242540-3484221295-18958 00360
\\SERVER8:
SID for \\SERVER8:
S-1-5-21-0588641833-1664620078-45184 5185
\\SERVER2:
SID for \\SERVER2:
S-1-5-21-1284242540-3484221295-18958 00360
\\SERVER3:
SID for \\SERVER3:
S-1-5-21-1284242540-3484221295-18958 00360
\\SERVER4:
SID for \\SERVER4:
S-1-5-21-1284242540-3484221295-18958 00360
\\SERVER5:
SID for \\SERVER5:
S-1-5-21-1284242540-3484221295-18958 00360
\\SERVER6:
SID for \\SERVER6:
S-1-5-21-1284242540-3484221295-18958 00360
\\SERVER7:
SID for \\SERVER7:
S-1-5-21-1284242540-3484221295-18958 00360
\\SERVERFS:
SID for \\SERVERFS:
S-1-5-21-8641831857-46200518-4658416 169
C:\Users\loladmin\Desktop\PSTools>
Looks like you have a lot of duplicate SIDs on your network. All of these servers have the same SID:
SID for \\SERVER1:
SID for \\SERVER2:
SID for \\SERVER3:
SID for \\SERVER4:
SID for \\SERVER5:
SID for \\SERVER6:
SID for \\SERVER7:
S-1-5-21-1284242540-348422
This is only a problem if they're domain controllers.
Are any of these domain controllers?
http://blogs.technet.com/b/markrussinovich/archive/2009/11/03/3291024.aspx
SID for \\SERVER1:
SID for \\SERVER2:
SID for \\SERVER3:
SID for \\SERVER4:
SID for \\SERVER5:
SID for \\SERVER6:
SID for \\SERVER7:
S-1-5-21-1284242540-348422
This is only a problem if they're domain controllers.
Are any of these domain controllers?
http://blogs.technet.com/b/markrussinovich/archive/2009/11/03/3291024.aspx
OK, was server 1 or 2 used to create the domain?
If so, then you'll need to run sysprep on all the servers and join them back to the domain.
If not, then you'll just need to sysprep the DCs.
For the domain controllers I would:
1. Demote server1
2. Run sysprep on server1
3. Clean up any references to server in AD
4. Promote server1
5. Perform steps 1 - 4 on Server2
Also, for Microsoft to support your server installs, you'll need to run sysprep on them:
https://support.microsoft.com/en-us/kb/314828
Please read the sysprep documentation before proceeding! https://technet.microsoft.com/en-us/library/cc766049(v=ws.10).aspx
If so, then you'll need to run sysprep on all the servers and join them back to the domain.
If not, then you'll just need to sysprep the DCs.
For the domain controllers I would:
1. Demote server1
2. Run sysprep on server1
3. Clean up any references to server in AD
4. Promote server1
5. Perform steps 1 - 4 on Server2
Also, for Microsoft to support your server installs, you'll need to run sysprep on them:
https://support.microsoft.com/en-us/kb/314828
Please read the sysprep documentation before proceeding! https://technet.microsoft.com/en-us/library/cc766049(v=ws.10).aspx
@Jeremy,
I need to check from with my Old SysAdmin that "was server 1 or 2 used to create the domain?" or not?
For now till i find the info, if i assume that server1 or server2 was used t create a Domain, than according to your recommendation, we need to run Sysprep on all rest of the servers (server3 to Server7).
If i do that, i am just concerned about the roles installed on the server. As, one of them are Print server, one of them are DFS, one of them are WSUS, one of them are APP. Does, running sysprep would remove those roles and do we need to configure again everything?
Also, what if i just run the ChangeSID from Sysprep?, will that work and keep the server roles intact ?
I need to check from with my Old SysAdmin that "was server 1 or 2 used to create the domain?" or not?
For now till i find the info, if i assume that server1 or server2 was used t create a Domain, than according to your recommendation, we need to run Sysprep on all rest of the servers (server3 to Server7).
If i do that, i am just concerned about the roles installed on the server. As, one of them are Print server, one of them are DFS, one of them are WSUS, one of them are APP. Does, running sysprep would remove those roles and do we need to configure again everything?
Also, what if i just run the ChangeSID from Sysprep?, will that work and keep the server roles intact ?
You need to thoroughly read the sysprep documentation. It will not remove any roles or install applications but it will reset any security associations.
You definitely will need to remove each of the computers from the domain and rejoin them after you sysprep. Print services will probably not need to be reconfigured but you may need to reconnect the clients to it. You will most likely need to reconfigure DFS. Your application server just depends.
You won't, however, need to reset any file or application permissions. Those should stay intact. This is not a light undertaking but must be done.
You definitely will need to remove each of the computers from the domain and rejoin them after you sysprep. Print services will probably not need to be reconfigured but you may need to reconnect the clients to it. You will most likely need to reconfigure DFS. Your application server just depends.
You won't, however, need to reset any file or application permissions. Those should stay intact. This is not a light undertaking but must be done.
Premium Content
You need an Expert Office subscription to comment.Start Free Trial