Questions

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

+
0 Votes
Locked

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

satam
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 ???
  • +
    2 Votes
    robo_dev

    Sometimes hidden adapters on the server do odd things...look for things like the 'WAN miniport' and 'DIrect Parallel' NICs on the server. Disable them, reboot server.

    Do a traceroute to the server IP....maybe somebody created an IP address the same as the server?

    Make sure the server's HOST file is as it should be, and I would clear the DNS cache of the server.

    Is this a cluster server? You cannot connect to shares by IP in a cluster.

    Overall, I would hook up a Wireshark protocol analyser....something odd, like a broadcast storm, could be causing the issue.

    Can a PC connected directly to the server via crossover cable map a share by IP?

    +
    0 Votes
    Rob Kuhn

    What happens if you manually configure this machine with a static IP and DNS? Will it connect to the share by both name and IP? If it does then you might have something in your IP stack on that machine that has gone wonky.

    Also, you're not using WINS by chance? If not check that machine to ensure it doesn't have a WINS entry.

    +
    0 Votes
    satam

    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......

  • +
    2 Votes
    robo_dev

    Sometimes hidden adapters on the server do odd things...look for things like the 'WAN miniport' and 'DIrect Parallel' NICs on the server. Disable them, reboot server.

    Do a traceroute to the server IP....maybe somebody created an IP address the same as the server?

    Make sure the server's HOST file is as it should be, and I would clear the DNS cache of the server.

    Is this a cluster server? You cannot connect to shares by IP in a cluster.

    Overall, I would hook up a Wireshark protocol analyser....something odd, like a broadcast storm, could be causing the issue.

    Can a PC connected directly to the server via crossover cable map a share by IP?

    +
    0 Votes
    Rob Kuhn

    What happens if you manually configure this machine with a static IP and DNS? Will it connect to the share by both name and IP? If it does then you might have something in your IP stack on that machine that has gone wonky.

    Also, you're not using WINS by chance? If not check that machine to ensure it doesn't have a WINS entry.

    +
    0 Votes
    satam

    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......