RichB Posted August 12, 2013 Posted August 12, 2013 Since last wednesday, without any changes been made that I am aware of we keep this error message internally. Externally still works fine and so does staff using the full version of exchange.
twin--turbo Posted August 12, 2013 Posted August 12, 2013 Who's Proxy server is it, and does it have a resolv.conf entry for the internal dns server on site? Rob
RichB Posted August 12, 2013 Author Posted August 12, 2013 Its our server but the internet line comes through our LA with filtering ect. Are you thinking this could be an external issue?
localzuk Posted August 12, 2013 Posted August 12, 2013 If it an internal server, you should really have an exclusion in place from your proxy settings - otherwise you're adding extra hops unnecessarily. That message is coming from your upsteam proxy - smooth5.kirkless.gov.uk (unless you name your internal proxy like that?). So, it looks to me like the upstream proxy is replying saying it has no idea what server that is - which would be right.
kmount Posted August 12, 2013 Posted August 12, 2013 The request is being sent to your LEA and not resolving up there (not unreasonably). Add a proxy exception or try the FQDN 1
RichB Posted August 12, 2013 Author Posted August 12, 2013 The request is being sent to your LEA and not resolving up there (not unreasonably). Add a proxy exception or try the FQDN tried FQDN still no luck and there is rule inplace. Seems strange it ramdomly happenly no-one was even in the building that day!
Sam_Brown Posted August 12, 2013 Posted August 12, 2013 (edited) What does an nslookup give you? And have you checked your internal DNS servers to make sure there's an entry for it in there? How about connecting via the ip address rather than the name? Edited August 12, 2013 by Sam_Brown
twin--turbo Posted August 12, 2013 Posted August 12, 2013 where is your proxying controled from? on the I.E. client or do you have an on site proxy that forwrds to the LEA proxy? Rob
RichB Posted August 12, 2013 Author Posted August 12, 2013 (edited) narrowed the issue down to a PC based issue. Some Pc's work some dont! im leaning to "someone" has messed in GP.... Edited August 12, 2013 by RichB
RichB Posted August 12, 2013 Author Posted August 12, 2013 getting no-where fast here. Update: some machines work some do not, even in the same GP. GP update has the same effect, not restricted to certain areas.
RichB Posted August 12, 2013 Author Posted August 12, 2013 Issue solved! problem with our LEA provider AGAIN... After them saying at 0900 it wasnt there fault. Day wasted.
twin--turbo Posted August 12, 2013 Posted August 12, 2013 But if it's an internal service, why are they involved? Rob
localzuk Posted August 12, 2013 Posted August 12, 2013 But if it's an internal service, why are they involved? Rob Indeed. If its hosted in-house, it should be routed directly from client machines to server without touching external servers at all - ie. it should bypass all proxies (eg. emley:81 should be an exclusion in internet options for the proxy). All our internal servers avoid our proxy entirely.
RichB Posted August 12, 2013 Author Posted August 12, 2013 Was an issue with one of there smoothwall servers we were told. Its an internal service however that is what caused it to break. I would look into the issue further but we have a new exchange install coming next week so we can get things set up correctly then on the new box.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now