Discussion Locked

RPC Connects one way but not the Other?

0 helpful
12 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I have 2 sites connected by a 56K WAN Link. WinNT4 SP5 and Windows 98.

All of the Computers in the Remote Site can connect to all the servers and PC's in our site.

From our site I cannot connect to any of the servers or PC's in the remote site. I can ping all the servers and PC's, but cannot see them in the network neighborhood or connect via the UNC names.

I ran RPCPing Server on one of our servers and Client on one of the servers in the Remote office and it worked fine.

I then ran the RPCPing Server on a server in the Remote Office and the client on the server here and it wouldn't work. Then I ran it with security and it worked??

I can also run server manager and event viewer on a server in the remote site and connect to the servers here, but cannot run them here and connect to the servers there?

Everything is in the same Domain. One of the servers in the remote site is a BDC, the other is a Member Server.

12 replies

by work

It looks like a name resolution issue. Set-up WINS or lmhosts file.

by dc1

Do you use WINS or DNS? Another thing to look at is the throughput on your 56k link.

by sdfgsdf

check your comms stuff like wins, dns, gateways, etc as well as shares, permissions, and trusts. on an unrelated not, i would look into SP6. i had a ton of problems with SP5.

by mwhite

Definitely a name resolution problem. Utilize your lmhosts file to troubleshoot.

by iglover

Okay I had to use my bosses account to post this because tech republic will not allow you to post an answer to your own question or post comments without closing. Name Resolution is working as I can ping all the computers in the other office. I ambeginning to think it is a firewall problem as I can connect my PC to the network on the outside of my firewall and connect to the UNC shares? Any Ideas?

by david_dennison

What is happening is that you are not getting namebios resolution. Let say for instance that you go to start, run and type in \\BDCname you would expect to get a connection to the ipc$ and see a list of all avalible connections to that server. But from what I see you are not. But if you try to connect by using \\BDCipaddress (\\10.1.1.1) from an NT Server, you will make that connection. There are two ways to correct this problem. One is to set up the PC in the Hosts table, This is involved. TheSecond is to Set up WINS. To do this Install the WINS service on both server, and Set them up as push/pull partners. next you want to add the WINS servers IP to the DHCP (Scope parameter 44 and 46) or add it to each pc (pointing to the local server of course). Once this is done you will need to reboot everything and about 5 minutes later you will be able to connect using the NetBios names..

by jcharlton

Okay...turns out the problem was the firewall was translating the addresses to get on the internet (as we have a shared internet/wan link between our site and Telus)and then sending them over the wan link as an internet address at which point the lan routers would drop the packet.

This discussion is closed to new replies.