Usamos cookies para medir audiência e melhorar sua experiência. Você pode aceitar ou recusar a qualquer momento. Veja sobre o iMasters.
pessoal, eh o seguinteaqui tem um servidor (de internet + rede) usando o wingate e rodando IISna minha maquina tem o wingate client e eu gostaria de ter o iis rodando tb, pois preciso fazer uns testes e nao queria mexer no servidor, mas o q acontece? eu instalei o iis e nao consigo rodar ele e o wingate ao mesmo tempo, ou eu tenho internet ou o servidor iis........serah q alguem sabe se tem alguma consiguracao q poderia ser feita para q os dois funcionassem?obrigada,K-ROL
Acredito que o problema seja que o Wingate esta levantando o serviço de webproxy ( porta 80 ) e o iis também utiliza a porta 80 para HTTP.Se você mudar um dos dois de porta poderá ter ambos rodando no mesmo micro.Tive este problema num servidor que fazia NAT da minha rede, mudei o proxy para porta 8080 e tudo ficou perfeito.Fuiz...
Acho mudar as portas o IIS mais facil... coloca 8088 e faz um teste... você sabe onde muda no IIS
Acho mudar as portas o IIS mais facil... coloca 8088 e faz um teste... você sabe onde muda no IIS
Trocar as portas eh melhor mesmo!!!!!
eu tentei, mas nao conseguifui no ferramentas administrativas -> gerenciador do iisno servico Site da Web Padrao, fui em propriedadesna identificacao de site da web coloquei o endereco IP como o IP da minha maquina e a porta TCP 8088 ou 8080, mas na hora q eu vou iniciar dah uma msg de Argumento Invalidotenho q alterar mais em algum lugar?obrigada
nas propriedades do wingate a porta do servidor estah como 2080 e nao 80, serah q tah dando conflito com as portas do servidor geral da rede?
no wingate do servidor tem q ter essa porta (q eu vou utilizar) liberada em alguma configuracao?
K-ROL,
Visitei o site da deerfield e na parte de suporte fala sobre seu problema.
Verefique os procedimentos e tente em seu ambiente.
Fuiz... :D
http://webboard.deerfield.com:9080/wbasp/m...c=2166&msg=5865
Topic: IIS and Wingate conflict (1 / 4)
Conf: WinGate
From: MaxBurn
Date: 3/23/2003 8:43:25 AM
I am having a conflict between Wingate 5 and IIS under windows 2000 advanced server.
I am running the Extended networking driver in wingate for NAT, I have Router unchecked and I am not using the wingate firewall (disabled).
The Problem:
When I restart the server it will not start the default web page, and if I try to start the web page manually it says address already in use. If I then go and shutdown the wingate engine I can start the default web page and restart the wingate engine and it's happy for a day until IIS crashes. IIS runs fine for weeks if Wingate isn't running. I can also use apache web server forever with wingate running with no problem, but I really need IIS for this application.
Any suggestions? All I am trying to do is have this server be able to throw web pages (local and to the internet) through IIS and have it serve the other computers in the office with a shared internet connection. Microsoft Internet connection sharing in my experience has been problematic at best, and I have been using wingate for years alongside apache with no problems.
sj
To reply to this post, or find other related posts Log into the Deerfield.com forum! Top
Topic: RE: IIS and Wingate conflict (2 / 4)
Conf: WinGate
From: odge
Date: 3/23/2003 9:19:16 AM
You WWW proxy server is probably bound to port 80 ... which is IIS
default port... change your WWW proxy to port 85 (or conventionally 3128
or 8080)
Remember to change your clients accordingly.
-----Original Message-----
From: WinGate Listmanager
[mailto:WinGate.listmanager@webboard.deerfield.com]
Sent: Sunday, March 23, 2003 3:35 PM
To: Recipients of 'WinGate' suppressed
Subject: IIS and Wingate conflict
From: "Scott Jalbert"
I am having a conflict between Wingate 5 and IIS under windows 2000
advanced server.
I am running the Extended networking driver in wingate for NAT, I have
Router unchecked and I am not using the wingate firewall (disabled).
The Problem:
When I restart the server it will not start the default web page, and if
I try to start the web page manually it says address already in use. If
I then go and shutdown the wingate engine I can start the default web
page and restart the wingate engine and it's happy for a day until IIS
crashes. IIS runs fine for weeks if Wingate isn't running. I can also
use apache web server forever with wingate running with no problem, but
I really need IIS for this application.
Any suggestions? All I am trying to do is have this server be able to
throw web pages (local and to the internet) through IIS and have it
serve the other computers in the office with a shared internet
connection. Internet connection sharing in my experience has been
problematic at best, and I have been using wingate for years alongside
apache with no problems.
sj
To reply: mailto:WinGate.5865@webboard.deerfield.com
To start a new topic: mailto:WinGate@webboard.deerfield.com
To login: http://webboard.deerfield.com/
To (un)subscribe: mailto: WinGate.list-request@webboard.deerfield.com
To reply to this post, or find other related posts Log into the Deerfield.com forum! Top
Topic: RE: IIS and Wingate conflict (3 / 4)
Conf: WinGate
From: MaxBurn
Date: 3/23/2003 9:47:13 AM
OK! It seems to work. I changed it to 8080 and IIS now starts as normal with the wingate engine running. My networking knowledge weak here, but what did that do? I didn't have to reconfigure the clients at all. I am not using wingate on the rest of the office machines, they are just set up as connect to the internet over LAN. Will they get that setting automatically this way or am I missing something?
To reply to this post, or find other related posts Log into the Deerfield.com forum! Top
Topic: RE: IIS and Wingate conflict (4 / 4)
Conf: WinGate
From: odge
Date: 3/23/2003 10:19:54 AM
Ok well basically you are not using the WWW proxy server for clients,
unfortunately when the WWW proxy server is configured on a port other
than that of 80 it is unable to Redirect ENS sessions (and then use the
caching proxy). This is fine I guess, but if you want to use the caching
service then you must configure the clients to use the wingate server on
port 8080.
I suggest using an auto config file which you can maintain on the server
side. Placing this file into IIS wwwroot directory and then setting the
clients to use this file.
I've attached a proxy1.pac file which you can modify to your network
needs.
And a slightly more advanced proxy file which I use (proxy.pac).
The double pipe ( || ) represents and OR operator. So if something OR
something else OR something other then DO THIS .... there are also elses
involved... it should all make sense
-----Original Message-----
From: WinGate Listmanager
[mailto:WinGate.listmanager@webboard.deerfield.com]
Sent: Sunday, March 23, 2003 4:47 PM
To: Recipients of 'WinGate' suppressed
Subject: RE: IIS and Wingate conflict
From: "Scott Jalbert"
OK! It seems to work. I changed it to 8080 and IIS now starts as normal
with the wingate engine running. My networking knowledge weak here, but
what did that do? I didn't have to reconfigure the clients at all. I am
not using wingate on the rest of the office machines, they are just set
up as connect to the internet over LAN. Will they get that setting
automatically this way or am I missing something?
To reply: mailto:WinGate.5869@webboard.deerfield.com
To start a new topic: mailto:WinGate@webboard.deerfield.com
To login: http://webboard.deerfield.com/
To (un)subscribe: mailto: WinGate.list-request@webboard.deerfield.com
entendi os procedimentos, mas o q quer dizer com www proxy server, tenho q configurar (liberar) a porta no wingate do servidor principal?na minha maquina nao tem nada q faca referencia a isso pra q eu mude a porta, aqui eh tudo client com excecao do iis, mas neste eu jah tentei mudar a porta e dah a msg de argumento invalido
cara, não tem como. Pois quando você instalou o IIS na sua máquina, ela se tornou um "servidor" de aplicações web e o IIS da sua máquina não tem como se conectar no seu servidor da internet.