Problema con terminal Server

08/03/2005 - 13:25 por Luis Oporta | Informe spam

Buenos dias.

Tengo instalado isa server 2004 en el cual cree dos reglas de publicación de
servidor terminal server, que detallo acontinuación:

1.- La LLame Terminal 1
Action = Allow
Traffic = RDP (terminal Service) server
From = anywhere
To = 192.168.10.163
Networks = External y Perimeter
ESTA FUNCIONA CORRECTAMENTE
2.- La LLame Terminal 2
Action = Allow
Traffic = RDP (terminal Service) server
From = External y perimeter 2 (perimeter 2 es otra red la cual
configure como una red perimetral)
To = 192.168.10.67
Networks = Perimeter 2
CUANDO INTENTO ACCESAR DESDE LA RED INTERNA FUNCIONA
CORRECTAMENTE PERO DESDE EL EXTERIOR NO FUNCIONA Y EN EL LOG NO APARECE NADA

Me gustaria saber que estoy haciendo mal

Mucha gracias de antemano

Siga el debate

7 respuestas

Tengo una respuesta

Preguntas similare

Mostrar todos los temas similares

Leer las respuestas

#1 Jorge Patricio Díaz Guzmán \(MCP\)

08/03/2005 - 14:00 | Informe spam

Los dos se accesan por distintas IPs publicas?

Jorge Patricio Díaz Guzmán
MCP

"Luis Oporta" escribió en el mensaje
news:
Mostrar la cita

Responder a este mensaje

#2 Luis Oporta

08/03/2005 - 14:25 | Informe spam

si son dirección IP publicas

"Jorge Patricio Díaz Guzmán (MCP)" wrote:

Mostrar la cita

Responder a este mensaje

#3 Jorge Patricio Díaz Guzmán \(MCP\)

08/03/2005 - 14:41 | Informe spam

En la publicación de los 2 server, cuando configuras el FROM con la externa,
especificas la IP publica que usarás?
Como estás publicando 2 servicios iguales hay que asignar las direcciones IP
externas a cada uno.
En el tab networks especificas por cual IP publica o perimetral va a
"escuchar"

Jorge Patricio Díaz Guzmán
MCP

"Luis Oporta" escribió en el mensaje
news:
Mostrar la cita

Responder a este mensaje

#4 Luis Oporta

08/03/2005 - 15:11 | Informe spam

me aparece esto en alerta:
Server publishing rule [Las Gaviotas] that maps 192.168.10.67:3389 TCP to
192.168.10.65:3389 for protocol [RDP (Terminal Services) Server] was unable
to bind a socket for the server. The server publishing rule cannot be
applied. The Firewall service failed to bind a socket for the server on ISA
Server since another process is using the same port. Check if any other
process is using the same port, and stop it if necessary.
Server publishing rule [Las Gaviotas] that maps 192.168.10.67:3389 TCP to
192.168.11.5:3389 for protocol [RDP (Terminal Services) Server] was unable to
bind a socket for the server. The server publishing rule cannot be applied.
The Firewall service failed to bind a socket for the server on ISA Server
since another process is using the same port. Check if any other process is
using the same port, and stop it if necessary.
Server publishing rule [Las Gaviotas] that maps 192.168.10.67:3389 TCP to
192.168.11.9:3389 for protocol [RDP (Terminal Services) Server] was unable to
bind a socket for the server. The server publishing rule cannot be applied.
The Firewall service failed to bind a socket for the server on ISA Server
since another process is using the same port. Check if any other process is
using the same port, and stop it if necessary.
Server publishing rule [Las Gaviotas] that maps 192.168.10.67:3389 TCP to
192.168.11.25:3389 for protocol [RDP (Terminal Services) Server] was unable
to bind a socket for the server. The server publishing rule cannot be
applied. The Firewall service failed to bind a socket for the server on ISA
Server since another process is using the same port. Check if any other
process is using the same port, and stop it if necessary.
Server publishing rule [Las Gaviotas] that maps 192.168.10.67:3389 TCP to
192.168.11.29:3389 for protocol [RDP (Terminal Services) Server] was unable
to bind a socket for the server. The server publishing rule cannot be
applied. The Firewall service failed to bind a socket for the server on ISA
Server since another process is using the same port. Check if any other
process is using the same port, and stop it if necessary.
Server publishing rule [Las Gaviotas] that maps 192.168.10.67:3389 TCP to
192.168.11.33:3389 for protocol [RDP (Terminal Services) Server] was unable
to bind a socket for the server. The server publishing rule cannot be
applied. The Firewall service failed to bind a socket for the server on ISA
Server since another process is using the same port. Check if any other
process is using the same port, and stop it if necessary.
Server publishing rule [Las Gaviotas] that maps 192.168.10.67:3389 TCP to
192.168.11.37:3389 for protocol [RDP (Terminal Services) Server] was unable
to bind a socket for the server. The server publishing rule cannot be
applied. The Firewall service failed to bind a socket for the server on ISA
Server since another process is using the same port. Check if any other
process is using the same port, and stop it if necessary.
Server publishing rule [Las Gaviotas] that maps 192.168.10.67:3389 TCP to
192.168.11.41:3389 for protocol [RDP (Terminal Services) Server] was unable
to bind a socket for the server. The server publishing rule cannot be
applied. The Firewall service failed to bind a socket for the server on ISA
Server since another process is using the same port. Check if any other
process is using the same port, and stop it if necessary.
Server publishing rule [Las Gaviotas] that maps 192.168.10.67:3389 TCP to
192.168.11.45:3389 for protocol [RDP (Terminal Services) Server] was unable
to bind a socket for the server. The server publishing rule cannot be
applied. The Firewall service failed to bind a socket for the server on ISA
Server since another process is using the same port. Check if any other
process is using the same port, and stop it if necessary.
Server publishing rule [Las Gaviotas] that maps 192.168.10.67:3389 TCP to
192.168.11.53:3389 for protocol [RDP (Terminal Services) Server] was unable
to bind a socket for the server. The server publishing rule cannot be
applied. The Firewall service failed to bind a socket for the server on ISA
Server since another process is using the same port. Check if any other
process is using the same port, and stop it if necessary.
Server publishing rule [Las Gaviotas] that maps 192.168.10.67:3389 TCP to
192.168.11.69:3389 for protocol [RDP (Terminal Services) Server] was unable
to bind a socket for the server. The server publishing rule cannot be
applied. The Firewall service failed to bind a socket for the server on ISA
Server since another process is using the same port. Check if any other
process is using the same port, and stop it if necessary.
Server publishing rule [Las Gaviotas] that maps 192.168.10.67:3389 TCP to
192.168.11.73:3389 for protocol [RDP (Terminal Services) Server] was unable
to bind a socket for the server. The server publishing rule cannot be
applied. The Firewall service failed to bind a socket for the server on ISA
Server since another process is using the same port. Check if any other
process is using the same port, and stop it if necessary.
Server publishing rule [Las Gaviotas] that maps 192.168.10.67:3389 TCP to
192.168.11.93:3389 for protocol [RDP (Terminal Services) Server] was unable
to bind a socket for the server. The server publishing rule cannot be
applied. The Firewall service failed to bind a socket for the server on ISA
Server since another process is using the same port. Check if any other
process is using the same port, and stop it if necessary.
Server publishing rule [Las Gaviotas] that maps 192.168.10.67:3389 TCP to
192.168.11.105:3389 for protocol [RDP (Terminal Services) Server] was unable
to bind a socket for the server. The server publishing rule cannot be
applied. The Firewall service failed to bind a socket for the server on ISA
Server since another process is using the same port. Check if any other
process is using the same port, and stop it if necessary.
Server publishing rule [Las Gaviotas] that maps 192.168.10.67:3389 TCP to
192.168.11.109:3389 for protocol [RDP (Terminal Services) Server] was unable
to bind a socket for the server. The server publishing rule cannot be
applied. The Firewall service failed to bind a socket for the server on ISA
Server since another process is using the same port. Check if any other
process is using the same port, and stop it if necessary.
Server publishing rule [Las Gaviotas] that maps 192.168.10.67:3389 TCP to
192.168.11.117:3389 for protocol [RDP (Terminal Services) Server] was unable
to bind a socket for the server. The server publishing rule cannot be
applied. The Firewall service failed to bind a socket for the server on ISA
Server since another process is using the same port. Check if any other
process is using the same port, and stop it if necessary.
Server publishing rule [Las Gaviotas] that maps 192.168.10.67:3389 TCP to
192.168.11.121:3389 for protocol [RDP (Terminal Services) Server] was unable
to bind a socket for the server. The server publishing rule cannot be
applied. The Firewall service failed to bind a socket for the server on ISA
Server since another process is using the same port. Check if any other
process is using the same port, and stop it if necessary.
Server publishing rule [Las Gaviotas] that maps 192.168.10.67:3389 TCP to
192.168.11.133:3389 for protocol [RDP (Terminal Services) Server] was unable
to bind a socket for the server. The server publishing rule cannot be
applied. The Firewall service failed to bind a socket for the server on ISA
Server since another process is using the same port. Check if any other
process is using the same port, and stop it if necessary.
Server publishing rule [Las Gaviotas] that maps 192.168.10.67:3389 TCP to
192.168.11.137:3389 for protocol [RDP (Terminal Services) Server] was unable
to bind a socket for the server. The server publishing rule cannot be
applied. The Firewall service failed to bind a socket for the server on ISA
Server since another process is using the same port. Check if any other
process is using the same port, and stop it if necessary.
Server publishing rule [Las Gaviotas] that maps 192.168.10.67:3389 TCP to
192.168.11.153:3389 for protocol [RDP (Terminal Services) Server] was unable
to bind a socket for the server. The server publishing rule cannot be
applied. The Firewall service failed to bind a socket for the server on ISA
Server since another process is using the same port. Check if any other
process is using the same port, and stop it if necessary.
Server publishing rule [Las Gaviotas] that maps 192.168.10.67:3389 TCP to
192.168.11.169:3389 for protocol [RDP (Terminal Services) Server] was unable
to bind a socket for the server. The server publishing rule cannot be
applied. The Firewall service failed to bind a socket for the server on ISA
Server since another process is using the same port. Check if any other
process is using the same port, and stop it if necessary.
Server publishing rule [Las Gaviotas] that maps 192.168.10.67:3389 TCP to
192.168.11.181:3389 for protocol [RDP (Terminal Services) Server] was unable
to bind a socket for the server. The server publishing rule cannot be
applied. The Firewall service failed to bind a socket for the server on ISA
Server since another process is using the same port. Check if any other
process is using the same port, and stop it if necessary.
Server publishing rule [Las Gaviotas] that maps 192.168.10.67:3389 TCP to
192.168.11.201:3389 for protocol [RDP (Terminal Services) Server] was unable
to bind a socket for the server. The server publishing rule cannot be
applied. The Firewall service failed to bind a socket for the server on ISA
Server since another process is using the same port. Check if any other
process is using the same port, and stop it if necessary.
Server publishing rule [Las Gaviotas] that maps 192.168.10.67:3389 TCP to
192.168.11.209:3389 for protocol [RDP (Terminal Services) Server] was unable
to bind a socket for the server. The server publishing rule cannot be
applied. The Firewall service failed to bind a socket for the server on ISA
Server since another process is using the same port. Check if any other
process is using the same port, and stop it if necessary.
Server publishing rule [Las Gaviotas] that maps 192.168.10.67:3389 TCP to
192.168.11.213:3389 for protocol [RDP (Terminal Services) Server] was unable
to bind a socket for the server. The server publishing rule cannot be
applied. The Firewall service failed to bind a socket for the server on ISA
Server since another process is using the same port. Check if any other
process is using the same port, and stop it if necessary.
Server publishing rule [Las Gaviotas] that maps 192.168.10.67:3389 TCP to
192.168.11.217:3389 for protocol [RDP (Terminal Services) Server] was unable
to bind a socket for the server. The server publishing rule cannot be
applied. The Firewall service failed to bind a socket for the server on ISA
Server since another process is using the same port. Check if any other
process is using the same port, and stop it if necessary.
Server publishing rule [Las Gaviotas] that maps 192.168.10.67:3389 TCP to
192.168.11.221:3389 for protocol [RDP (Terminal Services) Server] was unable
to bind a socket for the server. The server publishing rule cannot be
applied. The Firewall service failed to bind a socket for the server on ISA
Server since another process is using the same port. Check if any other
process is using the same port, and stop it if necessary.
Server publishing rule [Las Gaviotas] that maps 192.168.10.67:3389 TCP to
192.168.11.225:3389 for protocol [RDP (Terminal Services) Server] was unable
to bind a socket for the server. The server publishing rule cannot be
applied. The Firewall service failed to bind a socket for the server on ISA
Server since another process is using the same port. Check if any other
process is using the same port, and stop it if necessary.
Server publishing rule [Las Gaviotas] that maps 192.168.10.67:3389 TCP to
192.168.11.233:3389 for protocol [RDP (Terminal Services) Server] was unable
to bind a socket for the server. The server publishing rule cannot be
applied. The Firewall service failed to bind a socket for the server on ISA
Server since another process is using the same port. Check if any other
process is using the same port, and stop it if necessary.
Server publishing rule [Las Gaviotas] that maps 192.168.10.67:3389 TCP to
192.168.11.237:3389 for protocol [RDP (Terminal Services) Server] was unable
to bind a socket for the server. The server publishing rule cannot be
applied. The Firewall service failed to bind a socket for the server on ISA
Server since another process is using the same port. Check if any other
process is using the same port, and stop it if necessary.
Server publishing rule [Las Gaviotas] that maps 192.168.10.67:3389 TCP to
192.168.11.249:3389 for protocol [RDP (Terminal Services) Server] was unable
to bind a socket for the server. The server publishing rule cannot be
applied. The Firewall service failed to bind a socket for the server on ISA
Server since another process is using the same port. Check if any other
process is using the same port, and stop it if necessary.
Server publishing rule [Las Gaviotas] that maps 192.168.10.67:3389 TCP to
192.168.11.253:3389 for protocol [RDP (Terminal Services) Server] was unable
to bind a socket for the server. The server publishing rule cannot be
applied. The Firewall service failed to bind a socket for the server on ISA
Server since another process is using the same port. Check if any other
process is using the same port, and stop it if necessary.
Server publishing rule [Las Gaviotas] that maps 192.168.10.67:3389 TCP to
192.168.12.12:3389 for protocol [RDP (Terminal Services) Server] was unable
to bind a socket for the server. The server publishing rule cannot be
applied. The Firewall service failed to bind a socket for the server on ISA
Server since another process is using the same port. Check if any other
process is using the same port, and stop it if necessary.
Server publishing rule [Las Gaviotas] that maps 192.168.10.67:3389 TCP to
200.109.83.171:3389 for protocol [RDP (Terminal Services) Server] was unable
to bind a socket for the server. The server publishing rule cannot be
applied. The Firewall service failed to bind a socket for the server on ISA
Server since another process is using the same port. Check if any other
process is using the same port, and stop it if necessary.

"Jorge Patricio Díaz Guzmán (MCP)" wrote:

Mostrar la cita

Responder a este mensaje

#5 Jorge Patricio Díaz Guzmán \(MCP\)

08/03/2005 - 15:34 | Informe spam

Es justo lo que te estaba comentando. Debes especificar solo una IP tanto en
la perimetral como en la externa y debe ser única para cada publicación

Jorge Patricio Díaz Guzmán
MCP

"Luis Oporta" escribió en el mensaje
news:
Mostrar la cita

Responder a este mensaje

Ads by Google

Hacer una pregunta Siguiente

Tengo una respuesta

1 2

Busqueda sugerida