If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
|
#1
|
|||
|
|||
CMD command \\IP_Address is not working, \\computerName will be OK
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 |
#2
|
|||
|
|||
CMD command \\IP_Address is not working, \\computerName will be OK
Hi
Try to flash the computers local DNS cache. C:\ipconfig /flushdns Jack (MS, MVP-Networking). "ricky" wrote in message ... 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 |
#3
|
|||
|
|||
CMD command \\IP_Address is not working, \\computerName will b
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" wrote in message ... 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 . |
#4
|
|||
|
|||
CMD command \\IP_Address is not working, \\computerName will b
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" wrote in message ... 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 . |
#5
|
|||
|
|||
CMD command \\IP_Address is not working, \\computerName will be OK
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" wrote in message ... 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 |
#6
|
|||
|
|||
CMD command \\IP_Address is not working, \\computerName will b
" \\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" wrote in message ... 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 . |
#7
|
|||
|
|||
CMD command \\IP_Address is not working, \\computerName will b
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" wrote in message ... 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 . |
#8
|
|||
|
|||
CMD command \\IP_Address is not working, \\computerName will b
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" wrote in message ... 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 . |
#9
|
|||
|
|||
CMD command \\IP_Address is not working, \\computerName will b
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" wrote in message ... 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 . |
#10
|
|||
|
|||
CMD command \\IP_Address is not working, \\computerName will b
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" wrote in message ... 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 . |
#11
|
|||
|
|||
CMD command \\IP_Address is not working, \\computerName will b
" \\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" wrote in message ... 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 . |
#12
|
|||
|
|||
CMD command \\IP_Address is not working, \\computerName will be OK
Hi Try to flash the computers local DNS cache. C:\ipconfig /flushdns Jack (MS, MVP-Networking). "ricky" wrote in message ... 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 |
#13
|
|||
|
|||
CMD command \\IP_Address is not working, \\computerName will be OK
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" wrote in message ... 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 |
Thread Tools | |
Display Modes | |
|
|