Multihomed Win2K login problem

[Ash Ridley]

Hi,

I have a problem thats driving me crazy right now.

I have a Win2K server (SBS if that makes any difference) that until today
had 3 network adapters in it (1 LAN, 1 WLAN and 1 WAN(Internet)). Today the
WLAN adapter failed and I thought that I could keep the system running until
I replaced it by simply removing the connection for the failed adapter,
binding its IP address to the LAN adapter and then plugging my Wireless
access point into my hub (as opposed to the cross over cable directly to the
adapter I had previously.

This all works fine except that the wireless clients get an error on login.
I've had that the domain server doesnt exist and that the domain server
couldnt validate their passwords. Since one of them is a WinME box I've just
hit escape and gone to the desktop and confirmed that the client does
actually have connectivity to the server (it does, and can get out on the
web as well)

Any ideas why my wireless clients cant authenticate to the second bound IP
address on the LAN adapter?

Thanks

 

[Ash Ridley]

Does no one have any suggestions about this?

 

[Phillip Windell]

You original assumption of what you could have done to keep it running may
have been wrong, but I'm not really sure what you were attempting. The most
likely way to keep it going is obviously to just replace the bad Nic with a
new one. It's a good idea to keep a few nics of the same brand and model
laying on a shelf for these situations. Sometimes even switching brands and
models can cause a little grief, it's usualy not too serious but is
annoying.

I'm sorry, I don't know how the WAP and the hub you plugged it into fits
into the picture so I really can't comment on that. There are too many
dozens of possible scenarios to guess at. The actual topology is the
important thing to know. Whether something is wireless or if it uses a hub
or switch really doesn't matter.

 

[Ash Ridley]

Phillip,

Thanks for the reply.

Basically I have 2 logical subnets on the same physical interface (the
interface connects to a single hub which has the original wired subnet and
my wireless gateway with a different subnet address on it). But none of the
clients on the second logical subnet can login (but they could when the
second subnet had its own NIC). I'm guessing its something along the lines
of NETLOGON not binding to the second address on a single card but thats
just taking a wild stab in the dark. Its certainly not a connectivity issue
as the clients can ping the server and get on the web etc they just cant
authenticate to the server for some reason

I'm in the process of trying to replace the second NIC (too complicated) but
I need to get this running in the meantime

You original assumption of what you could have done to keep it running may
have been wrong, but I'm not really sure what you were attempting. The most
likely way to keep it going is obviously to just replace the bad Nic with a
new one. It's a good idea to keep a few nics of the same brand and model
laying on a shelf for these situations. Sometimes even switching brands and
models can cause a little grief, it's usualy not too serious but is
annoying.

I'm sorry, I don't know how the WAP and the hub you plugged it into fits
into the picture so I really can't comment on that. There are too many
dozens of possible scenarios to guess at. The actual topology is the
important thing to know. Whether something is wireless or if it uses a hub
or switch really doesn't matter.

--

Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com

Does no one have any suggestions about this?

Today the WLAN adapter failed and I thought that I could keep the

system

running

 

[Phillip Windell]

Basically I have 2 logical subnets on the same physical interface (the
interface connects to a single hub which has the original wired subnet and
my wireless gateway with a different subnet address on it). But none of the
clients on the second logical subnet can login (but they could when the
second subnet had its own NIC). I'm guessing its something along the lines
of NETLOGON not binding to the second address on a single card but thats
just taking a wild stab in the dark. Its certainly not a connectivity issue
as the clients can ping the server and get on the web etc they just cant
authenticate to the server for some reason

I'm in the process of trying to replace the second NIC (too complicated) but
I need to get this running in the meantime

What you are trying to do is much more complicated than just replacing the
bad Nic. Just replace the bad nic and be done with it.

 

[Ash Ridley]

Unfortunately the NIC is onboard in a 1U rack server and cannot be replaced
without a full system board replacement (and its not under warranty).

I am trying to organise this but its going to take a few days and I really
need to get the other subnet working.

Are you saying this cant be done?

 

[Phillip Windell]

Unfortunately the NIC is onboard in a 1U rack server and cannot be replaced
without a full system board replacement (and its not under warranty).

Then disable the onboard Nic and install a real Nic.

I am trying to organise this but its going to take a few days and I really
need to get the other subnet working.

Are you saying this cant be done?

I'm saying that I don't think it can be. Your current experience with it
should make that obvious. With most of this stuff, it all works in a
straight-forward way,...it you have to invent "rocket science" to make
something work then you are probably doing it wrong.

 

[Ash Ridley]

Unfortunately, since its a 1U rack server there are no free PCI slots

 

[Phillip Windell]

Unfortunately, since its a 1U rack server there are no free PCI slots

Then you *do* have a problem. In answer to your last question,...no. I do
not believe what you attempting can ever be made to work,...I cannot
document every tiny detail of "why" or "why not",...but I think you are
wasting your time.

I would consider a rack mount server like this to be a bad hardware design
for a device that might be considered "mission critical" unless everyone
kept and entire spare "complete" unit around,..and that is kinda expensive
to do.

 

[Marcel]

I'm in the process of trying to replace the second NIC (too complicated)
but
I need to get this running in the meantime

If you really need a second interface in short time, plug in a USB nic and
use it for your second subnet. Another option is to use a small router
between the subnets and remove the settings for the second net from your
server.

Marcel

 

[Phillip Windell]

That would be a good idea. I personally hate anything USB, but for a
situation like this that could be a good band-ade until the hardware problem
can be fixed.

 

[Ash Ridley]

Thanks for the suggestion, unfortunately the server doesnt have USB (nor any
free slots to install it) but the router option is a possibility