Solved cannot access shared folders by IP address But I can by name

September 25, 2012 at 07:19:33
Specs: windows 2003
HI Every one,
I have domain controller windows server 2003 and 30 domain members, and everything was working fine.
Yesterday our xp client complain that they cannot access shared folders and files in our domain controller server.
After some time i found that i can access the shared folder by name (\\nameserver) but i cannot access them by IP (\\XX.XX.XX.XX).

i can ping and nslookup the server the DNS working fine,
But I found the error events in the event viewer :

Event Type: Failure Audit
Event Source: Security
Event Category: Logon/Logoff
Event ID: 529
Date: 9/25/2012
Time: 4:10:51 PM
User: NT AUTHORITY\SYSTEM
Computer: SERVER2650
Description:
Logon Failure:
Reason: Unknown user name or bad password
User Name: Administrator
Domain: MENA
Logon Type: 3
Logon Process: NtLmSsp
Authentication Package: NTLM
Workstation Name: Steve-PC1
Caller User Name: -
Caller Domain: -
Caller Logon ID: -
Caller Process ID: -
Transited Services: -
Source Network Address: 10.10.10.15
Source Port: 0
---------------------------------------------------------------------

Event Type: Failure Audit
Event Source: Security
Event Category: Account Logon
Event ID: 680
Date: 9/25/2012
Time: 4:10:51 PM
User: NT AUTHORITY\SYSTEM
Computer: SERVER2650
Description:
Logon attempt by: MICROSOFT_AUTHENTICATION_PACKAGE_V1_0
Logon account: Administrator
Source Workstation: Steve-PC1
Error Code: 0xC000006A


----------------------------------------------------------------------


every time i am trying to access using IP address I receiving this errors.
The user name and password 100 % correct !!!!
So Please Can anyone help me with this problem ???


See More: cannot access shared folders by IP address But I can by name

Report •

✔ Best Answer
September 26, 2012 at 00:20:25
thanks All, For the Help
Yes everything was working fine Ping traceroute, but the accessing shared by the IP was not working.
I delete all the network adapters from device manager, restarted the DC and then reinstall the adapters and everything working now just fine.
thanks again to all of you......


#1
September 25, 2012 at 07:30:52
After some time i found that i can access the shared folder by name (\\nameserver) but i cannot access them by IP (\\XX.XX.XX.XX).

Are you able to ping the server by hostname and IP address or does it only respond to hostname?

Do a ping tests and also traceroutes (both by hostname and IP) and see what happens.

What are your results?

It matters not how straight the gate,
How charged with punishments the scroll,
I am the master of my fate;
I am the captain of my soul.

***William Henley***


Report •

#2
September 25, 2012 at 08:00:10
If things are setup correctly access by name is the correct way. You only access by ip address if not using DNS server. You at least know your DNS server is setup correctly.

Is it only steve-pc1 or all including the server?
If just pc1 have it join a workgroup, delete the AD machine account and rejoin the domain.

This error
Reason: Unknown user name or bad password
means its account/password that is the issue not anything with dns or ip.

Might want to review your firewall settings to see if any blocking by ip was engaged.

Answers are only as good as the information you provide.
How to properly post a question:
Sorry no tech support via PM's


Report •

#3
September 25, 2012 at 10:15:44
thanks curt for replay,
yes I can ping the hostname and the IP and traceroute both also

Report •

Related Solutions

#4
September 25, 2012 at 10:22:54
thanks wanderer,
yes, my dns working fine (I think so), but I need to use the IP for back up solution.
no not only the PC1, for all computers there is a Maped shared folder using the server IP address, and now no one can access this share !!!!!
I don,t think the problem with the account becouse I can accessed through the name (IF the problem with account then i will not be able to access it any way).
the firewall on the server is off .


Report •

#5
September 25, 2012 at 12:59:09
I just checked and I'm able to connect to a share using the IP. However, I can't just type the IP and it'll find it. I have to map to the IP of the server and the share name. Like so:

\\xxx.xxx.xxx.xxx\share

Of course, this doesn't mean it will work on your network as our setup here is rather complex, convoluted and includes healthy doses of Linux and UNIX as well as Windows. But it's worth a try if you know the exact share name you wish to connect to.

It matters not how straight the gate,
How charged with punishments the scroll,
I am the master of my fate;
I am the captain of my soul.

***William Henley***


Report •

#6
September 25, 2012 at 15:48:34
kinda strange to be mapping via ip address when dns is clearly working.

from the workstation logged in as admin can you go
\\server ip address\C$ which is the servers default admin share

is this accessable?

Do you only have this one share or is it all shares on the server?
Any shares between workstations? Do they work?

Server in the same subnet as the workstations and they all have the same subnet mask?

Answers are only as good as the information you provide.
How to properly post a question:
Sorry no tech support via PM's


Report •

#7
September 25, 2012 at 22:37:40
Curt I already did this way, same results and same errors.
wanderer, no I cannot access any share in the target server by using IP, But I can access all shares By the NAME!!!!
Server Of course in the same subnet and all the computers are members in this AD

Report •

#8
September 26, 2012 at 00:20:25
✔ Best Answer
thanks All, For the Help
Yes everything was working fine Ping traceroute, but the accessing shared by the IP was not working.
I delete all the network adapters from device manager, restarted the DC and then reinstall the adapters and everything working now just fine.
thanks again to all of you......

Report •

#9
September 26, 2012 at 07:31:01
That's a very unusual error....and fix. But I'm glad it worked and that you came back here and posted your fix. With luck, that'll help somebody else out in the future.

It matters not how straight the gate,
How charged with punishments the scroll,
I am the master of my fate;
I am the captain of my soul.

***William Henley***


Report •

#10
September 26, 2012 at 08:22:10
Makes me thing nic binding to ipv6 vs ipv4 was the issue.

Answers are only as good as the information you provide.
How to properly post a question:
Sorry no tech support via PM's


Report •

#11
September 27, 2012 at 10:05:50
That makes sense to me wanderer.

I never thought about it but I always uncheck the IPv6 box in the TCP/IP settings. I see no reason, or advantage, to having it enabled in an IPv4 network.

Internally we're not likely to ever go full IPv6. It would be a lot simpler for us to just go IPv6 on the edge at our BGP routers when the time comes.

It matters not how straight the gate,
How charged with punishments the scroll,
I am the master of my fate;
I am the captain of my soul.

***William Henley***


Report •

Ask Question