Windows 7 connection to Server 2003

cannot connect windows 7 to a server 2003
 "An attempt to resolve the DNS name of a domain controller in the domain being joined has failed. Please verify this client is configured to reach a DNS Server that can resolve DNS names in the target domain."
What edition of Windows 7?
Only Professional, Ultimate and Enterprise editions can join a domain.
----------------------------
This is either the DHCP is not configured properly to give the computer the proper DNS or you are using a static IP and have specified the wrong DNS or simply your DNS cache has not been updated. Lets start with the last one and work our way up. To refresh the cache do...
ipconfig /flushdns
ipconfig /registerdns
You have to do this with elevated rights in Windows 7 so right click in the Command Prompt and select run as administrator.
Then you can see if it is resolving your DC by doing a ping...
ping yourdomainname.local
If it does then try joining if not then look at what is specified in the DNS of your...
ipconfig /all
If it is not your primary Name Server then look at the network connections to correct it or look at your DHCP settings.
You may want to do an NSLOOKUP to make sure the computer is seeing your Name Server and not another.
You may also want to look at your DNS server to make sure the host for the DC is registered.

How to reset Internet Protocol (TCP/IP)

http://support.microsoft.com/kb/299357
Intro
One of the components of the Internet connection on your computer is a built-in set of instructions called TCP/IP. TCP/IP can sometimes become damaged or corrupted. If you cannot connect to the Internet and you have tried all other methods to resolve the problem, TCP/IP might be causing it.
Because TCP/IP is a core component of Windows, you cannot remove it. However, you can reset TCP/IP to its original state by using the NetShell utility (netsh).
This article describes two ways to reset TCP/IP. You must be logged on to the computer as an administrator. Use a manual method to reset TCP/IP for Windows XP
The reset command is available in the IP context of the NetShell utility. Follow these steps to use the reset command to reset TCP/IP manually:

1. To open a command prompt, click Start and then click Run. Copy and paste (or type) the following command in the Open box and then press ENTER:
   cmd
2. At the command prompt, copy and paste (or type) the following command and then press ENTER:
   netsh int ip reset c:\resetlog.txt
   Note If you do not want to specify a directory path for the log file, use the following command:
   netsh int ip reset resetlog.txt
3. Reboot the computer.

Use a manual method to reset TCP/IP for Windows Vista and Windows 7
The reset command is available in the IP context of the NetShell utility. Follow these steps to use the reset command to reset TCP/IP manually:

1. To open a command prompt, click Start and then type CMD in the Search programs and files.
2. Right-click CMD.exe icon in Programs and choose Run as administrator.
3. When the User Account Control box pop up, click Yes.
4. At the command prompt, copy and paste (or type) the following command and then press ENTER:
   netsh int ip reset c:\resetlog.txt
   Note If you do not want to specify a directory path for the log file, use the following command:
   netsh int ip reset resetlog.txt
5. Reboot the computer.

When you run the reset command, it rewrites two registry keys that are used by TCP/IP. This has the same result as removing and reinstalling the protocol. The reset command rewrites the following two registry keys:

SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\ 
SYSTEM\CurrentControlSet\Services\DHCP\Parameters\ 

To run the manual command successfully, you must specify a file name for the log, in which the actions that netsh takes will be recorded. When you run the manual command, TCP/IP is reset and the actions that were taken are recorded in the log file, known as resetlog.txt in this article.
The first example, c:\resetlog.txt, creates a path where the log will reside. The second example, resetlog.txt, creates the log file in the current directory. In either case, if the specified log file already exists, the new log will be appended to the end of the existing file.
 811259 How to determine and recover from Winsock2 corruption in Windows Server 2003, in Windows XP, and in Windows Vista

2 NICs -errors in Device Manager

http://support.microsoft.com/kb/943104/es El código de error código 10 se genera cuando el Administrador de dispositivos no tiene información suficiente o el error que asciende por los controladores de dispositivo no se reconoce por el Administrador de dispositivos. Además, este error puede producirse cuando uno de los controladores que necesita el dispositivo no se inicia. Si se utilizan muchos controladores por un dispositivo en particular, puede ser difícil determinar el que provocó el error.
El código de 10 de error similar al siguiente:
No se puede iniciar este dispositivo. (Código 10)
La resolución más común es actualizar los controladores que están asociados con el dispositivo del error. Para ello, siga estos pasos:
En el cuadro de diálogo de Propiedades del dispositivo, haga clic en la ficha Controlador .
Haga clic en Actualizar controlador para iniciar al Asistente para actualización de Hardware.
Siga las instrucciones para actualizar el controlador.
Nota Es podrán que deba proporcionar la ruta de acceso del controlador. Windows puede tener el controlador incorporado o los archivos del controlador todavía pueden instalarse desde la última vez que ha configurado el dispositivo. Si se le pedirá el controlador y no lo tiene, puede intentar descargar el controlador más reciente desde el sitio Web del proveedor de hardware.
Problemas típicos de error código 10
El error código 10 se debe principalmente a los problemas de controladores de hardware y dispositivos o a problemas de compatibilidad entre los controladores de hardware y software adicional que se instala en Windows. Por lo tanto, recomendamos que solucionar estos problemas centrándose en controladores de dispositivos, en problemas de configuración de dispositivo y en problemas de compatibilidad de hardware.
Controladores de dispositivos incompatibles, obsoletos o dañados
Si sospecha el error código 10 está relacionado con controladores de dispositivo incompatibles, obsoletos o dañados, pruebe los métodos de solución de problemas siguientes.
Método 1 Actualizar el controlador de dispositivo de hardware a través de Windows Update. Para tener acceso a Windows Update, visite el siguiente sitio Web de Microsoft:
http://update.microsoft.com
Método 2
Actualice los controladores de dispositivo desde el sitio Web del proveedor. Siga las instrucciones de instalación o actualización.
Si el dispositivo estaba preinstalado en el equipo, visite el sitio Web del fabricante de equipo.
Si el dispositivo se instaló después de la compra del equipo, visite el sitio Web del fabricante del dispositivo.
Si el dispositivo estaba preinstalado en el equipo y el fabricante del equipo no tiene un controlador actualizado para el dispositivo, visite el sitio Web del fabricante del dispositivo.
Nota Asegúrese de que los controladores de dispositivos que se van a instalar son compatibles con la versión de Windows y la plataforma actual.
Nota Al revisar los comentarios del cliente, muchos de los problemas de error código 10 están relacionados a los dispositivos conectados mediante un puerto USB. Como se mencionó anteriormente, asegúrese de que tiene los controladores más recientes instalados para el dispositivo junto con todas las actualizaciones para Windows. En el caso específico de Windows XP, consulte el artículo siguiente para determinar si se aplica a su situación:
925196 Un equipo que ejecuta Windows XP no puede detectar una unidad flash USB, un iPod de Apple o una unidad de disco duro externo
Si está ejecutando Windows XP y no se puede instalar el Service Pack 3 de Windows XP, consulte el siguiente artículo para determinar si se aplica a su situación:
940514 Dispositivos USB no funcionan después de desconectar y, a continuación, vuelva a conectar un concentrador USB de un equipo que ejecuta Windows XP
Problemas de configuración de dispositivo
Si sospecha que está relacionado con el error código 10 faltan actualizaciones de software y los service packs, pruebe los métodos de solución de problemas siguientes:
Instalar el service pack más reciente de Windows.
Utilice Windows Update para instalar las actualizaciones más recientes para Windows. Para ello, visite el siguiente sitio Web de Microsoft:
http://update.microsoft.com
Instale las actualizaciones que son específicas para el equipo o el dispositivo. Para ello, le recomendamos que visite el sitio Web del fabricante de equipo o sitio Web del fabricante del dispositivo.
Actualizaciones de software y sistema operativoSi sospecha que está relacionado con el error código 10 faltan actualizaciones de software y los service packs, pruebe los métodos de solución de problemas siguientes:
Utilice Windows Update para instalar las actualizaciones más recientes para Windows. Para ello, visite el siguiente sitio Web de Microsoft:
http://update.microsoft.com Para obtener más información acerca de cómo obtener el service pack más reciente de Windows, haga clic en los números de artículo siguientes para verlos en Microsoft Knowledge Base:
322389 Cómo obtener el service pack más reciente para Windows XP
935791 Cómo obtener el service pack más reciente de Windows Vista
889100 Cómo obtener el service pack más reciente para Windows Server 2003
968849 Cómo obtener el service pack más reciente para Windows Server 2008
Instale las actualizaciones que son específicas para el equipo o el dispositivo. Para ello, le recomendamos que visite el sitio Web del fabricante de equipo o sitio Web del fabricante del dispositivo.
Problemas de compatibilidad de hardware Otra posibilidad es que el dispositivo no fue diseñado para trabajar con una versión determinada de Windows que esté utilizando. Puede utilizar la lista de ventanas de compatibilidad de Hardware (HCL), para determinar si el dispositivo está disponible como compatible con la versión actual de Windows. Para ello, visite el siguiente sitio Web de Microsoft:
http://www.Microsoft.com/whdc/hcl/default.mspx
=========================

Codigo-de-Error-Por-El-Administador-de-dispositivos.html Código error 10
Si el dispositivo tiene un valor "FailReasonString" en su clave de hardware, se muestra esa cadena como mensaje de error. El controlador o el enumerador coloca allí este valor de cadena del Registro. Si no existe "FailReasonString" en la clave de hardware, se muestra el siguiente mensaje de error genérico:
No puede iniciar este dispositivo. (Código 10)
Solución recomendada
El dispositivo no se pudo iniciar. Haga clic en Actualizar controlador para actualizar los controladores de este dispositivo. En la ficha Propiedades generales del dispositivo, haga clic en Solucionar problemas para iniciar el Asistente para la solución de problemas.
Código error 12:
Este dispositivo no encuentra suficientes recursos libres que pueda usar. Si desea utilizar el dispositivo, debe deshabilitar otro de este sistema. (Código 12)
Solución recomendada
El BIOS, el sistema operativo o una combinación de los dos han asignado a dos dispositivos los mismos puertos de E/S, la misma interrupción o el mismo canal de Acceso directo a memoria (DMA, Direct Memory Access). Este mensaje de error también puede aparecer si el BIOS no asigna recursos suficientes al dispositivo (por ejemplo, si un bus serie universal (USB) no es una interrupción del BIOS debido a que una tabla de sistema multiprocesador, MPS, está dañada).
Puede utilizar Administrador de dispositivos para determinar donde está el conflicto y deshabilitar el dispositivo problemático. En la ficha Propiedades generales del dispositivo, haga clic en Solucionar problemas para iniciar el Asistente para la solución de problemas. ===================http://www.holacape.com/2011/07/este-dispositivo-no-puede-iniciar.html

Solución: en la página del fabricante encontré el controlador de red, se ubica en "Realtek PCI-E Ethernet Drivers ". Primero desinstalé el driver conflictivo, y luego instalé el driver descargado. El error desapareció:

http://foro.noticias3d.com/vbulletin/showthread.php?t=227737
========================
http://www.justanswer.com/computer/4w9h9-computer-crashed-so-friend-dump-everything.html
========================
http://tecnicambalandia.blogspot.com/2013/02/realtek-rtl81xx-drivers.html
Realtek Advice
Q. Device management appears code 10 error if multiple 8169/8168/8101 cards installed.
A. Please re-install the driver to all Realtek network card to ensure all the driver
   are identical.
Q. The driver can not install sucessfully after the network card drver selected
A. Try to use 'browse my compter ...' , ' let me pick ... ' , 'Have Disk' to install
   the driver
=======

Driver Installation

To install the driver, proceed as follows

1. Launch the executive file "setup.exe"
2. Follow the instructions displayed by the setup.exe program

NOTE:

• On Plug and Play Windows platforms, the adapter will be identified and configured automatically. Please stop all the automatic installation by Windows system. 
• To install driver, you should have administrator's privilege.

Manual Installation

Manual installation is to install driver by the installation file (INF) rather than use the "setup.exe" mentioned above. To install driver manually, please open Device Manager, expand the Network adapters tree list, select the "Realtek FE/Gbe Family Controller", and click right button, execute the menu item Update driver..., and follow the direction to indicate the path of INF file. NOTE：

• Manual installation is a kind of method of installation by advanced user. Generic users please use the "setup.exe" to install driver.

Silent Installation

The section describes the process to install driver without showing any dialog box on user's screen and requiring user's attendance. If you need to install driver in silence, you may launch DOS prompt and execute Silent Installation

C:>%driver_path%\setup.exe /s

Silent Removal

C:>%driver_path%\setup.exe /s /f1".\uninstall.iss"

Troubleshooting

If you encounter any problems during the driver installation phase, please carefully follow the instructions described in Installation section to install again. If you still need assistance, please contact our technical support department. For more information, you may access to our web site.

sesión "Circular Kernel Context Logger"

No se pudo iniciar la sesión "Circular Kernel Context Logger" por el siguiente error: 0xC0000035
Error de origen común?:
El servidor DHCP no asignó ninguna dirección de red al equipo para la tarjeta de red con dirección de red 0x080027003CDF. Error: 0x79. El equipo continuará intentando obtener una dirección desde el servidor de direcciones de red (DHCP). 

Deshabilita IPV6 y comprueba si el error sigue apareciendo

http://support.microsoft.com/default.aspx/kb/929852
http://support.microsoft.com/kb/952842

Acceso-limitado-a-la-red

Source

Es un error  que se produce SOLO cuando la maquina está suspendida o hibernada y se levanda de hibernacion TIene que ver con el IPv6 que no puede activarse al tener una tarjeta de red o wireless que no se levanta bien de odos de ahorro de energia y normalmente se soluciona, o bien quitando la marca de "permitir ahorro de energia en este dispositivo" en la correspondiente tarjeta de red en el Administrador de dispositivos, o bien desactivando el IPv6 (no recomendado).

Puede ser el driver de la tarjeta de red... y efectivamente no conviene desactivar el IPv6. En cualquier caso por lo leido, no pasa nada.

Source
Nothing to worry about, the system repeatedly tries to start the logger session until it succeeds. A temporary failure to start mostly (but not always) happens during a system state transition from standby to running.

------------------- 

Solution: Go to Control Panel\All Control Panel Items\Network and Sharing Center

Choose homegroup and sharing options

Leave the homegroup

Why? Resolve windows error

-----------------------------

Exact same errors and this fixed it for me

There probably more to it and this may be just a workaround but its working since--no errors )

1  found this article http://support.microsoft.com/kb/293497

2 Then  Did the folowing

(from cmd as Administrator ) 

• ipconfig  /all   -- return (save results for next time---its microsoft)
• ipconfig /flushdns   --return
• ipconfig /release /all  --return 
• quit

Make sure DCHP is enabled (well I had to), then you will have to reboot

--on restart, it re-registered with dns 

-------

Below is what I think happened in my case

(Ive a small home network with 5 networked devices) Windows 7pro  32bit

 ID 2 pcs mapped manually(This must be treated like a private network automatically?Somehow the subnet was set (automatically) to 255.255.255.255-- which is wrong but Ive no idea how it happened )

Although both devices were OK and I had net access all the time (homegroup), the system was also trying to allocate 2 extra addresses to the SAME 2 mapped pcs (which are been recognised as 2 seperate devices on a private network--- and cant be registered with dns,) so basically my system was retrying over and over--giving the errors above.

--------

I am not sure what your network config has to do with this error.  But, I'll bite. Microsoft in teh above link says to To resolve this problem, change the mask of the address pool to the subnet mask that the external network uses

-----------------------

I was able to relate my problem to a change I did a few days ago, about the time I start receiving the above error message.  The change that I did was to leave the homegroup (in the : change homegroup settings windows)
They say the homegroup only work with other win7 system on the network and since I do not have another win7  to share media and file on the local network I figured I did not need it.  Well that is when approximately that I started receiving these errors messages.  As a trial solution, I re-enable the homegroup and rebooted the system, the error message did not reappear so far, I keep my finger crossed.
Leaving the homegroup did not stop me from sharing file through a regular workgroup on my local network,  I am still confuse as to why they have to introduce this homegroup at all.  

------------------

Do you have a printer attached but not shared? Your network LAN is trying to find something. You may need a better print driver 

----------------------

I ran into trouble with this, and it was a Homegroup issue and here's what I think caused it. I created a Homegroup on my computer and my wife joined it on hers. Via Homegroup, her computer discovered my printer and installed the drivers. That was the plan, she wanted to print on my printer. So far so good. But at some point down the road I happened to find myself inside of Homegroup, and I saw a message about Homegroup finding a printer which I thought was a little strange. It asked me whether I wanted to install the printer and I said yes (I figured my wife had somehow uninstalled our shared printer on her computer or something). What actually happened was that Homegroup discovered an old printer driver on her computer from a printer she used to use a long time ago.
Long story short, if you use Homegroups to share a printer, the person who is physically connected to the printer likely doesn't want to install any printers found on Homegroup on their computer.
Source
CAUSE

This originated in the Windows 7 SP1 DVD/ISO creation process. There was an issue in the creation process that caused a WMI registration to remain in the DVD/ISO. Since the registration is designed to work only during the DVD/ISO creation process, it fails to run on a live system and causes these events. These events are not indicative of any issue in the system and can be safely ignored. If however you want to prevent these events from getting generated and want to remove this specific WMI registration manually, please follow the steps mentioned in this article for running the workaround script.

Some of the controls on this property sheet are disabled

"Some of the controls on this property sheet are disabled because one or more other Network property sheets are already open. To use these controls, close all these property sheets and then reopen this one"
Source
Source
Steps to reproduce:

1. Open “network connections” from the control panel.
2. Right click on “Local Area Connection” and click “properties”

Resolution:

1. Download drivers for your current network card.
2. Uninstall all your network cards from (Control panel->System->Device manager)
3. Restart your computer.
4. Let windows attempt to install your network card for you. If windows can not find the correct network card drivers use the one you downloaded in step 1.

If you are still having problems you could try;

• Uninstall all network related applications, eg HP wireless assistant, HP wlan assistant, ect…
• Uninstall all virtual machine applications, eg VMWare, Virtual box, ect…

Source
Are you opening the Local Area Connection so the Status Window is open? or just Right clicking the Local Area Connection? Are you logged in as a limited user or as an Administrator user? Enable the Hidden Administrator account and log out of the user profile your in and log in as Admin and see if it works there. then check your user account for restrictions. 
------

---

Try this: http://www.chicagotech.net/netforums...t=3921&start=

Source
Based on my research, the issue is usually caused by an aborted NIC driver
installation process which leaves a registry value under the following key:
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\RunOnce
I suggest you try the following steps to delete the registry value:
1. Click Start, type regedit in the Start Search box and press Enter.
2. Navigate to the following key:
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\RunOnce
3. Right click RunOnce and select Export to make a backup.
4. In the right pane, delete the value referenced to rundll32.
5. Quit Registry Editor.
Then, restart the computer to test the issue.
If the issue persists, please reinstall the NIC driver to check the result.
Source
Here's what happened, if you want to know. When I attempted to set the NetBEUI protocol up McAfee Firewall locked me out. I did not know you had setup McAfee to allow different protocols. This is an off the shelf version and all other devices use Enterprise version. ANYWAY, I knew the install was not complete so I searched the registry for "install" and found 3 items 2 were queues in waiting and the other was in HKLM, software, MS, windows, current version, runonce. Deleted that, rebooted and voila! I was back in control.

Windows NT6.1 can not connect to win NT5.2

Source
Source 2

Your routers needs to be connected DIRECTLY to your main (desktop) computer, not through another device. I had mine going through a VOIP adapter. I removed this, and how it works.

=================
Probs sharing Vista/XP

I could get to the Windows XP Pro SP3 computer with my Windows 7 Pro laptop, but got the error message when trying to open the shared folder. Some of these guys are reporting the issue correctly and I believe they did everything right. My tip, which did solve the problem was to add a registry entry that will increase the IRPStackSize to 15. Turns out for me the issue had nothing to do with networking. You can look here to help you solve your issue and read about the solution:
http://www.dslreports.com/forum/r21292996-XP-Pro-irpstacksize-is-too-small

The article you linked to:
IMPORTANT: Type "IRPStackSize" exactly as it is displayed because the value name is case-sensitive
The article the Event Viewer links to:
Using Regedit on the win XP PCs, open the following registry key:
HKLM\System\CurrentControlSet\Services\LanmanServer\Parameters\IrpStackSize
So should I be using IRP or Irp? 

 Use 20 as size!

IRPStacksize errors only occurred when trying to access Shares of a Computer (laptops). Not transferring, just accessing.
-----------------------------------------
Data Type: DWORD
Default: 0x4
Maximum: 0xC
Increasing this value requires some memory from the non-allocated memory pool, but the impact should not be noticeable.
NOTE: It is not always advisable to set the IRPStackSize value to its maximum of 12. Generally, you should start the value at 4 and work your way up, increasing the value by 1 each time. The problem may still occur if the value is too high
--
"Ah, women. They make the highs higher and the lows more frequent." - Friedrich Nietzsche
"'It's the law' is just an excuse for the unintelligent and unimaginative to remain that way" - Me

=================
Although the permissions were set to "everyone" you also have to go to the
security tab, click edit, click add, type everyone in the box, click apply 
================= 
Try turning off "Password Protect Sharing" under Control Panel > Network and Sharing Center ... I tried that and haven't had any troubles since. Once that is turned off filesharing is basically the same as XP
=================
Adjust OneCare through the following steps and that seemed to solve his problem:
Windows Live OneCare -
Change OneCare Settinge -
Firewall connection tool -
Tick relevant options (Network discovery, file and print settings, etc) -
OK -
Advanced Settings -
Change file sharing from 'Do not share files and printers" -
OK -
OK 
===============
change the workgroup name on the Vista machine from "workgroup" to MSHOME. Theen create a password on Vista User Account. I went onto view network computers on my XP machine, and the laptop (Vista) was sat there waiting. double clicked it, entered the user name which was the user account name on the laptop, entered the password and it was done.
=============== 
Make sure that file sharing is on, password protect is off and a Private Network id defined via Network/Sharing center. I also had sharing set on both system's C-root drives plus applicable printers, dvd and external HDD.
To make it work:
1. Get into ms-explorer,
2. Right-click on the c-drive that you're trying to access..
3. select properties.
4. select Security tab
5. see if User Name 'everyone' is in the list of defined users.
6. If it isn't, add it to the list by selecting 'advanced',then 'edit' then 'add'.. just type in the word 'anyone' in the user box and click ok. It is now added with limited permissions. Select it again and this time select 'edit'... click on 'full control' for the everyone user.
7. If it was already there OR if you just did step #6 above, make sure you give user 'anyone' Full-Control via the dit option above.
Keep going... you're not finished......
8. Go into 'advanced' again and look for user 'anyone' select it for 'edit'. If you don't see it, go back to step #6...
9. Once found and when in 'edit', give user 'anyone' FULL-CONTROL' permissions.
10. You may be given a few 'cannot grant permission' messages, but just keep clicking ok until the process completes... a few minutes.
You should now be able to connect without errors.
===============
REINSTALL THE WIRELESS ADAPTER ON THE XP COMPUTER
=================
Probs sharing Seven/XP

Mark - Apr 3, 2010

On the windows 7 machine, go to the network and sharing center. Click on the "Advanced sharing settings".
Almost towards the bottom, there should be a "File Sharing Connections" section, which is probably defaulted to the 128-bit encryption. Change it to the 40 or 56 bit encryption and your XP machine should show up.

For sharing between Windows 7 and Windows XP you have to set your Windows 7 computer to the lower encryption setting before it will see the Windows XP computers on your network.

===============

by Gunnar in Sweden http://www.filmtuben.se/index.php
If you're using Windows Firewall, you can skip this section, because Windows Firewall automatically opens the correct ports for file and printer sharing when you turn on network discovery. If you're using another firewall, you must open these ports yourself so that your computer can find other computers and devices that have files or printers that you want to share.
To find other computers running Windows Vista, open these ports:
*UDP 3702
*TCP 5357
*TCP 5358
To find other computers running earlier versions of Windows, and to use file and printer sharing on any version of Windows, open these ports:
*UDP 137
*UDP 138
*TCP 139
To find network devices, open these ports:
*UDP 1900
*TCP 2869
http://windows.microsoft.com/...

enrutamiento selectivo -ISP

Subredes
Es tarea del diseñador de la red o del administrador de la misma el obtener la partición en subredes más acertada de acuerdo con las necesidades actuales y futuras, con objeto de optimizar el número de IPs utilizadas, sobre todo en el caso de que la red séa pública.
Por un lado, se pueden precisar subredes con unas necesidades de host predeterminadas (p.e. 50 host por subred, 120, etc.), por otro se debe procurar que el número de IPs desperdiciadas séa mínimo, y por otro lado se deben limitar al máximo el ancho de banda absorvido por las peticiones de broadcast.
Por lo tanto, se hace preciso un cálculo exacto de las diferentes obciones disponibles, buscando que el rendimiento de la partición séa máximo, dentro de las necesidades exigidas a la partición. Un resumen de los rendimientos (direcciones ) lo tenñeis en la siguiente tabla:

Fuente

Pudiera ser que haya creado algun bridge y le haya asignado IP de otra red, eso justificaria que un ping tuviera respuesta.
Echa un vistazo a /etc/conf.d/net para ver si has descomentado alguna seccion y no te acuerdas.
Ese tipo de cosas suelen ocurrir cuando se usa alguna VM y para que funcione bién la red se crean puentes entre la tarjeta virtual de red y la fisica.

-----------

El que te está contestando es el router de tu Proveedor de Servicios. Tu equipo envía por la "default" todo el tráfico para el cual no tiene ruta. El primer router que se precie debe darte un error vía icmp diciendo que no sabe cómo enrutar dicho paquete. 

 Resulta que los routers de tu Proveedor de Servicios sí que tienen en su tabla de rutas la 192.168.2/24 y eventualmente acaban encontrando a un Host, que obviamente responde.

Esto NUNCA debería pasar. Los rangos de la RFC1928 deben cortarse SIEMPRE, es decir, cualquier router del Proveedor debe denegar tráfico hacia y desde dichas direcciones.
Un fallo del ISP. 

-----------------

 He creado la siguiente ruta en el router principal (router pentium 4):

route add -net 192.168.2.0 netmask 255.255.255.0 gw 10.0.2.5 dev eth0

192.168.2.0 Seria a la red que quiero acceder desde 10.0.2.x.
y 10.0.2.5 seria la ip wan del router al que quiero acceder (que tiene la ip lan en 192.168.2.1)
¿Estaria correctamente añadida esa ruta en el router principal?
Porque lo he hecho y me responde esto al intentar hacer un ping:

PING 192.168.2.1 (192.168.2.1) 56(84) bytes of data. From 10.0.2.18: icmp_seq=1 Redirect Host(New nexthop: 10.0.2.1) From 10.0.2.18: icmp_seq=2 Redirect Host(New nexthop: 10.0.2.2) From 10.0.2.18: icmp_seq=2 Redirect Host(New nexthop: 10.0.2.1) From 10.0.2.18: icmp_seq=3 Redirect Host(New nexthop: 10.0.2.2)

¿Que ocurre aqui?
El otro router (que contiene el rango 192.168.2.x en LAN), no lo he tocado para nada. ¿Es 100% necesario añadir una ruta allí tambien?
Si es asi, el otro router es un linksys con dd-wrt.

=========================
Selective routing / how to separate 2 subnets 

You've wired the Ethernets together. Don't do that.

Why I can't wire two subnets together?
> Isn't subneting invented to separate two or more networks connected together? It works perfectly without a router and, I think, it's desired solution in some circumstances, isn't it?
The short answer -- no. 

Subnetting was *not* designed to separate two or more networks connected together. It was to make it possible to separate two or more networks and have them communicate with each
other.
If you choose to put more than one subnet on the same virtual network, you will not be able to prevent machines from talking to each other.
It takes active steps at every possible pathway two machines could use to talk to each other to keep them from talking to each other, and you can't do that on a physical wire without using VLANs or a similar scheme.
You may get it to work for a bit, and then suddenly the machines find some other way to talk to each other.
=================
[OLSR-users] Same IP address for several interfaces

OpenSUSE -icmp_seq= Redirect Host

From 192.168.4.251: icmp_seq=2 Redirect Host(New nexthop: 192.168.4.1)

Source
You are seeing ICMP Redirects. Directly from Cisco, ICMP Redirects happen when:

- The interface on which the packet comes into the router is the same interface on which the packet gets routed out.
- The subnet or network of the source IP address is on the same subnet or network of the next-hop IP address of the routed packet.
- The datagram is not source-routed .
- The kernel is configured to send redirects.

You can disable ICMP redirects by going under interface config mode and issuing  
no ip redirects
and you won't see that anymore.
"Redirect Host" messages

If I understand this correctly, the 'hub' cannot talk anymore to 'the remote nodes' than the computer you were using for the ping. It just happens to have the necessary routing information to know the gateway IP-addresses for the 192.168.3/24 and 192.168.2/24 networks. I need to do a little guesswork here: 

I assume that your 'remote nodes' are actually located in these two networks and that you are not operating a really weird layer 2 device which physically partitions the ethernet connected to eth1 of the hub. If this is so, you could just put everything which is part of this LAN into a single IP-network, continue to use the 'hub' as default gateway and configure the other stations to simply make use of the information in the redirect messages. Alternatively, continuing to use the hub as 'gateway' should work as well, it will just cause a (probably non-relevant) slowdown.