WinGate Remote ShutDown

[blpot]

Just installed Wingate.
Nearly everything works fine.

I use Psshutdown in my private network to switch down unused servers during night. So I want to do with wingate server but it does not work.

I guess Wingate does not allow access and remote login on its server.
Wingate is running on stand alone W2K server. Shutdown command is comming from domaincontroller.

Same configuration worked with my old proxymachine but winproxy

Any ideas and tips?

Thanks
Bernd

[adrien]

Hi

We've used shutdown.exe from the Windows Server Resource Kit with no problem.

I believe remote shutdown uses SMB protocol which works over port 137 - 139 TCP/UDP. Do you see any firewall hits?

Adrien

[blpot]

Hallo!


Thanks for reply!

No, Firewall window is empty.
The difference between old and new is that old machine is NT4 now W2K.

When I decided for Psshutdown, MS shutdown was not able to power down, only shut down and the machine was still running, has this changed now?

As far as I know psshutdown has been integrated into Ressource toolkit.This is all is a little bit intransparent and needs further investigations and experiments.

Can Wingate be inactivated so that I get unlimited access to Network Adapters, does a closed or stopped wingate limit Network adapters?

[adrien]

Hi

There is a setting in WinGate which affects whether it will firewall things after the engine is stopped or not.

It's under Extended networking in GateKeeper.

If you turn this off, then

Net stop WinGateEngine

will stop the engine.

Adrien

[blpot]

Thanks, psshutdown not working was a problem caused by installing as less as possible network services. Did not depend on Wingate.

Works fine.

Thanks for help
Bernd