RE: NIC dropping data until IP is reset

Hannes,

Thank you. Yes, the Net Mask is identical on the two interfaces. Everything
is identical, actually, except the IP address (and, of course, the MAC).

My current workaround is this:

1) I created a BAT file that contains two NETSH Interface IP Set Address
commands, the first to set the interface IP to a bogus value and the second
to set it back to its correct value.

2) I created a BAT file that issues SysInternals' PSExec command to run the
first BAT file on the server.

In this way, when I am working (on my networked workstation) and the
internet comnnection disappears, I can simply invoke the second BAT file,
which resets things on the server.

I never had any problems with Windows Server 2003. This began when I did a
clean install of Windows 2003 R2.

Thanks again.
/Joel

"Hannes" wrote:

What are the masks for N1 and N2? (If both NICs cover the same network, you
may confuse Windows' routing, why it may behave randomly.)

When you click OK on the dialog, a message is sent to the TCP/IP stack to
reconfigure, with the new IP address. This probably flushes caches, etc, and
makes things work again for a while for you.

The stack is not constantly polling the registry for changes, so by only
changing the registry values, nothing will happen. The TCP/IP stack has to be
told to read its new configuration, and clicking OK on the dialog is one way
of triggering this to happen.

I suggest you run a sniffer (e.g. Wireshark) to find out what is happening
to your traffic when it is in the "broken" state. I am guessing that requests
come in one adapter, and are sent out the other, possibly due to the
overlapping of networks.

/ Hannes.

"Joel Finkel" wrote:

I am still trying to solve a problem about which I posted and entry in
December.

I have a Windows 2003 R2 server with three NICs. The first connects to my
local LAN. The other two connect to an ADSL modem; each has its own IP
address.

The problem is that, periodically, the connection to the ADSL modem fails. I
can restablish it by changing the IP address assigned to EITHER NIC!

Consider this configuration:

NIC IP Address Metric
N1 222.222.222.001 10
N2 222.222.222.111 30

I have internet connectivity through N1 for a while (30 mins to 20 hours).
When it fails, I can change the IP address of N2 to, say, 222.222.222.222,
and data will immediately begin to flow again over N1. I can also change the
IP address of N1 to anything and then back to its assigned value, and data
will begin to flow. In other words, modifying the IP address of EITHER NIC
will restart data flow.

Note: I use the GUI to change the IP addresses, namely Network Connections
| Status | Properties | Internet Protocol.

I have several questions:

1) Why is this happening?

2) How can I fix it?

3) Can someone tell me EXACTLY what happens when I close out of the Network
Connection dialog? In other words, what are all the actions that are
initiated. I know that one thing is that a registry key value is modified
(HKLM\System\ControlSet001\Services\Tcpip\Parameters\Interfaces\{xxxx}:IPAddress
now holds the current IP address. But simply changing this value with
Regedit does not fix the problem, so obviously other things are happening.

4) Failing to fix the root cause, is there some way I can automate (perhaps
with Powershell), the process of modifying the IP address in a manner that
triggers the same actions(s) that the GUI triggers?

5) Is there another newsgroup I should be using to ask this question?

Thanks in advance for all suggestions!


.

Relevant Pages

  • RE: Printing from Win9x clients stops
    ... Open Server Management. ... then right-click the name of the computer running Windows Small Business ... >From the client computer: ... The Select Network Component Type ...
    (microsoft.public.windows.server.sbs)
  • RE: Printing from Win9x clients stops
    ... The printers with 9x drivers on the server appeared automatically in the ... > then right-click the name of the computer running Windows Small Business ... > From the client computer: ... The Select Network Component Type ...
    (microsoft.public.windows.server.sbs)
  • Re: random lockouts
    ... >> I've got a network with several Windows 2000 Servers and ... >> about 150 Windows 98 clients. ... >This problem occurs because the Windows 2000-based server ... >because the session that is reused is against a DFS ...
    (microsoft.public.win2000.security)
  • Questions Relating to Administering Windows 2000 Server
    ... installed the network client on the target computer. ... Sarah has been attempting to install Windows 2000 ... Server for two days. ... Sarah has checked the cables and hard drives. ...
    (microsoft.public.cert.exam.mcse)
  • Questions Relating to Administering Windows 2000 Server
    ... installed the network client on the target computer. ... Sarah has been attempting to install Windows 2000 ... Server for two days. ... Sarah has checked the cables and hard drives. ...
    (microsoft.public.cert.exam.mcse)