Wingate does not recognize RAS (dial-in) until someone dials and hangs interface so I cannot put this interface as trusted. Then I put it as trusted manually every time.
If I don't do this dial-up clients cannot connect to ftp servers, office computers.
Can anyone help me
Wingate & RAS
Moderator: Qbik Staff
6 posts
• Page 1 of 1
by eric » Feb 13 04 7:26 am
hi there,
I'm using a windows 2k advanced server with wingate 5.2.2. The question is how i would configure the server to accept incoming calls and connect it to the internet.
In my current set-up, the windows is already accepting calls but the caller has to setup use proxy to be able to browse the internet. And everytime the dial in user do this upon logging in the next day or so, the dial in system would ask for a username, password and logon domain. We don't have a domain. Any solution please? Thanks
I'm using a windows 2k advanced server with wingate 5.2.2. The question is how i would configure the server to accept incoming calls and connect it to the internet.
In my current set-up, the windows is already accepting calls but the caller has to setup use proxy to be able to browse the internet. And everytime the dial in user do this upon logging in the next day or so, the dial in system would ask for a username, password and logon domain. We don't have a domain. Any solution please? Thanks
- eric
- Posts: 26
- Joined: Feb 13 04 7:18 am
by neil » Feb 13 04 9:49 am
Jah,
I don't think the changes we are making will help your situation. We are making improvements to how we are handle multiple dial up connections, but in the situation you describe these changes probably wont have any effect.
WinGate does not know about dial in connections until someone dials in because Windows doesn't (in a way) either. If you boot the dial in server and do a 'route print' you wont see the dial-in interface's IP listed. If you then connect a dial-in client it then shows up, even if you disconnect this dial-in client this interface IP stays in the route table. Hence WinGate can't know about.
The best solution to this is you will have to bind each proxy you want to allow dial-in users to utilise to 'any' interface. Thus for example, in WWW proxy, under the Bindings tab set it to 'Allow connections coming in on any interface'. Even though the dial-in interface wont actually appear in GK the proxies will accept connections as long as they have been set in this way. Of course this then becomes a slight security issue, as you are opening up your proxies to the world. So you will then need to create policies to lock these proxies down to just the users you want to allow access to.
Regards
Neil
I don't think the changes we are making will help your situation. We are making improvements to how we are handle multiple dial up connections, but in the situation you describe these changes probably wont have any effect.
WinGate does not know about dial in connections until someone dials in because Windows doesn't (in a way) either. If you boot the dial in server and do a 'route print' you wont see the dial-in interface's IP listed. If you then connect a dial-in client it then shows up, even if you disconnect this dial-in client this interface IP stays in the route table. Hence WinGate can't know about.
The best solution to this is you will have to bind each proxy you want to allow dial-in users to utilise to 'any' interface. Thus for example, in WWW proxy, under the Bindings tab set it to 'Allow connections coming in on any interface'. Even though the dial-in interface wont actually appear in GK the proxies will accept connections as long as they have been set in this way. Of course this then becomes a slight security issue, as you are opening up your proxies to the world. So you will then need to create policies to lock these proxies down to just the users you want to allow access to.
Regards
Neil
- neil
- Qbik Staff
- Posts: 356
- Joined: Sep 03 03 2:42 pm
- Location: Auckland
6 posts
• Page 1 of 1
Who is online
Users browsing this forum: Majestic-12 [Bot] and 15 guests