Problems using proxy server through vpn, plus DC error

We have users in Monaco (ahhh for the chance to go do some local tech support!), who lost internet connectivity to our proxy server in London at the weekend.  They get the error in IE of:

Appliance Error (configuration_error)
Your request could not be processed because of a configuration error: "No authority could be contacted for authentication."  

They are in a separate domain, and connect back through a VPN to us.  If the proxy server name in IE is changed to one local to them, they are fine.  

At the same time (over the weekend), I'm seeing these errors on our DC here in London, where the Monaco Domain can't be contacted.  These errors did not occur before the weekend.  Spooky coincidence??


Event Type:      Error
Event Source:      NETLOGON
Event Category:      None
Event ID:      5719
Date:            13/10/2004
Time:            12:16:29
User:            N/A
Computer:      LGLONA01
Description:
No Windows NT or Windows 2000 Domain Controller is available for domain<MonacoDomain>. The following error occurred:
There are currently no logon servers available to service the logon request.  
Data:

I'm currently poking through the suggestions on www.eventid.net for this error, but not finding a fix yet.  Anyone got any ideas?  cheers.
LVL 23
Danny ChildIT ManagerAsked:
Who is Participating?
 
harleyjdConnect With a Mentor Commented:
How is the vpn configured? IPSEC tunnel or PPTP back to your server or a RAS firewall?

Did you used to be able to ping monaco?

Has someone enabled some sort of firewall in monaco?

You have remote access to monaco, -if you can't ping it, how?

The trust between the sites is broken, I suspect it's monaco stopping london connecting somehow. Make sure those sysvol/netlogon shares are visible on the monaco server from monaco....

I really think you need to be onsite. Tell your boss "some guy on the internet said I had to go"

0
 
harleyjdCommented:
What's going on with their domain controller? Sounds like Monaco can't see it, so noone else is going to be able to either.

I'd focus on the DC not your proxy.

Check the sysvol and netlogon folders are shared correctly. Check the DNS in Monaco. Fly out there and see it for yourself.

(surely I deserve the points just for that last suggestion) :)

0
 
Danny ChildIT ManagerAuthor Commented:
ok, the Monaco server can open both the \\london\netlogon and \\london\sysvol shares.
Monaco can ping London, but not the other way around (I'm surprised pings work at all, I thought the VPN would kill them)

dns in monaco seems ok - the 2 servers it's set to use are:
itself - as primary
the london DC as secondary.

nslookups on www addresses work ok (though I get the occassional timeout).  I also tried reversing the order of the dns servers, and repeating the www lookups.  Still good.  

and harleyjd, when that plane ticket's in my hand, the points are all yours....

kinda looking like authentication to me, but hey, if I had the answers, I wouldn't be here!
0
Cloud Class® Course: CompTIA Cloud+

The CompTIA Cloud+ Basic training course will teach you about cloud concepts and models, data storage, networking, and network infrastructure.

 
Danny ChildIT ManagerAuthor Commented:
harleyjd:
vpn - managed by 2 Netscreen 25 boxes, one at each end.  Pretty sure it's pptp.

pinging monaco?  dunno if it *used* to work, I'm the new guy round here

monaco firewall?  shouldn't be any changes.

remote access?  some machines, ie Mine, are permissioned to use the vpn, so I can pcAnywhere to it (and ping it), but the DC can't.  

trust between the sites?  I'll check it out, but I'm not exactly God's Gift to Trusts, so I'll go easy...  and yes, the monaco box can open \\LondonDC\netlogon.

running
repadmin /showreps <LondonDC> dc=<DomainName>,dc=com

show all is ok, but doesn't list the Monaco servers.  Methinks it should!

There's also plans underfoot to make all the Monaco users join our domain, so this is all gonna change anyway.   Thanks for all your help, this is really helping me get a handle on this.  
0
 
harleyjdCommented:
ahhh...

If the DC cannot access the VPN, then the DC cannot authenticate anyone from the other domain as either the requests do not arrive, or the responses are blocked. This goes to the trust as well - it can't be verified if it can't communicate.

I'm not sure there should be replication between trusted DC's - I'm no gift either - so I'm not sure that the repadmin path is the right one.

I think it's really important that the 2 DC's have full and complete visibility of one another.

One other thought - check the routing on your PC vs the london server. Make sure there is a valid route for monaco on the server.

0
 
Danny ChildIT ManagerAuthor Commented:
I'll keep on it.  We've set up a workaround to give the users a local proxy in monaco, so it looks like my trip there is off... sob.
harleyjd - thanks for all the excellent info.
0
 
harleyjdCommented:
Well, I'm sorry I coulfn't get you the trip...
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.