Problem in AD

Use this forum to post questions relating to WinGate, feature requests, technical or configuration problems

Moderator: Qbik Staff

Problem in AD

Postby mkobald » Feb 24 06 8:01 pm

I'm running Wingate in an Active Directory environment. I had it previously set up and working fine on a Win98 machine but decided to upgrade to newer hardware and WinXP so I could make use of the Windows authentication. I carefully made note of all the settings on the old system, installed on the new system, and configured as before. No changes were made on the AD server.
The installation, reactivation of Wingate and plugin licenses, and configuration went very smoothly. But now I'm getting no IE browser connectivity on the clients and I can't connect to the Wingate POP3 server. Inbound email is flowing in no problem but internal clients can't do anything. Browser connection settings are for using the www proxy.

My question: what is different in the Wingate setup on WinXP, or in the WinXP networking setup itself that might cause this? Please give me some ideas to look into because I think I've tried everything.

Thanks.
Mike
mkobald
 
Posts: 23
Joined: Oct 18 05 5:53 pm

Re: Problem in AD

Postby Nev » Feb 25 06 12:02 am

Hi Mike,

No good, long shot, but are the adapters / nic's correctly identified in the network tab as Internal / External for the Wingate system?

Report back and someone will take it further.
--
Nev.
Nev
WinGate Guru
 
Posts: 861
Joined: Sep 22 03 11:35 pm
Location: Mudgee ~ NSW ~ Australia

Problem in AD

Postby mkobald » Feb 25 06 4:18 am

Yes, that's probably the very first thing I checked. Funny thing though, at first when they were set to auto both were identified as external and when I would change the internal one to internal it would immediately jump back to auto by itself, but eventually it stayed on what I selected.

Also, I just tried to get into the network to a PCanywhere session from the outside and that worked fine. I can also ping the internal interface from the local network no problem.

What else?
Mike
mkobald
 
Posts: 23
Joined: Oct 18 05 5:53 pm

Problem gone

Postby mkobald » Feb 25 06 6:09 am

Hi again,

Just to be sure I checked the internal/external settings of my nic's and wouldn't you know it, they were both set to external. I know for a fact this was set properly. Why would it change?

Thanks,
Mike
Mike
mkobald
 
Posts: 23
Joined: Oct 18 05 5:53 pm

Re: Problem gone

Postby Nev » Feb 28 06 1:40 am

mkobald wrote:Hi again,

Just to be sure I checked the internal/external settings of my nic's and wouldn't you know it, they were both set to external. I know for a fact this was set properly. Why would it change?

Thanks,
Mike


Hi Mike,

Well Wingate will make a decision based on a few facts, such as whether or not a gateway is assigned.

Out of interest, [this could have a bearing on it], what are the Int / Ext ip ranges, any non private ones?
--
Nev.
Nev
WinGate Guru
 
Posts: 861
Joined: Sep 22 03 11:35 pm
Location: Mudgee ~ NSW ~ Australia

Postby Pascal » Feb 28 06 11:27 am

Hi Mike,

The adapter settings should stick to what you have them set at.

There is a current bug which we are tracking down where the UI will revert back to it's original setting while you have the configuration dialog open on every pulse of update information.

On the issue of moving between 98 and XP - check the service login properties as a first step. We normally recommend that you create an account with full permissions to the AD for WinGate and then log the service in as that (Rather than it's normal defaults)

Details are here and this also provides a good overview.
Pascal

Qbik New Zealand
pascalv@qbik.com
http://www.qbik.com
Pascal
Qbik Staff
 
Posts: 2623
Joined: Sep 08 03 8:19 pm
Location: Auckland, New Zealand


Return to WinGate

Who is online

Users browsing this forum: Google [Bot] and 1 guest