is ISP not recognised?

When two lan cards are accepted, why can't we tell server, this is for isp
and don't take it as servers for our network, you look at the other card.
With the cable of isp on, I cant define my server as the first. When my
server is connected to my client pc, why is not the network complete? Any
help?

Having two network connections to a server has always been a problem,
because it means that you have two different addresses associated with the
server's name.

You can solve the problem for Netbios names by disabling Netbios over
TCP/IP on the card on the public side (ie the one connected to your ISP).
For DNS names, check that the public NIC does not register its name in your
local DNS.

When a machine on the local LAN needs to contact the server it will try
to resolve the server's name to its IP address. It is important that it
always gets the address of the private NIC. How do your clients resolve
names to IP addresses? Do they use the local DNS server?

"dindigul" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> When two lan cards are accepted, why can't we tell server, this is for isp
> and don't take it as servers for our network, you look at the other card.
> With the cable of isp on, I cant define my server as the first. When my
> server is connected to my client pc, why is not the network complete? Any
> help?
>
>
>
>

In news:(E-Mail Removed),
dindigul <(E-Mail Removed)> typed:
> When two lan cards are accepted, why can't we tell server, this is
> for isp and don't take it as servers for our network, you look at the
> other card. With the cable of isp on, I cant define my server as the
> first. When my server is connected to my client pc, why is not the
> network complete? Any help?

Get a router/firewall appliance and use a single NIC in your server, and
your life will be a lot easier. And your network will likely be quite a bit
more secure.