Accesing localhost applications

[gmamador]

I am on an 8-computer network, all of then running XP Professional and Wingate through the WGIC configuration. The machine where the Wingate server was installed had some problems so we switched the nic cards, uninstalled WG software and now I have installed the wingate server on my machine according to your instructions (DSL, two nic cards). I now face the two following problems:
1.- I cannot work anymore in Visual Studio, because IIS is stopped, I cannot access my localhost sites (Firewall or binding settings ????)
I guess this should be easy to solve, so I do appreciatte your quick answer on this.

2.- At intervals, I would say every two hours or so, navigation stops, at my machine and also at all the client machines. Gatekeeper seems to be working normally, but nobody has access to the Internet. At that point I am forced to restart my computer, after which everything returns to normal until again it fails after about two more hours.

We have a numbered network from 192.168.0.1 to 8, not using WG DHCP. I made an express instalation, with everything at the default setting except the mail server that I did not install

Thanks in advance for your attention

[neil]

For number 1, I would recommend running IIS on a different port (say 8080) and then it will be able to happily co-exist with WinGate running its WWW proxy on port 80.

As for number two, which version of WinGate are you running?! 5.2.0? Do you get any Syslogs? This sounds a bit like an Out Of Buffers problem we used to get pre 5.2. When this happens again, try getting one of the client PCs to ping the WinGate server. If they can achieve this, then try and telnet to the telnet proxy in wingate and connect out via that. Basically to see if its the ENS thats causing the problem or a general network lock up.

Regards

Neil

[gmamador]

Thank you very much for your answer.

For number 1 I changed the port (80 to 8080) in Wingate and left IIS running on port 80. I hope there is no problem to Wingate.

For number 2, before getting your reply, I started closely examining my system at the moment that the problem ocurred. I discovered that always at that precise time the task manager reported problems with my SQL service (I am running version 8.00.382 of the SQL Service Manager provided by MSDE local instalation). If I keep the SQL Service stopped all the time, I never have that problem, that's to say, Wingate keeps running 100% of the time, without any interruption. I am running the latest version 5.2.0. The problem will propably hit again when I start working heavily with my databases, but for the moment it's OK