cannot access XP client in 2K3 domain via unc path

Hi All,

this might sound like a simple one, but i am having problems accessing a machine on the client via it's unc path.
this PC is connected to a local printer that is shared to afew other users.
When going to access the machine via: \\client1 - i get the error "network path not found"
i have checked in DNS - entries are there. nslookup is correct, and resolving fine.
i have turned off the local firewall on the PC and also disabled the windows firewall service.
I have also added "domain users" group into the local admin group of the PC.
i can ping this PC from the DC and all clients.

does anybody have any ideas? that would be much appreciated!!
demolition_unitAsked:
Who is Participating?
 
DarthModCommented:
PAQd, 125 points refunded.

DarthMod
CS Moderator
0
 
Jay_Jay70Commented:
can you access via \\IPaddress
0
 
Keith AlabasterEnterprise ArchitectCommented:
Does it work for the failing pc itself ie put in \\client1 whilst on client1?
0
Free Tool: Site Down Detector

Helpful to verify reports of your own downtime, or to double check a downed website you are trying to access.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

 
demolition_unitAuthor Commented:
i cannot access it from \\ip address, but if i go to the actual client, and run: \\client1, that works.
when going via the windows browser, and browing through "microsoft network" the error message i recieve is: "\\client1 is not accessable, you might not have permission to use this network resource. contact the administrator of this server to find out if you have access permissions.

Permissions wise, i have opened the PC right up, and added "Everyone" into the admin group as well as many computer accounts into it's local admin group, but i still recieve this error.
0
 
johnb6767Commented:
Workstation service started?
Server Service Started?
Netlogon service started (i know this doesnt have anything to do with preventing access, just thinking outside of the box)

File and printer sharing installed on the XP Client?

0
 
johnb6767Commented:
And can you do \\client1\c$ ?
0
 
demolition_unitAuthor Commented:
the workstation, server and netlogon services are started on that PC, and file and print sharing are installed.
i cannot access \\client1\c$
i have also made sure that:
NetBIOS over TCP/IP is enabled.
-ICF is not enabled.
-No TCP/IP Filtering is enabled.
-Computer Browsing Service is enabled and running.


This is the result of a "net view":
C:\>net view
Server Name            Remark

-------------------------------------------------------------------------------
\\LT-01                
\\dcomain-controller
\\client1
\\client2
\\client3
The command completed successfully.
___________________________________________________________________
The wierd thing is that this problem just occured yesterday, and there was no change made to the network.
i was able to connect to this computer afew days ago and share it's local printer, etc.


ALSO here are some other diagnostics i took:
C:\>nbtstat -a -n

Local Area Connection:
Node IpAddress: [10.70.0.51] Scope Id: []

    Host not found.



C:\>nbtstat -n

Local Area Connection:
Node IpAddress: [10.70.0.51] Scope Id: []

                NetBIOS Local Name Table

       Name               Type         Status
    ---------------------------------------------
    client1    <00>  UNIQUE      Registered
    domain   <00>  GROUP       Registered
    client1    <20>  UNIQUE      Registered





C:\>nbtstat -r

    NetBIOS Names Resolution and Registration Statistics
    ----------------------------------------------------

    Resolved By Broadcast     = 1
    Resolved By Name Server   = 2

    Registered By Broadcast   = 3
    Registered By Name Server = 3

    NetBIOS Names Resolved By Broadcast
---------------------------------------------
           client3






C:\>netstat -a -n

Active Connections

  Proto  Local Address          Foreign Address        State
  TCP    0.0.0.0:23             0.0.0.0:0              LISTENING
  TCP    0.0.0.0:25             0.0.0.0:0              LISTENING
  TCP    0.0.0.0:80             0.0.0.0:0              LISTENING
  TCP    0.0.0.0:135            0.0.0.0:0              LISTENING
  TCP    0.0.0.0:443            0.0.0.0:0              LISTENING
  TCP    0.0.0.0:445            0.0.0.0:0              LISTENING
  TCP    0.0.0.0:1044           0.0.0.0:0              LISTENING
  TCP    0.0.0.0:2383           0.0.0.0:0              LISTENING
  TCP    0.0.0.0:2869           0.0.0.0:0              LISTENING
  TCP    0.0.0.0:3389           0.0.0.0:0              LISTENING
  TCP    10.70.0.51:139         0.0.0.0:0              LISTENING
  TCP    10.70.0.51:1121        10.70.0.61:139         TIME_WAIT
  TCP    127.0.0.1:1434         0.0.0.0:0              LISTENING
  UDP    0.0.0.0:445            *:*
  UDP    0.0.0.0:500            *:*
  UDP    0.0.0.0:1025           *:*
  UDP    0.0.0.0:1026           *:*
  UDP    0.0.0.0:3456           *:*
  UDP    0.0.0.0:4500           *:*
  UDP    10.70.0.51:123         *:*
  UDP    10.70.0.51:137         *:*
  UDP    10.70.0.51:138         *:*
  UDP    10.70.0.51:1900        *:*
  UDP    127.0.0.1:123          *:*
  UDP    127.0.0.1:1027         *:*
  UDP    127.0.0.1:1052         *:*
  UDP    127.0.0.1:1087         *:*
  UDP    127.0.0.1:1900         *:*



0
 
demolition_unitAuthor Commented:
I have found the problem for the moment.
when i tried to telnet the Pc on port 135, there was no connection. the PC was running a McAfee firewall.
i had disabled this and thaught that should rule out the problem, but it was still blocking the ports
once i totally un-installed it, the problem went away.

Cheers to everyone for they're suggestions!!
0
 
Keith AlabasterEnterprise ArchitectCommented:
<<<  Does it work for the failing pc itself ie put in \\client1 whilst on client1? >>>

The simplist answer is often the best but go on then, no problem from me :)
Keith

0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.