Windows 2000 Server

[Hoober]

Depends on your setup. Do you have a router? If so, you don't need both NICs. If you're using your 2K server box to handle DHCP and routing for your network to the internet then you need to configure your server to do all that stuff.

That's how I was going to do it before I decided to keep the router. So I just removed the second NIC from my server, reinstalled 2K Server (because I wanted to) and now everything works great.

 

[jurek2000]

Yes I have a router . But when I unplugged the other nic card I was still getting the same errors . Do I need to completly uninstall it ?

 

[Woodie]

It's a timing issue. The cached record of the second nic has to get flushed from the routing tables.

Reboot everything.

--Woodie

 

[Woodie]

jurek2000:

If you're running W2K, you can assign different DNS domain names to the different nics. So:

Nic #1:
IP addy from broadband supplier, Internet DNS server, hostname is "Neptune", domain is rr.com (FQDN=neptune.rr.com). This nic is wired to DSL router.

Nic #2:
Private IP addy (192.168.x.x), Local (or Internet) DNS server, hostname is still "Neptune", connection-specific domain is planets.local (FQDN=neptune.planets.local). This nic is wired to internal hub/router.
Note: All the other LAN computers should have ip addresses on the same (private) subnet.

Clients: (behind neptune)
Their default gateway should be neptune.planets.local
DNS server can be either internal or external.
IP addy's must be on the same private subnet.
Netmask must be identical.
NEPTUNE needs to have IP forwarding turned on. (routes the packets from private nic to external nic.

--Woodie

 

[Hoober]

I'm trying to understand this Woodie -- he needs two domains in order to get it to work right? Or a subdomain (whatever they're called) under the larger domain for the internal network? And why not just one domain for the whole thing?

Thanks

 

[jurek2000]

You are the man Woodie....this solution works perfect for my setup and it has solved that duplicate name on the network.
What you think may solve unability to access my server from other workstation , gives a message "the server does not accept any more connections....."

thank you for your help !!!

 

[Woodie]

Hoober:
Two seperate domain names, means no "Duplicate name" errors, since they're different names, with different IP addresses. The error occurs because you have the same name (FQDN) with two different IP addresses. It confuses the router. Does it make sense now?

jurek2000:
You're having the licensing issue. This occurs w/ Server only (Client is hard-coded to 10 I think). Check licensing mode (Per seat/per server), the number of licenses there, and also the number of connections per share (make them unlimited).

--Woodie

 

[Hoober]

Makes a lot more sense. Thanks.

 

[Shadow07]

I always turn off the Licensing Manager service. Also, when you setup DNS, make sure that you enable DNS FORWARDING. You can do this by going in tot he DNS MMC, going to the PROPERTIES of the server name, clicking on FORWARDING, and then putting your ISP's DNS servers IP address(es) here. Then, everything internally should be pointing to your internal DNS server. Also, if you happen to find a "." domain zone listed in your DNS server, delete it.

Also, if you do want to have two NIC's attached to the same logical and physical network, you will need to make sure that you turn off NetBIOS on one of the NIC's and that the DNS name on the two NIC's are completely different. Now you can use W2KS-1 and W2KS-2 as the completely different names.

Hope that helps.

Let me know if you have any further questions.

 

[jurek2000]

When I turned of the license logging service I still can't connect to the server from my workstation "Server cannot accept any more conections....." I have another problem with messages upon boot of my server regarding L2TP connection. "A certificate could not be found . Connections that use L2TP protocol over IPsec require the installation of a machine certificate.No L2TP calls will be accepted".

Thank you for all help,

Jurek

 

[Tallgeese]

<< Yayyyy.

Dual nics can definately be tricky. Much better behaved when they're used for routing traffic between different subnets. >>

As per MS TechNet Article ID: Q175767

We actually do use multi-port NICs in our servers at work. They support special &quot;teaming&quot; functions which, when attached to correctly configured ports on our Cisco switches, give us the benefit of both redundancy and increased bandwidth.

NOT for the faint-of-heart, tho. Hideously complex configurations (on both switch and server) and load commands (for our Novell box anyway).

 

[Shadow07]

To resolve you L2TP/IPSec issue, you will need a Certificate Authority to issue certificates. This is why IPSec has a higher encryption scheme than PPTP. By using certificates, you essentially have a PKI (Public Key Infrastructure). You will either need to install the CA in your domain, or goto Verisign and see if they can &quot;host&quot; a CA for you.

Make sure that you have the default setting on the share for the total amount of users. This is UNLIMITED. If that still doesn't work, then un-share the folder, then re-share it.

 

[Woodie]

I don't think you really want to do LTP2/IPSec with certs. PKI's are a real PITA, and you'll want to think a lot before you decide to do one.

BTDT, and I didn't even get a t-shirt.

--Woodie