NT to W2k file sharing across a WAN

[dyost]

Two networks
A - 192.168.1.0/255.255.255.0
B - 192.168.2.0/255.255.255.0

Network A (NT 4.0 server)connects to the internet via 768K DSL , network B (W2K server)connects to
the internet via T-1(W2K). Linux CIPE tunnel routes traffic between
networks.

PC X is 192.168.1.1 on network B and PC Y is 192.168.2.1 on network B.

I can ping to/from each machine with times averaging 50ms.

Both PCs have file sharing enabled and a share named FOLDER1 with
security set to EVERYONE, FULL CONTROL

From X, I can connect to Y and view the shared folder and transfer
files.

When I attempt to connect to Y from X, after entering a username and
password, the system hangs for approx. two minutes and returns "The
remote procedure call failed" error.

Any help would be greatly appreciated.

 

[jtb]

Both X and Y are on Network "B"? Then give X a more correct IP address!!

If you meant X is x.x.1.1 on Network A and Y is x.x.2.1 on Network B, I'd suggest you revisit your Network Naming and Access Management standards since .1 should be your gateway (i.e., router) address...

You state that you can get to Y from X, and then you state you cannot. I assume that you meant you cannot get to X from Y... It's a common issue...

If you're going to make a habit of connecting these servers, I'd recommend using registered IP addresses since NATing around the Internet can cause other problems...

I'd also recommend making certain you had all of the latest service packs installed on all four boxes (NT-X, W2K-Y, Linux-A, Linux-B)... no sense in opening up any other cans of worms...

You will need to validate:

--Share permissions on both systems
--NTFS permissions on both systems
--DNS/WINS/LMHOSTS setup on both systems is correct
--System Policies (on the NT server) allow file sharing
--Group Policies (on the W2K server) allow file sharing

Good hunting!!

JTB
Solutions Architect
MCSE-NT4, MCP+I, MCP-W2K, CCNA, CCDA,
CTE, MCIWD, i-Net+, Network+
(MCSA, MCSE-W2K, MCIWA, SCSA, SCNA in progress)

 

[dyost]

I don't think you understand the problem. From X 192.168.1.x (w2k) I can connect, read,write etc to Y 192.168.2.x (NT). But I cannot get from Y back to X. It gives me a redirector time out. File sharing is enabled on both. I am not using NAT accross the WAN. I have registered IP addresses on my Linux boxes that are using CIPE (VPN) to tunnel my traffic between the two networks. I have all the latest service packs installed.

 

[zoeythecat]

Are they both using NTFS?

 

[dyost]

Yes......both are using NTFS

 

[zoeythecat]

Is this network part of a domain or part of a workgroup?

 

[dyost]

Both networks are seperate domains.

 

[zoeythecat]

Do you have trusts setup?

 

[dyost]

Just figured it out. My CIPE adapters were locked down too tight. When the traffic gets heavy it would open up other ports to use and then the adapter on the other end would not accept the incoming connection on the new port. I set them to accept from only each other but on any port. Thanks for the advice........

 

[victorv]

hi,
I belive that your domain,shares,ip-address,def-gateway ecc
in 2 networks are well configured.

You say that can ping B from A : this means that packets can pass in both sense (infact can also ping A from B).

The 2 networks are also physically separated ?

Probably the router is not "symmetrically" or "mutual"
configured. A file-share on windows is based on SMB protocol
that use ports 137,138,139 tcp and/or udp, different
from port that use ping.

Do FTP, telnet, htttp, ecc, pass in both sense ?

bye