Tengo un problema de RED

20/10/2008 - 00:35 por JUAN REYES | Informe spam

Tengo TRES SERVIDORES DL380

1.- 1ro PDC con Windows 2003 server, IP 192.168.1.5, SM 255.255.255.0, GW
192.168.1.1, dhcp 192.168.1.16 to 192.168.1.200

2.- 2do Member Server con Windows 2003 server y EXCANGE SERVER 2007, IP
192.168.1.8, SM 255.255.255.0 GW 192.168.1.1

3.- 3er SDC Windows 2003 server, base de datos ORACLE, IP 192.168.1.7, SM
255.255.255.0, GW 192.168.1.1

4.- y demas pcs y printer en la red.

EL PROBLEMA ES EL SIGUIENTE:

El servidor 3ro, que es mi sevidor de base de datos, de buenas a primera
solo hace ping al servidor 1ro mi PDC, no hace ping al router 192.168.1.1,
sin embargo los demas servidores si.
Todos los servidore lo ven a el, pero el no. Tambien no hace ping a algunos
hosts de la red.
Mas estrano es que cuando hago ping, por ejemplo al router 192.168.1.1 a
veces responde una unica vez y comienza a darme time out.

No he podido identificar el problema, mi server tiene dos tarjetas, la he
intercambiado, desintalado, cambiado de salida en el switch y no logro que se
vea en la red como se debe.

Mis clientes ultimamente cuando estan utilizando la base de datos de buenas
a primera la base de datos se desconecta y he llegado a relacionar este
problema con el problema anteriormente descripto.

TIENE ALGUNA IDEA DE LO QUE PUEDE ESTAR PASANDO. SI NECESITAN MAS
INOFRMACION POR FAVOR NOTIFIQUEME PARA DARLE MAS DETALLE.

Siga el debate

28 respuestas

Tengo una respuesta

Preguntas similare

Mostrar todos los temas similares

Leer las respuestas

#16 JUAN REYES

21/10/2008 - 14:18 | Informe spam

Guillermos muchisimas gracias por toda la ayuda prestada. Te informo que el
cambio de direccion de la 192.168.1.7 a la 192.168.1.12 ha dado resultado. Lo
que temo es que al no saber con claridad que demonios pasa esto podria
repetirse.

Con relacion a la parte de hardware, aun crees que es un problema fisico del
servidor, la tarjetas estan respondiendo bien, hasta ahora.

SI TIENES MAS INFORMACION SOBRE ESTE CASO EN PARTICULAR POR FAVOR ENVIAR A
MI CORREO

MUCHAS GRACIAS, CUALQUIER COSA PUEDO CONTACTARTE DE NUEVO????

"Guillermo Delprato [MS-MVP]" wrote:

Luego de cambiar la dirección IP, hay que hacer:
IPCONFIG /REGISTERDNS

Y si es controlador de dominio, además
NET STOP NETLOGON

NET START NETLOGON

Y además en los clientes puede estar "cacheada" la resolución anterior. Para
purgar el "cache"
IPCONFIG /FLUSHDNS

Guillermo Delprato
MVP - MCT - MCSE
Buenos Aires, Argentina
http://w2k8-server.spaces.live.com

Este mensaje se proporciona "como está" sin garantías de ninguna clase, ni
otorga ningún derecho. Ud. asume los riesgos.
This posting is provide "as is" with no warranties and confers no rights.
You assume all risk for your use.
_____________________

"JUAN REYES" wrote in message
news:
> ahora al cambiar de direccion el servidor los host no hacen ping via el
> nombre del server, o sea el nombre aun se esta resolviendo con la
> direccion
> 192.168.1.7 parece que DC PRINCIPAL ESTA ENVIANDO AUN ESA RESOLUCION.
>
>
> "Guillermo Delprato [MS-MVP]" wrote:
>
>> Si que tengo idea :-)
>> Es la placa
>>
>>
>> Guillermo Delprato
>> MVP - MCT - MCSE
>> Buenos Aires, Argentina
>> http://w2k8-server.spaces.live.com
>>
>> Este mensaje se proporciona "como está" sin garantías de ninguna clase,
>> ni
>> otorga ningún derecho. Ud. asume los riesgos.
>> This posting is provide "as is" with no warranties and confers no rights.
>> You assume all risk for your use.
>> _____________________
>>
>>
>> "JUAN REYES" wrote in message
>> news:
>> > Caramba guillermo disculpa tantas molestias, pero este caso es
>> > fustrante,
>> > mira lo que acabo de hacer.
>> >
>> > 1.- Deshative la tarjeta que hasta el momento estaba funcionando.
>> > 2.- Active la segunda tarjeta, pero la deje DHCP.
>> > 3.- El servidor de DHCP le envio la direccion 192.168.1.47
>> > 4.- AHORA el server le da ping a todo el mundo.
>> >
>> > Todo parece indicar que es un problema que hay internamente en el
>> > server
>> > cuando este tiene la direccion 192.168.1.7
>> >
>> > Le coloque fija otra direccion 192.168.1.12 con la misma configuracion
>> > anterior, reinicie el mismo y hasta el momento no me ha dado problemas
>> > ahora
>> > esta viendo todos los HOST. Dime te surge una idea de todo esto...
>> >
>> >
>> > "Guillermo Delprato [MS-MVP]" wrote:
>> >
>> >> iSCSI no tiene nada que ver
>> >> Y no debería estar funcionando el servicio si no tienes un dispositivo
>> >> iSCSI
>> >>
>> >>
>> >> Guillermo Delprato
>> >> MVP - MCT - MCSE
>> >> Buenos Aires, Argentina
>> >> http://w2k8-server.spaces.live.com
>> >>
>> >> Este mensaje se proporciona "como está" sin garantías de ninguna
>> >> clase,
>> >> ni
>> >> otorga ningún derecho. Ud. asume los riesgos.
>> >> This posting is provide "as is" with no warranties and confers no
>> >> rights.
>> >> You assume all risk for your use.
>> >> _____________________
>> >>
>> >>
>> >> "JUAN REYES" wrote in message
>> >> news:
>> >> > Guillermo mira esto:
>> >> >
>> >> > este error aparece muchas veces en event:
>> >> >
>> >> > Event Type: Error
>> >> > Event Source: iScsiPrt
>> >> > Event Category: None
>> >> > Event ID: 1
>> >> > Date: 20/10/2008
>> >> > Time: 3:11:33 PM
>> >> > User: N/A
>> >> > Computer: OPMMFSVR02
>> >> > Description:
>> >> > Initiator failed to connect to the target. Target IP address and TCP
>> >> > Port
>> >> > number are given in dump data.
>> >> >
>> >> > For more information, see Help and Support Center at
>> >> > http://go.microsoft.com/fwlink/events.asp.
>> >> > Data:
>> >> > 0000: 00 00 06 00 01 00 62 00 ..b.
>> >> > 0008: 00 00 00 00 01 00 00 c0 ...À
>> >> > 0010: 00 00 00 00 00 00 00 00
>> >> > 0018: 00 00 00 00 00 00 00 00
>> >> > 0020: 00 00 00 00 00 00 00 00
>> >> > 0028: bc 0c c0 a8 01 0a ¼.À¨..
>> >> >
>> >> > OJO OJO OJO OJO
>> >> > Y ESTOS APARECEN luego de conectar la segunda tarjeta en otro
>> >> > switch
>> >> >
>> >> > Event Type: Information
>> >> > Event Source: iScsiPrt
>> >> > Event Category: None
>> >> > Event ID: 34
>> >> > Date: 20/10/2008
>> >> > Time: 3:11:58 PM
>> >> > User: N/A
>> >> > Computer: OPMMFSVR02
>> >> > Description:
>> >> > A connection to the target was lost, but Initiator successfully
>> >> > reconnected
>> >> > to the target. Dump data contains the target name.
>> >> >
>> >> > For more information, see Help and Support Center at
>> >> > http://go.microsoft.com/fwlink/events.asp.
>> >> > Data:
>> >> > 0000: 00 00 68 00 01 00 c2 00 ..h...Â.
>> >> > 0008: 00 00 00 00 22 00 00 40 "..@
>> >> > 0010: 00 00 00 00 00 00 00 00
>> >> > 0018: 00 00 00 00 00 00 00 00
>> >> > 0020: 00 00 00 00 00 00 00 00
>> >> > 0028: 69 00 71 00 6e 00 2e 00 i.q.n...
>> >> > 0030: 31 00 39 00 38 00 36 00 1.9.8.6.
>> >> > 0038: 2d 00 30 00 33 00 2e 00 -.0.3...
>> >> > 0040: 63 00 6f 00 6d 00 2e 00 c.o.m...
>> >> > 0048: 68 00 70 00 3a 00 73 00 h.p.:.s.
>> >> > 0050: 74 00 6f 00 72 00 61 00 t.o.r.a.
>> >> > 0058: 67 00 65 00 2e 00 64 00 g.e...d.
>> >> > 0060: 32 00 64 00 62 00 73 00 2.d.b.s.
>> >> > 0068: 2e 00 68 00 75 00 31 00 ..h.u.1.
>> >> > 0070: 37 00 30 00 38 00 30 00 7.0.8.0.
>> >> > 0078: 77 00 6d 00 30 00 2e 00 w.m.0...
>> >> > 0080: 35 00 30 00 30 00 31 00 5.0.0.1.
>> >> > 0088: 31 00 30 00 61 00 30 00 1.0.a.0.
>> >> >
>> >> > Event Type: Information
>> >> > Event Source: l2nd
>> >> > Event Category: None
>> >> > Event ID: 16
>> >> > Date: 20/10/2008
>> >> > Time: 3:13:54 PM
>> >> > User: N/A
>> >> > Computer: OPMMFSVR02
>> >> > Description:
>> >> > HP NC373i: Driver initialized successfully.
>> >> > Data:
>> >> > 0000: 00 00 00 00 02 00 4e 00 ..N.
>> >> > 0008: 00 00 00 00 10 00 05 40 ...@
>> >> > 0010: 00 00 00 00 00 00 00 00
>> >> > 0018: 00 00 00 00 00 00 00 00
>> >> > 0020: 00 00 00 00 00 00 00 00
>> >> >
>> >> > Event Type: Information
>> >> > Event Source: W32Time
>> >> > Event Category: None
>> >> > Event ID: 37
>> >> > Date: 20/10/2008
>> >> > Time: 3:15:01 PM
>> >> > User: N/A
>> >> > Computer: OPMMFSVR02
>> >> > Description:
>> >> > The time provider NtpClient is currently receiving valid time data
>> >> > from
>> >> > opmmfsvr01.MMFDOMAIN (ntp.d|192.168.1.7:123->192.168.1.5:123).
>> >> >
>> >> > For more information, see Help and Support Center at
>> >> > http://go.microsoft.com/fwlink/events.asp.
>> >> >
>> >> > Event Type: Warning
>> >> > Event Source: Dhcp
>> >> > Event Category: None
>> >> > Event ID: 1007
>> >> > Date: 20/10/2008
>> >> > Time: 3:15:06 PM
>> >> > User: N/A
>> >> > Computer: OPMMFSVR02
>> >> > Description:
>> >> > Your computer has automatically configured the IP address for the
>> >> > Network
>> >> > Card with network address 001B7842EAEC. The IP address being used
>> >> > is
>> >> > 169.254.253.131.
>> >> >
>> >> > For more information, see Help and Support Center at
>> >> > http://go.microsoft.com/fwlink/events.asp.
>> >> > Data:
>> >> > 0000: 00 00 00 00
>> >> >
>> >> > Event Type: Information
>> >> > Event Source: BROWSER
>> >> > Event Category: None
>> >> > Event ID: 8015
>> >> > Date: 20/10/2008
>> >> > Time: 3:15:07 PM
>> >> > User: N/A
>> >> > Computer: OPMMFSVR02
>> >> > Description:
>> >> > The browser has forced an election on network
>> >> > \Device\NetBT_Tcpip_{BBD4F63D-1FEA-4F49-8E29-8F2E48F5EED0} because a
>> >> > Windows
>> >> > Server (or domain master) browser is started.
>> >> >
>> >> > For more information, see Help and Support Center at
>> >> > http://go.microsoft.com/fwlink/events.asp.
>> >> >
>> >> > Event Type: Warning
>> >> > Event Source: Server
>> >> > Event Category: None
>> >> > Event ID: 2504
>> >> > Date: 20/10/2008
>> >> > Time: 3:15:10 PM
>> >> > User: N/A
>> >> > Computer: OPMMFSVR02
>> >> > Description:
>> >> > The server could not bind to the transport
>> >> > \Device\NetBT_Tcpip_{BBD4F63D-1FEA-4F49-8E29-8F2E48F5EED0}.
>> >> >
>> >> > For more information, see Help and Support Center at
>> >> > http://go.microsoft.com/fwlink/events.asp.
>> >> > Data:
>> >> > 0000: aa 05 00 00 ª...
>> >> >
>> >> > Event Type: Information
>> >> > Event Source: BROWSER
>> >> > Event Category: None
>> >> > Event ID: 8015
>> >> > Date: 20/10/2008
>> >> > Time: 3:15:11 PM
>> >> > User: N/A
>> >> > Computer: OPMMFSVR02
>> >> > Description:
>> >> > The browser has forced an election on network
>> >> > \Device\NetBT_Tcpip_{BBD4F63D-1FEA-4F49-8E29-8F2E48F5EED0} because a
>> >> > Windows
>> >> > Server (or domain master) browser is started.
>> >> >
>> >> > For more information, see Help and Support Center at
>> >> > http://go.microsoft.com/fwlink/events.asp.
>> >> >
>> >> >
>> >> > "Guillermo Delprato [MS-MVP]" wrote:
>> >> >
>> >> >> Si ping entre servidores funciona, el problema está entre ese
>> >> >> servidor
>> >> >> específico y el switch
>> >> >> Cambia Placa/Cable/Switch hasta encontrar "al culpable" :-)
>> >> >>
>> >> >>
>> >> >> Guillermo Delprato
>> >> >> MVP - MCT - MCSE
>> >> >> Buenos Aires, Argentina
>> >> >> http://w2k8-server.spaces.live.com
>> >> >>
>> >> >> Este mensaje se proporciona "como está" sin garantías de ninguna
>> >> >> clase,
>> >> >> ni
>> >> >> otorga ningún derecho. Ud. asume los riesgos.
>> >> >> This posting is provide "as is" with no warranties and confers no
>> >> >> rights.
>> >> >> You assume all risk for your use.
>> >> >> _____________________
>> >> >>
>> >> >>
>> >> >> "JUAN REYES" wrote in message
>> >> >> news:
>> >> >> > Mira esto es un ping al switch donde el esta conectado:
>> >> >> >
>> >> >> > Pinging 192.168.1.18 with 32 bytes of data:

Responder a este mensaje

#17 JUAN REYES

21/10/2008 - 14:37 | Informe spam

una nueva guillermo.

Mira lo que he tenido que hacer. Al servidor cambiar la dirección
definitivamente a la 192.168.1.12 y hasta ahora esta funcionando, no aseguro
que no vuelva a lo mismo porque no he podido determinar que demonios pasa.

Para seguir tratando de averiguar que pasa, la dirección 192.168.1.7 se la
puse a mi laptop y reacciona igual de mal que el servidor , algo pasa con
esta dirección es como si alguien la tenga asiganada pero ese alguien no
responde a un ping o telnet, nada. O si esta bloqueda por alguien. De verda
que esto es estraño

"Guillermo Delprato [MS-MVP]" wrote:

Luego de cambiar la dirección IP, hay que hacer:
IPCONFIG /REGISTERDNS

Y si es controlador de dominio, además
NET STOP NETLOGON

NET START NETLOGON

Y además en los clientes puede estar "cacheada" la resolución anterior. Para
purgar el "cache"
IPCONFIG /FLUSHDNS

Guillermo Delprato
MVP - MCT - MCSE
Buenos Aires, Argentina
http://w2k8-server.spaces.live.com

Este mensaje se proporciona "como está" sin garantías de ninguna clase, ni
otorga ningún derecho. Ud. asume los riesgos.
This posting is provide "as is" with no warranties and confers no rights.
You assume all risk for your use.
_____________________

"JUAN REYES" wrote in message
news:
> ahora al cambiar de direccion el servidor los host no hacen ping via el
> nombre del server, o sea el nombre aun se esta resolviendo con la
> direccion
> 192.168.1.7 parece que DC PRINCIPAL ESTA ENVIANDO AUN ESA RESOLUCION.
>
>
> "Guillermo Delprato [MS-MVP]" wrote:
>
>> Si que tengo idea :-)
>> Es la placa
>>
>>
>> Guillermo Delprato
>> MVP - MCT - MCSE
>> Buenos Aires, Argentina
>> http://w2k8-server.spaces.live.com
>>
>> Este mensaje se proporciona "como está" sin garantías de ninguna clase,
>> ni
>> otorga ningún derecho. Ud. asume los riesgos.
>> This posting is provide "as is" with no warranties and confers no rights.
>> You assume all risk for your use.
>> _____________________
>>
>>
>> "JUAN REYES" wrote in message
>> news:
>> > Caramba guillermo disculpa tantas molestias, pero este caso es
>> > fustrante,
>> > mira lo que acabo de hacer.
>> >
>> > 1.- Deshative la tarjeta que hasta el momento estaba funcionando.
>> > 2.- Active la segunda tarjeta, pero la deje DHCP.
>> > 3.- El servidor de DHCP le envio la direccion 192.168.1.47
>> > 4.- AHORA el server le da ping a todo el mundo.
>> >
>> > Todo parece indicar que es un problema que hay internamente en el
>> > server
>> > cuando este tiene la direccion 192.168.1.7
>> >
>> > Le coloque fija otra direccion 192.168.1.12 con la misma configuracion
>> > anterior, reinicie el mismo y hasta el momento no me ha dado problemas
>> > ahora
>> > esta viendo todos los HOST. Dime te surge una idea de todo esto...
>> >
>> >
>> > "Guillermo Delprato [MS-MVP]" wrote:
>> >
>> >> iSCSI no tiene nada que ver
>> >> Y no debería estar funcionando el servicio si no tienes un dispositivo
>> >> iSCSI
>> >>
>> >>
>> >> Guillermo Delprato
>> >> MVP - MCT - MCSE
>> >> Buenos Aires, Argentina
>> >> http://w2k8-server.spaces.live.com
>> >>
>> >> Este mensaje se proporciona "como está" sin garantías de ninguna
>> >> clase,
>> >> ni
>> >> otorga ningún derecho. Ud. asume los riesgos.
>> >> This posting is provide "as is" with no warranties and confers no
>> >> rights.
>> >> You assume all risk for your use.
>> >> _____________________
>> >>
>> >>
>> >> "JUAN REYES" wrote in message
>> >> news:
>> >> > Guillermo mira esto:
>> >> >
>> >> > este error aparece muchas veces en event:
>> >> >
>> >> > Event Type: Error
>> >> > Event Source: iScsiPrt
>> >> > Event Category: None
>> >> > Event ID: 1
>> >> > Date: 20/10/2008
>> >> > Time: 3:11:33 PM
>> >> > User: N/A
>> >> > Computer: OPMMFSVR02
>> >> > Description:
>> >> > Initiator failed to connect to the target. Target IP address and TCP
>> >> > Port
>> >> > number are given in dump data.
>> >> >
>> >> > For more information, see Help and Support Center at
>> >> > http://go.microsoft.com/fwlink/events.asp.
>> >> > Data:
>> >> > 0000: 00 00 06 00 01 00 62 00 ..b.
>> >> > 0008: 00 00 00 00 01 00 00 c0 ...À
>> >> > 0010: 00 00 00 00 00 00 00 00
>> >> > 0018: 00 00 00 00 00 00 00 00
>> >> > 0020: 00 00 00 00 00 00 00 00
>> >> > 0028: bc 0c c0 a8 01 0a ¼.À¨..
>> >> >
>> >> > OJO OJO OJO OJO
>> >> > Y ESTOS APARECEN luego de conectar la segunda tarjeta en otro
>> >> > switch
>> >> >
>> >> > Event Type: Information
>> >> > Event Source: iScsiPrt
>> >> > Event Category: None
>> >> > Event ID: 34
>> >> > Date: 20/10/2008
>> >> > Time: 3:11:58 PM
>> >> > User: N/A
>> >> > Computer: OPMMFSVR02
>> >> > Description:
>> >> > A connection to the target was lost, but Initiator successfully
>> >> > reconnected
>> >> > to the target. Dump data contains the target name.
>> >> >
>> >> > For more information, see Help and Support Center at
>> >> > http://go.microsoft.com/fwlink/events.asp.
>> >> > Data:
>> >> > 0000: 00 00 68 00 01 00 c2 00 ..h...Â.
>> >> > 0008: 00 00 00 00 22 00 00 40 "..@
>> >> > 0010: 00 00 00 00 00 00 00 00
>> >> > 0018: 00 00 00 00 00 00 00 00
>> >> > 0020: 00 00 00 00 00 00 00 00
>> >> > 0028: 69 00 71 00 6e 00 2e 00 i.q.n...
>> >> > 0030: 31 00 39 00 38 00 36 00 1.9.8.6.
>> >> > 0038: 2d 00 30 00 33 00 2e 00 -.0.3...
>> >> > 0040: 63 00 6f 00 6d 00 2e 00 c.o.m...
>> >> > 0048: 68 00 70 00 3a 00 73 00 h.p.:.s.
>> >> > 0050: 74 00 6f 00 72 00 61 00 t.o.r.a.
>> >> > 0058: 67 00 65 00 2e 00 64 00 g.e...d.
>> >> > 0060: 32 00 64 00 62 00 73 00 2.d.b.s.
>> >> > 0068: 2e 00 68 00 75 00 31 00 ..h.u.1.
>> >> > 0070: 37 00 30 00 38 00 30 00 7.0.8.0.
>> >> > 0078: 77 00 6d 00 30 00 2e 00 w.m.0...
>> >> > 0080: 35 00 30 00 30 00 31 00 5.0.0.1.
>> >> > 0088: 31 00 30 00 61 00 30 00 1.0.a.0.
>> >> >
>> >> > Event Type: Information
>> >> > Event Source: l2nd
>> >> > Event Category: None
>> >> > Event ID: 16
>> >> > Date: 20/10/2008
>> >> > Time: 3:13:54 PM
>> >> > User: N/A
>> >> > Computer: OPMMFSVR02
>> >> > Description:
>> >> > HP NC373i: Driver initialized successfully.
>> >> > Data:
>> >> > 0000: 00 00 00 00 02 00 4e 00 ..N.
>> >> > 0008: 00 00 00 00 10 00 05 40 ...@
>> >> > 0010: 00 00 00 00 00 00 00 00
>> >> > 0018: 00 00 00 00 00 00 00 00
>> >> > 0020: 00 00 00 00 00 00 00 00
>> >> >
>> >> > Event Type: Information
>> >> > Event Source: W32Time
>> >> > Event Category: None
>> >> > Event ID: 37
>> >> > Date: 20/10/2008
>> >> > Time: 3:15:01 PM
>> >> > User: N/A
>> >> > Computer: OPMMFSVR02
>> >> > Description:
>> >> > The time provider NtpClient is currently receiving valid time data
>> >> > from
>> >> > opmmfsvr01.MMFDOMAIN (ntp.d|192.168.1.7:123->192.168.1.5:123).
>> >> >
>> >> > For more information, see Help and Support Center at
>> >> > http://go.microsoft.com/fwlink/events.asp.
>> >> >
>> >> > Event Type: Warning
>> >> > Event Source: Dhcp
>> >> > Event Category: None
>> >> > Event ID: 1007
>> >> > Date: 20/10/2008
>> >> > Time: 3:15:06 PM
>> >> > User: N/A
>> >> > Computer: OPMMFSVR02
>> >> > Description:
>> >> > Your computer has automatically configured the IP address for the
>> >> > Network
>> >> > Card with network address 001B7842EAEC. The IP address being used
>> >> > is
>> >> > 169.254.253.131.
>> >> >
>> >> > For more information, see Help and Support Center at
>> >> > http://go.microsoft.com/fwlink/events.asp.
>> >> > Data:
>> >> > 0000: 00 00 00 00
>> >> >
>> >> > Event Type: Information
>> >> > Event Source: BROWSER
>> >> > Event Category: None
>> >> > Event ID: 8015
>> >> > Date: 20/10/2008
>> >> > Time: 3:15:07 PM
>> >> > User: N/A
>> >> > Computer: OPMMFSVR02
>> >> > Description:
>> >> > The browser has forced an election on network
>> >> > \Device\NetBT_Tcpip_{BBD4F63D-1FEA-4F49-8E29-8F2E48F5EED0} because a
>> >> > Windows
>> >> > Server (or domain master) browser is started.
>> >> >
>> >> > For more information, see Help and Support Center at
>> >> > http://go.microsoft.com/fwlink/events.asp.
>> >> >
>> >> > Event Type: Warning
>> >> > Event Source: Server
>> >> > Event Category: None
>> >> > Event ID: 2504
>> >> > Date: 20/10/2008
>> >> > Time: 3:15:10 PM
>> >> > User: N/A
>> >> > Computer: OPMMFSVR02
>> >> > Description:
>> >> > The server could not bind to the transport
>> >> > \Device\NetBT_Tcpip_{BBD4F63D-1FEA-4F49-8E29-8F2E48F5EED0}.
>> >> >
>> >> > For more information, see Help and Support Center at
>> >> > http://go.microsoft.com/fwlink/events.asp.
>> >> > Data:
>> >> > 0000: aa 05 00 00 ª...
>> >> >
>> >> > Event Type: Information
>> >> > Event Source: BROWSER
>> >> > Event Category: None
>> >> > Event ID: 8015
>> >> > Date: 20/10/2008
>> >> > Time: 3:15:11 PM
>> >> > User: N/A
>> >> > Computer: OPMMFSVR02
>> >> > Description:
>> >> > The browser has forced an election on network
>> >> > \Device\NetBT_Tcpip_{BBD4F63D-1FEA-4F49-8E29-8F2E48F5EED0} because a
>> >> > Windows
>> >> > Server (or domain master) browser is started.
>> >> >
>> >> > For more information, see Help and Support Center at
>> >> > http://go.microsoft.com/fwlink/events.asp.
>> >> >
>> >> >
>> >> > "Guillermo Delprato [MS-MVP]" wrote:
>> >> >
>> >> >> Si ping entre servidores funciona, el problema está entre ese
>> >> >> servidor
>> >> >> específico y el switch
>> >> >> Cambia Placa/Cable/Switch hasta encontrar "al culpable" :-)
>> >> >>
>> >> >>
>> >> >> Guillermo Delprato
>> >> >> MVP - MCT - MCSE
>> >> >> Buenos Aires, Argentina
>> >> >> http://w2k8-server.spaces.live.com
>> >> >>
>> >> >> Este mensaje se proporciona "como está" sin garantías de ninguna
>> >> >> clase,
>> >> >> ni
>> >> >> otorga ningún derecho. Ud. asume los riesgos.
>> >> >> This posting is provide "as is" with no warranties and confers no
>> >> >> rights.
>> >> >> You assume all risk for your use.
>> >> >> _____________________
>> >> >>
>> >> >>
>> >> >> "JUAN REYES" wrote in message
>> >> >> news:
>> >> >> > Mira esto es un ping al switch donde el esta conectado:
>> >> >> >
>> >> >> > Pinging 192.168.1.18 with 32 bytes of data:

Responder a este mensaje

#18 Guillermo Delprato [MS-MVP]

21/10/2008 - 16:10 | Informe spam

Seguramente está ya ocupada en algún equipo, que si tiene el cortafuegos
levantado no responde.

Prueba esto
PING 192.168.1.7
Y luego
ARP -a

De esa forma puedes ver las Direcciones MAC que tengas en "cache". Revisa si
hay alguna que corresponda a la IP en cuestión

Guillermo Delprato
MVP - MCT - MCSE
Buenos Aires, Argentina
http://w2k8-server.spaces.live.com

Este mensaje se proporciona "como está" sin garantías de ninguna clase, ni
otorga ningún derecho. Ud. asume los riesgos.
This posting is provide "as is" with no warranties and confers no rights.
You assume all risk for your use.
_____________________

"JUAN REYES" wrote in message
news:

una nueva guillermo.

Mira lo que he tenido que hacer. Al servidor cambiar la dirección
definitivamente a la 192.168.1.12 y hasta ahora esta funcionando, no
aseguro
que no vuelva a lo mismo porque no he podido determinar que demonios pasa.

Para seguir tratando de averiguar que pasa, la dirección 192.168.1.7 se
la
puse a mi laptop y reacciona igual de mal que el servidor , algo pasa con
esta dirección es como si alguien la tenga asiganada pero ese alguien no
responde a un ping o telnet, nada. O si esta bloqueda por alguien. De
verda
que esto es estraño

"Guillermo Delprato [MS-MVP]" wrote:

Luego de cambiar la dirección IP, hay que hacer:
IPCONFIG /REGISTERDNS

Y si es controlador de dominio, además
NET STOP NETLOGON

NET START NETLOGON

Y además en los clientes puede estar "cacheada" la resolución anterior.
Para
purgar el "cache"
IPCONFIG /FLUSHDNS

Guillermo Delprato
MVP - MCT - MCSE
Buenos Aires, Argentina
http://w2k8-server.spaces.live.com

Este mensaje se proporciona "como está" sin garantías de ninguna clase,
ni
otorga ningún derecho. Ud. asume los riesgos.
This posting is provide "as is" with no warranties and confers no rights.
You assume all risk for your use.
_____________________

"JUAN REYES" wrote in message
news:
> ahora al cambiar de direccion el servidor los host no hacen ping via el
> nombre del server, o sea el nombre aun se esta resolviendo con la
> direccion
> 192.168.1.7 parece que DC PRINCIPAL ESTA ENVIANDO AUN ESA RESOLUCION.
>
>
> "Guillermo Delprato [MS-MVP]" wrote:
>
>> Si que tengo idea :-)
>> Es la placa
>>
>>
>> Guillermo Delprato
>> MVP - MCT - MCSE
>> Buenos Aires, Argentina
>> http://w2k8-server.spaces.live.com
>>
>> Este mensaje se proporciona "como está" sin garantías de ninguna
>> clase,
>> ni
>> otorga ningún derecho. Ud. asume los riesgos.
>> This posting is provide "as is" with no warranties and confers no
>> rights.
>> You assume all risk for your use.
>> _____________________
>>
>>
>> "JUAN REYES" wrote in message
>> news:
>> > Caramba guillermo disculpa tantas molestias, pero este caso es
>> > fustrante,
>> > mira lo que acabo de hacer.
>> >
>> > 1.- Deshative la tarjeta que hasta el momento estaba funcionando.
>> > 2.- Active la segunda tarjeta, pero la deje DHCP.
>> > 3.- El servidor de DHCP le envio la direccion 192.168.1.47
>> > 4.- AHORA el server le da ping a todo el mundo.
>> >
>> > Todo parece indicar que es un problema que hay internamente en el
>> > server
>> > cuando este tiene la direccion 192.168.1.7
>> >
>> > Le coloque fija otra direccion 192.168.1.12 con la misma
>> > configuracion
>> > anterior, reinicie el mismo y hasta el momento no me ha dado
>> > problemas
>> > ahora
>> > esta viendo todos los HOST. Dime te surge una idea de todo esto...
>> >
>> >
>> > "Guillermo Delprato [MS-MVP]" wrote:
>> >
>> >> iSCSI no tiene nada que ver
>> >> Y no debería estar funcionando el servicio si no tienes un
>> >> dispositivo
>> >> iSCSI
>> >>
>> >>
>> >> Guillermo Delprato
>> >> MVP - MCT - MCSE
>> >> Buenos Aires, Argentina
>> >> http://w2k8-server.spaces.live.com
>> >>
>> >> Este mensaje se proporciona "como está" sin garantías de ninguna
>> >> clase,
>> >> ni
>> >> otorga ningún derecho. Ud. asume los riesgos.
>> >> This posting is provide "as is" with no warranties and confers no
>> >> rights.
>> >> You assume all risk for your use.
>> >> _____________________
>> >>
>> >>
>> >> "JUAN REYES" wrote in message
>> >> news:
>> >> > Guillermo mira esto:
>> >> >
>> >> > este error aparece muchas veces en event:
>> >> >
>> >> > Event Type: Error
>> >> > Event Source: iScsiPrt
>> >> > Event Category: None
>> >> > Event ID: 1
>> >> > Date: 20/10/2008
>> >> > Time: 3:11:33 PM
>> >> > User: N/A
>> >> > Computer: OPMMFSVR02
>> >> > Description:
>> >> > Initiator failed to connect to the target. Target IP address and
>> >> > TCP
>> >> > Port
>> >> > number are given in dump data.
>> >> >
>> >> > For more information, see Help and Support Center at
>> >> > http://go.microsoft.com/fwlink/events.asp.
>> >> > Data:
>> >> > 0000: 00 00 06 00 01 00 62 00 ..b.
>> >> > 0008: 00 00 00 00 01 00 00 c0 ...À
>> >> > 0010: 00 00 00 00 00 00 00 00
>> >> > 0018: 00 00 00 00 00 00 00 00
>> >> > 0020: 00 00 00 00 00 00 00 00
>> >> > 0028: bc 0c c0 a8 01 0a ¼.À¨..
>> >> >
>> >> > OJO OJO OJO OJO
>> >> > Y ESTOS APARECEN luego de conectar la segunda tarjeta en otro
>> >> > switch
>> >> >
>> >> > Event Type: Information
>> >> > Event Source: iScsiPrt
>> >> > Event Category: None
>> >> > Event ID: 34
>> >> > Date: 20/10/2008
>> >> > Time: 3:11:58 PM
>> >> > User: N/A
>> >> > Computer: OPMMFSVR02
>> >> > Description:
>> >> > A connection to the target was lost, but Initiator successfully
>> >> > reconnected
>> >> > to the target. Dump data contains the target name.
>> >> >
>> >> > For more information, see Help and Support Center at
>> >> > http://go.microsoft.com/fwlink/events.asp.
>> >> > Data:
>> >> > 0000: 00 00 68 00 01 00 c2 00 ..h...Â.
>> >> > 0008: 00 00 00 00 22 00 00 40 "..@
>> >> > 0010: 00 00 00 00 00 00 00 00
>> >> > 0018: 00 00 00 00 00 00 00 00
>> >> > 0020: 00 00 00 00 00 00 00 00
>> >> > 0028: 69 00 71 00 6e 00 2e 00 i.q.n...
>> >> > 0030: 31 00 39 00 38 00 36 00 1.9.8.6.
>> >> > 0038: 2d 00 30 00 33 00 2e 00 -.0.3...
>> >> > 0040: 63 00 6f 00 6d 00 2e 00 c.o.m...
>> >> > 0048: 68 00 70 00 3a 00 73 00 h.p.:.s.
>> >> > 0050: 74 00 6f 00 72 00 61 00 t.o.r.a.
>> >> > 0058: 67 00 65 00 2e 00 64 00 g.e...d.
>> >> > 0060: 32 00 64 00 62 00 73 00 2.d.b.s.
>> >> > 0068: 2e 00 68 00 75 00 31 00 ..h.u.1.
>> >> > 0070: 37 00 30 00 38 00 30 00 7.0.8.0.
>> >> > 0078: 77 00 6d 00 30 00 2e 00 w.m.0...
>> >> > 0080: 35 00 30 00 30 00 31 00 5.0.0.1.
>> >> > 0088: 31 00 30 00 61 00 30 00 1.0.a.0.
>> >> >
>> >> > Event Type: Information
>> >> > Event Source: l2nd
>> >> > Event Category: None
>> >> > Event ID: 16
>> >> > Date: 20/10/2008
>> >> > Time: 3:13:54 PM
>> >> > User: N/A
>> >> > Computer: OPMMFSVR02
>> >> > Description:
>> >> > HP NC373i: Driver initialized successfully.
>> >> > Data:
>> >> > 0000: 00 00 00 00 02 00 4e 00 ..N.
>> >> > 0008: 00 00 00 00 10 00 05 40 ...@
>> >> > 0010: 00 00 00 00 00 00 00 00
>> >> > 0018: 00 00 00 00 00 00 00 00
>> >> > 0020: 00 00 00 00 00 00 00 00
>> >> >
>> >> > Event Type: Information
>> >> > Event Source: W32Time
>> >> > Event Category: None
>> >> > Event ID: 37
>> >> > Date: 20/10/2008
>> >> > Time: 3:15:01 PM
>> >> > User: N/A
>> >> > Computer: OPMMFSVR02
>> >> > Description:
>> >> > The time provider NtpClient is currently receiving valid time
>> >> > data
>> >> > from
>> >> > opmmfsvr01.MMFDOMAIN (ntp.d|192.168.1.7:123->192.168.1.5:123).
>> >> >
>> >> > For more information, see Help and Support Center at
>> >> > http://go.microsoft.com/fwlink/events.asp.
>> >> >
>> >> > Event Type: Warning
>> >> > Event Source: Dhcp
>> >> > Event Category: None
>> >> > Event ID: 1007
>> >> > Date: 20/10/2008
>> >> > Time: 3:15:06 PM
>> >> > User: N/A
>> >> > Computer: OPMMFSVR02
>> >> > Description:
>> >> > Your computer has automatically configured the IP address for the
>> >> > Network
>> >> > Card with network address 001B7842EAEC. The IP address being
>> >> > used
>> >> > is
>> >> > 169.254.253.131.
>> >> >
>> >> > For more information, see Help and Support Center at
>> >> > http://go.microsoft.com/fwlink/events.asp.
>> >> > Data:
>> >> > 0000: 00 00 00 00
>> >> >
>> >> > Event Type: Information
>> >> > Event Source: BROWSER
>> >> > Event Category: None
>> >> > Event ID: 8015
>> >> > Date: 20/10/2008
>> >> > Time: 3:15:07 PM
>> >> > User: N/A
>> >> > Computer: OPMMFSVR02
>> >> > Description:
>> >> > The browser has forced an election on network
>> >> > \Device\NetBT_Tcpip_{BBD4F63D-1FEA-4F49-8E29-8F2E48F5EED0}
>> >> > because a
>> >> > Windows
>> >> > Server (or domain master) browser is started.
>> >> >
>> >> > For more information, see Help and Support Center at
>> >> > http://go.microsoft.com/fwlink/events.asp.
>> >> >
>> >> > Event Type: Warning
>> >> > Event Source: Server
>> >> > Event Category: None
>> >> > Event ID: 2504
>> >> > Date: 20/10/2008
>> >> > Time: 3:15:10 PM
>> >> > User: N/A
>> >> > Computer: OPMMFSVR02
>> >> > Description:
>> >> > The server could not bind to the transport
>> >> > \Device\NetBT_Tcpip_{BBD4F63D-1FEA-4F49-8E29-8F2E48F5EED0}.
>> >> >
>> >> > For more information, see Help and Support Center at
>> >> > http://go.microsoft.com/fwlink/events.asp.
>> >> > Data:
>> >> > 0000: aa 05 00 00 ª...
>> >> >
>> >> > Event Type: Information
>> >> > Event Source: BROWSER
>> >> > Event Category: None
>> >> > Event ID: 8015
>> >> > Date: 20/10/2008
>> >> > Time: 3:15:11 PM
>> >> > User: N/A
>> >> > Computer: OPMMFSVR02
>> >> > Description:
>> >> > The browser has forced an election on network
>> >> > \Device\NetBT_Tcpip_{BBD4F63D-1FEA-4F49-8E29-8F2E48F5EED0}
>> >> > because a
>> >> > Windows
>> >> > Server (or domain master) browser is started.
>> >> >
>> >> > For more information, see Help and Support Center at
>> >> > http://go.microsoft.com/fwlink/events.asp.
>> >> >
>> >> >
>> >> > "Guillermo Delprato [MS-MVP]" wrote:
>> >> >
>> >> >> Si ping entre servidores funciona, el problema está entre ese
>> >> >> servidor
>> >> >> específico y el switch
>> >> >> Cambia Placa/Cable/Switch hasta encontrar "al culpable" :-)
>> >> >>
>> >> >>
>> >> >> Guillermo Delprato
>> >> >> MVP - MCT - MCSE
>> >> >> Buenos Aires, Argentina
>> >> >> http://w2k8-server.spaces.live.com
>> >> >>
>> >> >> Este mensaje se proporciona "como está" sin garantías de ninguna
>> >> >> clase,
>> >> >> ni
>> >> >> otorga ningún derecho. Ud. asume los riesgos.
>> >> >> This posting is provide "as is" with no warranties and confers
>> >> >> no
>> >> >> rights.
>> >> >> You assume all risk for your use.
>> >> >> _____________________
>> >> >>
>> >> >>
>> >> >> "JUAN REYES" wrote in
>> >> >> message
>> >> >> news:
>> >> >> > Mira esto es un ping al switch donde el esta conectado:
>> >> >> >
>> >> >> > Pinging 192.168.1.18 with 32 bytes of data:

Responder a este mensaje

#19 Guillermo Delprato [MS-MVP]

21/10/2008 - 16:10 | Informe spam

Estaré por acá :-)
En el grupo somos varios que contestamos

Guillermo Delprato
MVP - MCT - MCSE
Buenos Aires, Argentina
http://w2k8-server.spaces.live.com

Este mensaje se proporciona "como está" sin garantías de ninguna clase, ni
otorga ningún derecho. Ud. asume los riesgos.
This posting is provide "as is" with no warranties and confers no rights.
You assume all risk for your use.
_____________________

"JUAN REYES" wrote in message
news:

Guillermos muchisimas gracias por toda la ayuda prestada. Te informo que
el
cambio de direccion de la 192.168.1.7 a la 192.168.1.12 ha dado resultado.
Lo
que temo es que al no saber con claridad que demonios pasa esto podria
repetirse.

Con relacion a la parte de hardware, aun crees que es un problema fisico
del
servidor, la tarjetas estan respondiendo bien, hasta ahora.

SI TIENES MAS INFORMACION SOBRE ESTE CASO EN PARTICULAR POR FAVOR ENVIAR A
MI CORREO

MUCHAS GRACIAS, CUALQUIER COSA PUEDO CONTACTARTE DE NUEVO????

"Guillermo Delprato [MS-MVP]" wrote:

Luego de cambiar la dirección IP, hay que hacer:
IPCONFIG /REGISTERDNS

Y si es controlador de dominio, además
NET STOP NETLOGON

NET START NETLOGON

Y además en los clientes puede estar "cacheada" la resolución anterior.
Para
purgar el "cache"
IPCONFIG /FLUSHDNS

Guillermo Delprato
MVP - MCT - MCSE
Buenos Aires, Argentina
http://w2k8-server.spaces.live.com

Este mensaje se proporciona "como está" sin garantías de ninguna clase,
ni
otorga ningún derecho. Ud. asume los riesgos.
This posting is provide "as is" with no warranties and confers no rights.
You assume all risk for your use.
_____________________

"JUAN REYES" wrote in message
news:
> ahora al cambiar de direccion el servidor los host no hacen ping via el
> nombre del server, o sea el nombre aun se esta resolviendo con la
> direccion
> 192.168.1.7 parece que DC PRINCIPAL ESTA ENVIANDO AUN ESA RESOLUCION.
>
>
> "Guillermo Delprato [MS-MVP]" wrote:
>
>> Si que tengo idea :-)
>> Es la placa
>>
>>
>> Guillermo Delprato
>> MVP - MCT - MCSE
>> Buenos Aires, Argentina
>> http://w2k8-server.spaces.live.com
>>
>> Este mensaje se proporciona "como está" sin garantías de ninguna
>> clase,
>> ni
>> otorga ningún derecho. Ud. asume los riesgos.
>> This posting is provide "as is" with no warranties and confers no
>> rights.
>> You assume all risk for your use.
>> _____________________
>>
>>
>> "JUAN REYES" wrote in message
>> news:
>> > Caramba guillermo disculpa tantas molestias, pero este caso es
>> > fustrante,
>> > mira lo que acabo de hacer.
>> >
>> > 1.- Deshative la tarjeta que hasta el momento estaba funcionando.
>> > 2.- Active la segunda tarjeta, pero la deje DHCP.
>> > 3.- El servidor de DHCP le envio la direccion 192.168.1.47
>> > 4.- AHORA el server le da ping a todo el mundo.
>> >
>> > Todo parece indicar que es un problema que hay internamente en el
>> > server
>> > cuando este tiene la direccion 192.168.1.7
>> >
>> > Le coloque fija otra direccion 192.168.1.12 con la misma
>> > configuracion
>> > anterior, reinicie el mismo y hasta el momento no me ha dado
>> > problemas
>> > ahora
>> > esta viendo todos los HOST. Dime te surge una idea de todo esto...
>> >
>> >
>> > "Guillermo Delprato [MS-MVP]" wrote:
>> >
>> >> iSCSI no tiene nada que ver
>> >> Y no debería estar funcionando el servicio si no tienes un
>> >> dispositivo
>> >> iSCSI
>> >>
>> >>
>> >> Guillermo Delprato
>> >> MVP - MCT - MCSE
>> >> Buenos Aires, Argentina
>> >> http://w2k8-server.spaces.live.com
>> >>
>> >> Este mensaje se proporciona "como está" sin garantías de ninguna
>> >> clase,
>> >> ni
>> >> otorga ningún derecho. Ud. asume los riesgos.
>> >> This posting is provide "as is" with no warranties and confers no
>> >> rights.
>> >> You assume all risk for your use.
>> >> _____________________
>> >>
>> >>
>> >> "JUAN REYES" wrote in message
>> >> news:
>> >> > Guillermo mira esto:
>> >> >
>> >> > este error aparece muchas veces en event:
>> >> >
>> >> > Event Type: Error
>> >> > Event Source: iScsiPrt
>> >> > Event Category: None
>> >> > Event ID: 1
>> >> > Date: 20/10/2008
>> >> > Time: 3:11:33 PM
>> >> > User: N/A
>> >> > Computer: OPMMFSVR02
>> >> > Description:
>> >> > Initiator failed to connect to the target. Target IP address and
>> >> > TCP
>> >> > Port
>> >> > number are given in dump data.
>> >> >
>> >> > For more information, see Help and Support Center at
>> >> > http://go.microsoft.com/fwlink/events.asp.
>> >> > Data:
>> >> > 0000: 00 00 06 00 01 00 62 00 ..b.
>> >> > 0008: 00 00 00 00 01 00 00 c0 ...À
>> >> > 0010: 00 00 00 00 00 00 00 00
>> >> > 0018: 00 00 00 00 00 00 00 00
>> >> > 0020: 00 00 00 00 00 00 00 00
>> >> > 0028: bc 0c c0 a8 01 0a ¼.À¨..
>> >> >
>> >> > OJO OJO OJO OJO
>> >> > Y ESTOS APARECEN luego de conectar la segunda tarjeta en otro
>> >> > switch
>> >> >
>> >> > Event Type: Information
>> >> > Event Source: iScsiPrt
>> >> > Event Category: None
>> >> > Event ID: 34
>> >> > Date: 20/10/2008
>> >> > Time: 3:11:58 PM
>> >> > User: N/A
>> >> > Computer: OPMMFSVR02
>> >> > Description:
>> >> > A connection to the target was lost, but Initiator successfully
>> >> > reconnected
>> >> > to the target. Dump data contains the target name.
>> >> >
>> >> > For more information, see Help and Support Center at
>> >> > http://go.microsoft.com/fwlink/events.asp.
>> >> > Data:
>> >> > 0000: 00 00 68 00 01 00 c2 00 ..h...Â.
>> >> > 0008: 00 00 00 00 22 00 00 40 "..@
>> >> > 0010: 00 00 00 00 00 00 00 00
>> >> > 0018: 00 00 00 00 00 00 00 00
>> >> > 0020: 00 00 00 00 00 00 00 00
>> >> > 0028: 69 00 71 00 6e 00 2e 00 i.q.n...
>> >> > 0030: 31 00 39 00 38 00 36 00 1.9.8.6.
>> >> > 0038: 2d 00 30 00 33 00 2e 00 -.0.3...
>> >> > 0040: 63 00 6f 00 6d 00 2e 00 c.o.m...
>> >> > 0048: 68 00 70 00 3a 00 73 00 h.p.:.s.
>> >> > 0050: 74 00 6f 00 72 00 61 00 t.o.r.a.
>> >> > 0058: 67 00 65 00 2e 00 64 00 g.e...d.
>> >> > 0060: 32 00 64 00 62 00 73 00 2.d.b.s.
>> >> > 0068: 2e 00 68 00 75 00 31 00 ..h.u.1.
>> >> > 0070: 37 00 30 00 38 00 30 00 7.0.8.0.
>> >> > 0078: 77 00 6d 00 30 00 2e 00 w.m.0...
>> >> > 0080: 35 00 30 00 30 00 31 00 5.0.0.1.
>> >> > 0088: 31 00 30 00 61 00 30 00 1.0.a.0.
>> >> >
>> >> > Event Type: Information
>> >> > Event Source: l2nd
>> >> > Event Category: None
>> >> > Event ID: 16
>> >> > Date: 20/10/2008
>> >> > Time: 3:13:54 PM
>> >> > User: N/A
>> >> > Computer: OPMMFSVR02
>> >> > Description:
>> >> > HP NC373i: Driver initialized successfully.
>> >> > Data:
>> >> > 0000: 00 00 00 00 02 00 4e 00 ..N.
>> >> > 0008: 00 00 00 00 10 00 05 40 ...@
>> >> > 0010: 00 00 00 00 00 00 00 00
>> >> > 0018: 00 00 00 00 00 00 00 00
>> >> > 0020: 00 00 00 00 00 00 00 00
>> >> >
>> >> > Event Type: Information
>> >> > Event Source: W32Time
>> >> > Event Category: None
>> >> > Event ID: 37
>> >> > Date: 20/10/2008
>> >> > Time: 3:15:01 PM
>> >> > User: N/A
>> >> > Computer: OPMMFSVR02
>> >> > Description:
>> >> > The time provider NtpClient is currently receiving valid time
>> >> > data
>> >> > from
>> >> > opmmfsvr01.MMFDOMAIN (ntp.d|192.168.1.7:123->192.168.1.5:123).
>> >> >
>> >> > For more information, see Help and Support Center at
>> >> > http://go.microsoft.com/fwlink/events.asp.
>> >> >
>> >> > Event Type: Warning
>> >> > Event Source: Dhcp
>> >> > Event Category: None
>> >> > Event ID: 1007
>> >> > Date: 20/10/2008
>> >> > Time: 3:15:06 PM
>> >> > User: N/A
>> >> > Computer: OPMMFSVR02
>> >> > Description:
>> >> > Your computer has automatically configured the IP address for the
>> >> > Network
>> >> > Card with network address 001B7842EAEC. The IP address being
>> >> > used
>> >> > is
>> >> > 169.254.253.131.
>> >> >
>> >> > For more information, see Help and Support Center at
>> >> > http://go.microsoft.com/fwlink/events.asp.
>> >> > Data:
>> >> > 0000: 00 00 00 00
>> >> >
>> >> > Event Type: Information
>> >> > Event Source: BROWSER
>> >> > Event Category: None
>> >> > Event ID: 8015
>> >> > Date: 20/10/2008
>> >> > Time: 3:15:07 PM
>> >> > User: N/A
>> >> > Computer: OPMMFSVR02
>> >> > Description:
>> >> > The browser has forced an election on network
>> >> > \Device\NetBT_Tcpip_{BBD4F63D-1FEA-4F49-8E29-8F2E48F5EED0}
>> >> > because a
>> >> > Windows
>> >> > Server (or domain master) browser is started.
>> >> >
>> >> > For more information, see Help and Support Center at
>> >> > http://go.microsoft.com/fwlink/events.asp.
>> >> >
>> >> > Event Type: Warning
>> >> > Event Source: Server
>> >> > Event Category: None
>> >> > Event ID: 2504
>> >> > Date: 20/10/2008
>> >> > Time: 3:15:10 PM
>> >> > User: N/A
>> >> > Computer: OPMMFSVR02
>> >> > Description:
>> >> > The server could not bind to the transport
>> >> > \Device\NetBT_Tcpip_{BBD4F63D-1FEA-4F49-8E29-8F2E48F5EED0}.
>> >> >
>> >> > For more information, see Help and Support Center at
>> >> > http://go.microsoft.com/fwlink/events.asp.
>> >> > Data:
>> >> > 0000: aa 05 00 00 ª...
>> >> >
>> >> > Event Type: Information
>> >> > Event Source: BROWSER
>> >> > Event Category: None
>> >> > Event ID: 8015
>> >> > Date: 20/10/2008
>> >> > Time: 3:15:11 PM
>> >> > User: N/A
>> >> > Computer: OPMMFSVR02
>> >> > Description:
>> >> > The browser has forced an election on network
>> >> > \Device\NetBT_Tcpip_{BBD4F63D-1FEA-4F49-8E29-8F2E48F5EED0}
>> >> > because a
>> >> > Windows
>> >> > Server (or domain master) browser is started.
>> >> >
>> >> > For more information, see Help and Support Center at
>> >> > http://go.microsoft.com/fwlink/events.asp.
>> >> >
>> >> >
>> >> > "Guillermo Delprato [MS-MVP]" wrote:
>> >> >
>> >> >> Si ping entre servidores funciona, el problema está entre ese
>> >> >> servidor
>> >> >> específico y el switch
>> >> >> Cambia Placa/Cable/Switch hasta encontrar "al culpable" :-)
>> >> >>
>> >> >>
>> >> >> Guillermo Delprato
>> >> >> MVP - MCT - MCSE
>> >> >> Buenos Aires, Argentina
>> >> >> http://w2k8-server.spaces.live.com
>> >> >>
>> >> >> Este mensaje se proporciona "como está" sin garantías de ninguna
>> >> >> clase,
>> >> >> ni
>> >> >> otorga ningún derecho. Ud. asume los riesgos.
>> >> >> This posting is provide "as is" with no warranties and confers
>> >> >> no
>> >> >> rights.
>> >> >> You assume all risk for your use.
>> >> >> _____________________
>> >> >>
>> >> >>
>> >> >> "JUAN REYES" wrote in
>> >> >> message
>> >> >> news:
>> >> >> > Mira esto es un ping al switch donde el esta conectado:
>> >> >> >
>> >> >> > Pinging 192.168.1.18 with 32 bytes of data:

Responder a este mensaje

#20 JUAN REYES

21/10/2008 - 16:59 | Informe spam

lo hice, pero no hay referencia de con esta direccion 192.168.1.7

"Guillermo Delprato [MS-MVP]" wrote:

Seguramente está ya ocupada en algún equipo, que si tiene el cortafuegos
levantado no responde.

Prueba esto
PING 192.168.1.7
Y luego
ARP -a

De esa forma puedes ver las Direcciones MAC que tengas en "cache". Revisa si
hay alguna que corresponda a la IP en cuestión

Guillermo Delprato
MVP - MCT - MCSE
Buenos Aires, Argentina
http://w2k8-server.spaces.live.com

Este mensaje se proporciona "como está" sin garantías de ninguna clase, ni
otorga ningún derecho. Ud. asume los riesgos.
This posting is provide "as is" with no warranties and confers no rights.
You assume all risk for your use.
_____________________

"JUAN REYES" wrote in message
news:
> una nueva guillermo.
>
> Mira lo que he tenido que hacer. Al servidor cambiar la dirección
> definitivamente a la 192.168.1.12 y hasta ahora esta funcionando, no
> aseguro
> que no vuelva a lo mismo porque no he podido determinar que demonios pasa.
>
> Para seguir tratando de averiguar que pasa, la dirección 192.168.1.7 se
> la
> puse a mi laptop y reacciona igual de mal que el servidor , algo pasa con
> esta dirección es como si alguien la tenga asiganada pero ese alguien no
> responde a un ping o telnet, nada. O si esta bloqueda por alguien. De
> verda
> que esto es estraño
>
>
> "Guillermo Delprato [MS-MVP]" wrote:
>
>> Luego de cambiar la dirección IP, hay que hacer:
>> IPCONFIG /REGISTERDNS
>>
>> Y si es controlador de dominio, además
>> NET STOP NETLOGON
>>
>> NET START NETLOGON
>>
>> Y además en los clientes puede estar "cacheada" la resolución anterior.
>> Para
>> purgar el "cache"
>> IPCONFIG /FLUSHDNS
>>
>>
>> Guillermo Delprato
>> MVP - MCT - MCSE
>> Buenos Aires, Argentina
>> http://w2k8-server.spaces.live.com
>>
>> Este mensaje se proporciona "como está" sin garantías de ninguna clase,
>> ni
>> otorga ningún derecho. Ud. asume los riesgos.
>> This posting is provide "as is" with no warranties and confers no rights.
>> You assume all risk for your use.
>> _____________________
>>
>>
>> "JUAN REYES" wrote in message
>> news:
>> > ahora al cambiar de direccion el servidor los host no hacen ping via el
>> > nombre del server, o sea el nombre aun se esta resolviendo con la
>> > direccion
>> > 192.168.1.7 parece que DC PRINCIPAL ESTA ENVIANDO AUN ESA RESOLUCION.
>> >
>> >
>> > "Guillermo Delprato [MS-MVP]" wrote:
>> >
>> >> Si que tengo idea :-)
>> >> Es la placa
>> >>
>> >>
>> >> Guillermo Delprato
>> >> MVP - MCT - MCSE
>> >> Buenos Aires, Argentina
>> >> http://w2k8-server.spaces.live.com
>> >>
>> >> Este mensaje se proporciona "como está" sin garantías de ninguna
>> >> clase,
>> >> ni
>> >> otorga ningún derecho. Ud. asume los riesgos.
>> >> This posting is provide "as is" with no warranties and confers no
>> >> rights.
>> >> You assume all risk for your use.
>> >> _____________________
>> >>
>> >>
>> >> "JUAN REYES" wrote in message
>> >> news:
>> >> > Caramba guillermo disculpa tantas molestias, pero este caso es
>> >> > fustrante,
>> >> > mira lo que acabo de hacer.
>> >> >
>> >> > 1.- Deshative la tarjeta que hasta el momento estaba funcionando.
>> >> > 2.- Active la segunda tarjeta, pero la deje DHCP.
>> >> > 3.- El servidor de DHCP le envio la direccion 192.168.1.47
>> >> > 4.- AHORA el server le da ping a todo el mundo.
>> >> >
>> >> > Todo parece indicar que es un problema que hay internamente en el
>> >> > server
>> >> > cuando este tiene la direccion 192.168.1.7
>> >> >
>> >> > Le coloque fija otra direccion 192.168.1.12 con la misma
>> >> > configuracion
>> >> > anterior, reinicie el mismo y hasta el momento no me ha dado
>> >> > problemas
>> >> > ahora
>> >> > esta viendo todos los HOST. Dime te surge una idea de todo esto...
>> >> >
>> >> >
>> >> > "Guillermo Delprato [MS-MVP]" wrote:
>> >> >
>> >> >> iSCSI no tiene nada que ver
>> >> >> Y no debería estar funcionando el servicio si no tienes un
>> >> >> dispositivo
>> >> >> iSCSI
>> >> >>
>> >> >>
>> >> >> Guillermo Delprato
>> >> >> MVP - MCT - MCSE
>> >> >> Buenos Aires, Argentina
>> >> >> http://w2k8-server.spaces.live.com
>> >> >>
>> >> >> Este mensaje se proporciona "como está" sin garantías de ninguna
>> >> >> clase,
>> >> >> ni
>> >> >> otorga ningún derecho. Ud. asume los riesgos.
>> >> >> This posting is provide "as is" with no warranties and confers no
>> >> >> rights.
>> >> >> You assume all risk for your use.
>> >> >> _____________________
>> >> >>
>> >> >>
>> >> >> "JUAN REYES" wrote in message
>> >> >> news:
>> >> >> > Guillermo mira esto:
>> >> >> >
>> >> >> > este error aparece muchas veces en event:
>> >> >> >
>> >> >> > Event Type: Error
>> >> >> > Event Source: iScsiPrt
>> >> >> > Event Category: None
>> >> >> > Event ID: 1
>> >> >> > Date: 20/10/2008
>> >> >> > Time: 3:11:33 PM
>> >> >> > User: N/A
>> >> >> > Computer: OPMMFSVR02
>> >> >> > Description:
>> >> >> > Initiator failed to connect to the target. Target IP address and
>> >> >> > TCP
>> >> >> > Port
>> >> >> > number are given in dump data.
>> >> >> >
>> >> >> > For more information, see Help and Support Center at
>> >> >> > http://go.microsoft.com/fwlink/events.asp.
>> >> >> > Data:
>> >> >> > 0000: 00 00 06 00 01 00 62 00 ..b.
>> >> >> > 0008: 00 00 00 00 01 00 00 c0 ...À
>> >> >> > 0010: 00 00 00 00 00 00 00 00
>> >> >> > 0018: 00 00 00 00 00 00 00 00
>> >> >> > 0020: 00 00 00 00 00 00 00 00
>> >> >> > 0028: bc 0c c0 a8 01 0a ¼.À¨..
>> >> >> >
>> >> >> > OJO OJO OJO OJO
>> >> >> > Y ESTOS APARECEN luego de conectar la segunda tarjeta en otro
>> >> >> > switch
>> >> >> >
>> >> >> > Event Type: Information
>> >> >> > Event Source: iScsiPrt
>> >> >> > Event Category: None
>> >> >> > Event ID: 34
>> >> >> > Date: 20/10/2008
>> >> >> > Time: 3:11:58 PM
>> >> >> > User: N/A
>> >> >> > Computer: OPMMFSVR02
>> >> >> > Description:
>> >> >> > A connection to the target was lost, but Initiator successfully
>> >> >> > reconnected
>> >> >> > to the target. Dump data contains the target name.
>> >> >> >
>> >> >> > For more information, see Help and Support Center at
>> >> >> > http://go.microsoft.com/fwlink/events.asp.
>> >> >> > Data:
>> >> >> > 0000: 00 00 68 00 01 00 c2 00 ..h...Â.
>> >> >> > 0008: 00 00 00 00 22 00 00 40 "..@
>> >> >> > 0010: 00 00 00 00 00 00 00 00
>> >> >> > 0018: 00 00 00 00 00 00 00 00
>> >> >> > 0020: 00 00 00 00 00 00 00 00
>> >> >> > 0028: 69 00 71 00 6e 00 2e 00 i.q.n...
>> >> >> > 0030: 31 00 39 00 38 00 36 00 1.9.8.6.
>> >> >> > 0038: 2d 00 30 00 33 00 2e 00 -.0.3...
>> >> >> > 0040: 63 00 6f 00 6d 00 2e 00 c.o.m...
>> >> >> > 0048: 68 00 70 00 3a 00 73 00 h.p.:.s.
>> >> >> > 0050: 74 00 6f 00 72 00 61 00 t.o.r.a.
>> >> >> > 0058: 67 00 65 00 2e 00 64 00 g.e...d.
>> >> >> > 0060: 32 00 64 00 62 00 73 00 2.d.b.s.
>> >> >> > 0068: 2e 00 68 00 75 00 31 00 ..h.u.1.
>> >> >> > 0070: 37 00 30 00 38 00 30 00 7.0.8.0.
>> >> >> > 0078: 77 00 6d 00 30 00 2e 00 w.m.0...
>> >> >> > 0080: 35 00 30 00 30 00 31 00 5.0.0.1.
>> >> >> > 0088: 31 00 30 00 61 00 30 00 1.0.a.0.
>> >> >> >
>> >> >> > Event Type: Information
>> >> >> > Event Source: l2nd
>> >> >> > Event Category: None
>> >> >> > Event ID: 16
>> >> >> > Date: 20/10/2008
>> >> >> > Time: 3:13:54 PM
>> >> >> > User: N/A
>> >> >> > Computer: OPMMFSVR02
>> >> >> > Description:
>> >> >> > HP NC373i: Driver initialized successfully.
>> >> >> > Data:
>> >> >> > 0000: 00 00 00 00 02 00 4e 00 ..N.
>> >> >> > 0008: 00 00 00 00 10 00 05 40 ...@
>> >> >> > 0010: 00 00 00 00 00 00 00 00
>> >> >> > 0018: 00 00 00 00 00 00 00 00
>> >> >> > 0020: 00 00 00 00 00 00 00 00
>> >> >> >
>> >> >> > Event Type: Information
>> >> >> > Event Source: W32Time
>> >> >> > Event Category: None
>> >> >> > Event ID: 37
>> >> >> > Date: 20/10/2008
>> >> >> > Time: 3:15:01 PM
>> >> >> > User: N/A
>> >> >> > Computer: OPMMFSVR02
>> >> >> > Description:
>> >> >> > The time provider NtpClient is currently receiving valid time
>> >> >> > data
>> >> >> > from
>> >> >> > opmmfsvr01.MMFDOMAIN (ntp.d|192.168.1.7:123->192.168.1.5:123).
>> >> >> >
>> >> >> > For more information, see Help and Support Center at
>> >> >> > http://go.microsoft.com/fwlink/events.asp.
>> >> >> >
>> >> >> > Event Type: Warning
>> >> >> > Event Source: Dhcp
>> >> >> > Event Category: None
>> >> >> > Event ID: 1007
>> >> >> > Date: 20/10/2008
>> >> >> > Time: 3:15:06 PM
>> >> >> > User: N/A
>> >> >> > Computer: OPMMFSVR02
>> >> >> > Description:
>> >> >> > Your computer has automatically configured the IP address for the
>> >> >> > Network
>> >> >> > Card with network address 001B7842EAEC. The IP address being
>> >> >> > used
>> >> >> > is
>> >> >> > 169.254.253.131.
>> >> >> >
>> >> >> > For more information, see Help and Support Center at
>> >> >> > http://go.microsoft.com/fwlink/events.asp.
>> >> >> > Data:
>> >> >> > 0000: 00 00 00 00
>> >> >> >
>> >> >> > Event Type: Information
>> >> >> > Event Source: BROWSER
>> >> >> > Event Category: None
>> >> >> > Event ID: 8015
>> >> >> > Date: 20/10/2008
>> >> >> > Time: 3:15:07 PM
>> >> >> > User: N/A
>> >> >> > Computer: OPMMFSVR02
>> >> >> > Description:
>> >> >> > The browser has forced an election on network
>> >> >> > \Device\NetBT_Tcpip_{BBD4F63D-1FEA-4F49-8E29-8F2E48F5EED0}
>> >> >> > because a
>> >> >> > Windows
>> >> >> > Server (or domain master) browser is started.
>> >> >> >
>> >> >> > For more information, see Help and Support Center at
>> >> >> > http://go.microsoft.com/fwlink/events.asp.
>> >> >> >
>> >> >> > Event Type: Warning
>> >> >> > Event Source: Server
>> >> >> > Event Category: None
>> >> >> > Event ID: 2504
>> >> >> > Date: 20/10/2008
>> >> >> > Time: 3:15:10 PM
>> >> >> > User: N/A
>> >> >> > Computer: OPMMFSVR02

Responder a este mensaje

Ads by Google

Hacer una preguntaSiguiente

Tengo una respuesta

1 2 3 4 5 6

Busqueda sugerida