> > The problems occur when the user does do file/setup/ok and the ini file is actually updated. The next time he logs in if the saved ip is already in use the portmaster assigns a new ip but winsock does not accept the change and fails to properly commu
nicate.
> >
> > We frequently have problems when our (ignorant/stupid/careless) users change the setup and cause this situation.
>
> Sounds more like a problem with trumpet winsock then with the users
> saving the settings.
>
> Patrick
I'll ditto patrick on that one. You need to put an
address <timeout>
command in the winsock login.cmd file and you won't have to worry about
the IP address the user gets...
-Dave Andersen
--
angio@aros.net Complete virtual hosting and business-oriented
system administration Internet services. (WWW, FTP, email)
http://www.aros.net/ http://www.aros.net/about/virtual/
"She totally confused all the passing piranhas"