|
Posted by Steven L Umbach on September 30, 2005, 7:40 pm
If you were Registered and logged in, you could reply and use other advanced thread options
Try using \xxx.xxx.xxx.xxx\C$ using the target computers IP address to see
if that works. If it does you have a name resolution process though your
ping results of successful ping by name tend to rule that out. Verify that
the server service is running on the target computer and that you can telnet
into either port 139 or 445 to verify that the ports are open and available
to your computer and not filtered by a firewall, ipsec, etc. You can use
telnet as in telnet xxx.xxx.xxx 139 . If the port is open you will get a
blank command window with a blinking cursor otherwise you would probably get
a connection failed message. See if you can access the target computer from
any other computer to try and narrow down if the problem is related to the
target computer or the computer you are trying to access from.
You could also have a problem with SMB signing or incompatible
authentication method. The security options for digitally sign
communications and lan manager authentication level control that behavior.
Use secpol.msc to open Local Security Policy on a Windows 2003 server. Also
check the logs of the client and server computers via Event Viewer for any
pertinent info that may help solve the problem. The support tool netdiag can
also be very helpful in diagnosing networking problems though more so for
domain computers. The link below explains security setting
incompatibilities. --- Steve
http://support.microsoft.com/default.aspx?scid=kb;en-us;823659
>
> When I run command window and run command like \MachineName\C$
> it says network can not be reached
> This is a stand alone machine not in the network, and I am running it
> interactively
> after logging on locally to machine running Windows 2003 server 64 bit OS
> on
> AMD processor
>
> I can ping the server ping MachineName
>
> Any clues would be appreciated.
>
>
> Thanks
> Kiran
>
>
>
| 
XML site map