Networks

Ask something
Discussion Locked

multihomed server boot up problem

0 helpful
6 replies

by 1i1m01e

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

hardware:
Windows 2000 server with service pack 1
3COM NIC card - Internet
Intel NIC card - internal network
software:
DNS
DHCP
WINS
winroute

I changed the IP settings on the 3COM NIC card and rebooted the server. During the bootup process, the window indicates "setting up network connections" but it doesn't continue to the CTRL-ALT-DEL window. I have to do a hard boot and enter into safe mode in order to disable the 3COM card. Then, the server will boot normally. After I logon, I can enable the 3COM card and access the Internet. The company that did the server installation installed Win Route in order for the internal network to have access to the Internet.

Why would the multihomed server have problems during the bootup process ?

Thanks in advance.

6 replies

by william jay

The slow startup is likely due to one or more of the nics looking FOR the dhcp server. And ... because winroute was likely set up AS that dhcp server ... .

Windows 2000 can do most of the things that winroute does, and is much better at some.
This may be the best time to consider the particulars of your network setup, with an eye to simplicity. Have you more protocols than needed? What is WINS actually doing for you? Is NetBeui installed on the workstations? Are there many workgroups? Are there many other servers? It may be possible to simplify the networkat this point, (down to tcp-ip, dhcp, and simple routing), but it depends somewhat on physical layout and more on what windows networking is used for in your particular case.
Before going further, decide wich services win2k will offer and which, if any, winroute will offer.

Winroute is fabulous in win9x for basic internet sharing and services, but it is duplicating services available "out of the box" with Windows 2000 products ...

Set up the server as normal to provide the desired services to your network on the first nic.
Setup the external nic to connect properly to the isp.
Configure and enable win2k routing and remote access services, which will create the bridge.

For more detailed info, or ways to keep winroute if you must, the please post a comment in this thread, or make contact ...

by william jay

If you still have WinRoute installed, lose it, the conflict is likey centered there because Win2K has NAT built-in ... it's called RRAS - Routing and Remote Access

by techdictator

Try updating the 3COM NIC driver, get the diagnostic drivers as this will help you if you continue to have problems. I'd also disable WinRoute to see if that fixes the problem. Check WinRoute's site on the internet for updates, FAQ, or knowledgebase.

This discussion is closed to new replies.