WinGate Forums

by **nole57** » Oct 28 04 1:59 am

I had to re-install wingate when my servers (2000) hard drive failed, and I can connect to the internet using my dial-up networking dialer, when I installed wingate and wanted it to connect for me, it dials, but can't complete the connection, and re-dials ...forever...
If I stop the wingate dialer, it hangs up the port, and modem, and I have to re-set the server to get control. If I dial into the internet with the DUN dialer, the clients can access the internet, but they don't activate the wingate dialer.

by **Pascal** » Oct 28 04 9:46 am

1. Which version of WinGate are you using?
2. Did you reconfigure the dialer completely? On a NT based OS (NT, 2K, XP, 2003) you have to specify the password as well.

One last idea - if you turn on full logging for the dialer and have it try to connect again you should get appropriate error messages in the log file which might help point at the exact problem.

by **Nev** » Oct 28 04 11:10 pm

Pascal wrote:1. Which version of WinGate are you using?
2. Did you reconfigure the dialer completely? On a NT based OS (NT, 2K, XP, 2003) you have to specify the password as well.

One last idea - if you turn on full logging for the dialer and have it try to connect again you should get appropriate error messages in the log file which might help point at the exact problem.

Hi all,

At an upgrade of V5.2.3~6.0.3 today all working 100% prior.

No way could be found to have Wingate dial the profile, POP3, HTTP etc, however it would connect & authenticate manually [Dial button].

Activity showed in GK, hmm just recalled that I didn't check adaptor usage but web was served to clients if profile was manually dialed.

Debug logging yielded nothing > reverted painfully to 5.2.3 again [sigh].

Win XP Pro SP1 Cel 2.6/512mb, single dial up, etc etc.

Any ideas before I try again?

Nev.

by **Pascal** » Oct 28 04 11:14 pm

Just off the top of my head I recall there was mentions on the forums earlier about a DNS lookup required to instigate the dialer. (Can't remember if that discussion was on the previous forums, might have been)

I don't have code in front of me, but there used to be a tickbox for "Allow requests to instigate the dialer".

Only other thought - is it a software modem?

by **Pascal** » Oct 28 04 11:18 pm

This post

http://forums.qbik.com/viewtopic.php?t= ... dns+dialer

has some details on that. (Your post)

by **Nev** » Oct 29 04 2:40 am

Pascal wrote:Just off the top of my head I recall there was mentions on the forums earlier about a DNS lookup required to instigate the dialer. (Can't remember if that discussion was on the previous forums, might have been)

I don't have code in front of me, but there used to be a tickbox for "Allow requests to instigate the dialer".

Only other thought - is it a software modem?

G'day Pascal,

From memory Allow DNS requests to initate dialer should be enabled but will examine it when I go there [6.0.3] again.

No not a Winmodem, just a standard External one.

Thanks,
Nev.

by **nole57** » Oct 29 04 1:38 pm

I'm running ver 4.x 12 user.
When I re-installed the Operating system on the server, I re-created the dial-up networking connector, and tested it. It connected fine, and I could browse fine. I have dhcp and dns running on the server also. Next I installed the wingate, and told it to use the same dialer I had set up in windows. it picks up the line, dials, handshakes, disconnects, and starts over. Once this starts, I can't stop it except to re-boot the server.

by **Pascal** » Oct 29 04 1:48 pm

Which 4.x? The dialer changed dramatically around 4.4.2 (If I remember correctly)

by **nole57** » Oct 29 04 2:08 pm

ver 4.1.1

by **erwin** » Oct 29 04 2:54 pm

Hi there

I had to re-install wingate when my servers (2000) hard drive failed, and I can connect to the internet using my dial-up networking dialer, when I installed wingate and wanted it to connect for me, it dials, but can't complete the connection, and re-dials ...forever...

Not sure if its related to your issue, but I have seen something similar to this occurring here in the lab, and its usually when an incorrect/old driver is installed for the modem(usually external) or the modem/dialer config has become corrupted somehow.

Since you have done a server install, as a suggestion you might want to check the driver and settings for the modem are correct in the OS, and then possibly try creating a new dialup profile and seeing if WinGate will use this successfully.

Regards
Erwin

by **nole57** » Oct 29 04 2:59 pm

The system uses an external 56K modem, by US Robotics. It was using a generic modem driver that only allowed it to connect at 9600bps. I installed an updated driver that allows it to connect quite a bit faster, but now we have these other problems. Could this be it?

WinGate Forums

dialer won't connect

dialer won't connect

dialer won't connect

dialer

dialer...

Who is online