I got 2 XP Pro. client computers with me now.

Both 2 computers have no problem of doing following.
1. Able to Ping computerName or Ping IP_address
2. Able to Connect via CMD command \\computerName

Unfortunately, 1 of these computers can't connect to server CMD command
\\IP_Address.

Any inputs will highly appreciated.

Ricky

Hi
Try to flash the computers local DNS cache.
C:\>ipconfig /flushdns
Jack (MS, MVP-Networking).

"ricky" <(E-Mail Removed)> wrote in message
news:16AE7BAC-BAA4-493D-97D7-(E-Mail Removed)...
>I got 2 XP Pro. client computers with me now.
>
> Both 2 computers have no problem of doing following.
> 1. Able to Ping computerName or Ping IP_address
> 2. Able to Connect via CMD command \\computerName
>
> Unfortunately, 1 of these computers can't connect to server CMD command
> \\IP_Address.
>
> Any inputs will highly appreciated.
>
> Ricky
>

Thanks for your reply.
But Problem still there after "ipconfig /flushdns"
any other Idea?

"Jack [MVP-Networking]" wrote:

> Hi
> Try to flash the computers local DNS cache.
> C:\>ipconfig /flushdns
> Jack (MS, MVP-Networking).
>
> "ricky" <(E-Mail Removed)> wrote in message
> news:16AE7BAC-BAA4-493D-97D7-(E-Mail Removed)...
> >I got 2 XP Pro. client computers with me now.
> >
> > Both 2 computers have no problem of doing following.
> > 1. Able to Ping computerName or Ping IP_address
> > 2. Able to Connect via CMD command \\computerName
> >
> > Unfortunately, 1 of these computers can't connect to server CMD command
> > \\IP_Address.
> >
> > Any inputs will highly appreciated.
> >
> > Ricky
> >
>
> .
>

What response do you see when you try? (If you're doing this from the Run
box open a command prompt instead and enter Start \\IP_Address to see the
output.)
--

"ricky" <(E-Mail Removed)> wrote in message
news:16AE7BAC-BAA4-493D-97D7-(E-Mail Removed)...
> I got 2 XP Pro. client computers with me now.
>
> Both 2 computers have no problem of doing following.
> 1. Able to Ping computerName or Ping IP_address
> 2. Able to Connect via CMD command \\computerName
>
> Unfortunately, 1 of these computers can't connect to server CMD command
> \\IP_Address.
>
> Any inputs will highly appreciated.
>
> Ricky
>

" \\IP_Address is not accessible. You might not have permission to use the
network resource. Contact the administrator of the server to find out if you
have access permissions".

"GTS" wrote:

> What response do you see when you try? (If you're doing this from the Run
> box open a command prompt instead and enter Start \\IP_Address to see the
> output.)
> --
>
> "ricky" <(E-Mail Removed)> wrote in message
> news:16AE7BAC-BAA4-493D-97D7-(E-Mail Removed)...
> > I got 2 XP Pro. client computers with me now.
> >
> > Both 2 computers have no problem of doing following.
> > 1. Able to Ping computerName or Ping IP_address
> > 2. Able to Connect via CMD command \\computerName
> >
> > Unfortunately, 1 of these computers can't connect to server CMD command
> > \\IP_Address.
> >
> > Any inputs will highly appreciated.
> >
> > Ricky
> >
> .
>

It might be a security issue.
Try sharing a folder on the server with full permissions (apply that for the
folder and for the share).

"ricky" wrote:

>
> " \\IP_Address is not accessible. You might not have permission to use the
> network resource. Contact the administrator of the server to find out if you
> have access permissions".
>
> "GTS" wrote:
>
> > What response do you see when you try? (If you're doing this from the Run
> > box open a command prompt instead and enter Start \\IP_Address to see the
> > output.)
> > --
> >
> > "ricky" <(E-Mail Removed)> wrote in message
> > news:16AE7BAC-BAA4-493D-97D7-(E-Mail Removed)...
> > > I got 2 XP Pro. client computers with me now.
> > >
> > > Both 2 computers have no problem of doing following.
> > > 1. Able to Ping computerName or Ping IP_address
> > > 2. Able to Connect via CMD command \\computerName
> > >
> > > Unfortunately, 1 of these computers can't connect to server CMD command
> > > \\IP_Address.
> > >
> > > Any inputs will highly appreciated.
> > >
> > > Ricky
> > >
> > .
> >

If there's security issue...
It should be the same result no matter which of the following method is
used.
\\IP address
\\Computer Name

But, \\Computer Name is working properly and \\IP address doesn't.

"Bostjan Glazar" wrote:

> It might be a security issue.
> Try sharing a folder on the server with full permissions (apply that for the
> folder and for the share).
>
> "ricky" wrote:
>
> >
> > " \\IP_Address is not accessible. You might not have permission to use the
> > network resource. Contact the administrator of the server to find out if you
> > have access permissions".
> >
> > "GTS" wrote:
> >
> > > What response do you see when you try? (If you're doing this from the Run
> > > box open a command prompt instead and enter Start \\IP_Address to see the
> > > output.)
> > > --
> > >
> > > "ricky" <(E-Mail Removed)> wrote in message
> > > news:16AE7BAC-BAA4-493D-97D7-(E-Mail Removed)...
> > > > I got 2 XP Pro. client computers with me now.
> > > >
> > > > Both 2 computers have no problem of doing following.
> > > > 1. Able to Ping computerName or Ping IP_address
> > > > 2. Able to Connect via CMD command \\computerName
> > > >
> > > > Unfortunately, 1 of these computers can't connect to server CMD command
> > > > \\IP_Address.
> > > >
> > > > Any inputs will highly appreciated.
> > > >
> > > > Ricky
> > > >
> > > .
> > >