IP addresses

  • Thread starter Thread starter GriffithsJ
  • Start date Start date
G

GriffithsJ

Hi

What is the maximum number of IP addresses one can bind to a particular
machine?

I ask because I've got 12 bound to one machine at the moment. Every time I
add another, the machine becomes "unavailable" for about 10 minutes (by
"unavailable", I mean that I lose my terminal services connection, web
access etc). When I added the first 5, there was no such problem. I can't
tell if it's actually re-booting because it's hosted by a separate company.

Is there a limit or problem that I'm unaware of?

Thanks

Griff

PS - apologies for "multi-posting", but I've also posted to
microsoft.public.windows.server.general before discovering this group.
 
What Service Pack are you running? I seem to recall an issue with this a
long time ago, but it was fixed in an early SP.
If you have SP4, you may try reinstalling SP4. If you don't have SP4, I
would recommend you try installing it.

--

Thanks,
Marc Reynolds
Microsoft Technical Support

This posting is provided "AS IS" with no warranties, and confers no rights.
 
GriffithsJ said:
Hi

What is the maximum number of IP addresses one can bind to a particular
machine?
Click to expand...

A lot -- more than you wish to bind in all likelyhood.

I have heard of 2000+ IP addresses on single NIC of an NT 4 server.
I ask because I've got 12 bound to one machine at the moment. Every time I
add another, the machine becomes "unavailable" for about 10 minutes (by
"unavailable", I mean that I lose my terminal services connection, web
access etc). When I added the first 5, there was no such problem. I can't
tell if it's actually re-booting because it's hosted by a separate
Click to expand...
company.

It's probably just reseting the IP/NIC driver and that's loosing your
connection.

Can you script this in using NetSH, and just run it ONCE?

Netsh is hard to learn to use so the easiest way is to tell it to list out
the current
configuration to a text file, edit, then load the results back using the
Netsh
script feature.

It can also be done through the registry.
 
Marc

Thanks for the reply.

We're running sp3. Unfortunately, I's be a little loathe to apply the patch
since my predecessor had a server running our application and this ground to
a halt with sp4 on it. The server was rebuilt with sp3 and the application
ran fine.

sp4 was never proven to be the cause of the problem, I suspect just the
scape-goat. However, I'd have a hard time trying to convince people to try
reapplying it again.

Griff
 
Back
Top