ChadStiller
MIS
Hey all - this is a good one my boss dropped into my lap to research for a client that he has been working with. The situation is as follows:
Site has two servers - one is a NT 4.0 MS Proxy 2.0 & MS Exchange 5.5 server, the other a NT 4.0 file/app/db server. Service packs are current on both boxes and this implementation has been in place and running flawlessly for some time. Users have proxy access to the Internet via a DSL connection, with a "vanilla" service access scheme in place.
The latest Symantec NAV corporate edition (7.5) was put on the file/app server, the SSC console setup, updates scheduled, clients rolled out, etc - no problems there.
The latest Symantec NAV for Exchange (2.1.?) was put on the Proxy/Exchange machine. NAV & Exchange works, but users can no longer surf through the Proxy server UNLESS they have the workstation proxy client (WSP) installed on their systems. Users without the WSP present locally get the generic timeout/can't connect page in Internet Explorer - users with WSP can surf normally with no browser or settings changes.
There have been no permissions, group or user account, or IP changes on the server in question, services all seem to start normally, and no error messages are logged in either the NT logs or within one of the specfic apps. I've gone through the Symantec & Microsoft tech bases and have not found any matching issues.
I've worked with all of these products before, but never in an evironment where the Exchange and Proxy services are on the same machine, and that appears to be the culprit. This is not a site that I work with directly, and is not even in the same city, but I hope the above info is enough for someone to work with.
Any ideas or advice is most heartily thanked for in advance!
Chad D. Stiller, MCSE
Ramcom Technology
cds@ramcom.com
Site has two servers - one is a NT 4.0 MS Proxy 2.0 & MS Exchange 5.5 server, the other a NT 4.0 file/app/db server. Service packs are current on both boxes and this implementation has been in place and running flawlessly for some time. Users have proxy access to the Internet via a DSL connection, with a "vanilla" service access scheme in place.
The latest Symantec NAV corporate edition (7.5) was put on the file/app server, the SSC console setup, updates scheduled, clients rolled out, etc - no problems there.
The latest Symantec NAV for Exchange (2.1.?) was put on the Proxy/Exchange machine. NAV & Exchange works, but users can no longer surf through the Proxy server UNLESS they have the workstation proxy client (WSP) installed on their systems. Users without the WSP present locally get the generic timeout/can't connect page in Internet Explorer - users with WSP can surf normally with no browser or settings changes.
There have been no permissions, group or user account, or IP changes on the server in question, services all seem to start normally, and no error messages are logged in either the NT logs or within one of the specfic apps. I've gone through the Symantec & Microsoft tech bases and have not found any matching issues.
I've worked with all of these products before, but never in an evironment where the Exchange and Proxy services are on the same machine, and that appears to be the culprit. This is not a site that I work with directly, and is not even in the same city, but I hope the above info is enough for someone to work with.
Any ideas or advice is most heartily thanked for in advance!
Chad D. Stiller, MCSE
Ramcom Technology
cds@ramcom.com
