Cannot Access File Share

there must be a two way trust if they are different domains. i.e. nyc.example.com lv.example.com

Nope. This is same domain.

Try running this command first &  then try accessing the shared folder.

net use \\192.168.1.31\sharedfoldername  /user:domain\user id & hit enter. It will ask for the password of mentioned user.

If above works then try accessing the UNC path.

I have tried the share like this.

\\192.168.1.31\Sharename. its working.

if I run it like \\192.168.1.31 will not working.

I think \\192.168.1.31\IP$ not working

any idea ?

if you want the c: directory \\192.168.1.31\c$
 \\192.168.1.31\IP$ isn't a valid share were you thinking instead of \IPCS$

that also cannot access

on the server in a command prompt type "net share" this will tell you the available shares.

I think its rpc problem there may be MTU problem.

Can we check of its MTU problem ?

Is there any one who knows how to check MTU problem  ?

i am still working in this problem, is there  any idea ?

I highly doubt that it is a MTU problem

ping example.com -f -l xxxx
-l = lower case letter L
xxxx packet size

The normal MTU is 1500

C:\Users\David Johnson>ping google.com -f -l 1475
Pinging google.com [66.185.95.25] with 1475 bytes of data:
Packet needs to be fragmented but DF set.
Packet needs to be fragmented but DF set.
Packet needs to be fragmented but DF set.
Packet needs to be fragmented but DF set.
Ping statistics for 66.185.95.25:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

C:\Users\David Johnson>ping google.com -f -l 1473
Pinging google.com [66.185.95.25] with 1473 bytes of data:
Packet needs to be fragmented but DF set.
Packet needs to be fragmented but DF set.
Packet needs to be fragmented but DF set.
Packet needs to be fragmented but DF set.
Ping statistics for 66.185.95.25:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

C:\Users\David Johnson>ping google.com -f -l 1472
Pinging google.com [66.185.95.25] with 1472 bytes of data:
Reply from 66.185.95.25: bytes=1472 time=17ms TTL=58
Reply from 66.185.95.25: bytes=1472 time=13ms TTL=58
Reply from 66.185.95.25: bytes=1472 time=17ms TTL=58
Reply from 66.185.95.25: bytes=1472 time=13ms TTL=58
Ping statistics for 66.185.95.25:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 13ms, Maximum = 17ms, Average = 15ms

Select allOpen in new window

By trial and error I see that the optimum mtu is 1472
To find out what my configured MTU is .. from an elevated command prompt

C:\WINDOWS\system32>netsh interface ipv4 show subinterfaces

   MTU  MediaSenseState   Bytes In  Bytes Out  Interface
------  ---------------  ---------  ---------  -------------
  1500                1  7678156698  10595591033  Ethernet 2
4294967295                1       4065     114312  Loopback Pseudo-Interface 1
  1500                1          0     198527  VMware Network Adapter VMnet1
  1500                1          0     200471  VMware Network Adapter VMnet8

Select allOpen in new window

To set the mtu

C:\WINDOWS\system32>netsh interface ipv4 set subinterface "Ethernet 2" mtu=1472
store=persistent
Ok.

Select allOpen in new window

You said access via \\192.168.1.31\Sharename works.
Does \\192.168.1.31\c$ also work?

We are working with Microsoft Support for this now. Will you know the solution.

I appreciate the update, ucguy. Thanks!

This question has been classified as abandoned and is closed as part of the Cleanup Program. See the recommendation for more details.