Server with 2 Network Cards + cannot browse domain

I have just set up a new server running 2003 Server Standard. I have three
network cards on the server: a 10/100 which is disabled and 2 Gigabit cards
each with a class B ip address. All the clients on my network currently run
win2k and winxp and all have class b ip addresses. I have set-up Active
Directory (this is the first domain) which installed & automatically
configured Routing and Remote Access on both network cards. I installed and
configured DNS, DHCP & Wins.

My problem is on WinXP & Win2K machines. I can add them to the network and
have DHCP configured for them. Internet browsing works fine but I cannot
browse the network from these computers - I constantly get this error when
double clicking on the domain:

----------------------
Domain is not accessible. You might not have permission to use this network
resource. Contact the administrator of this server to find out if you have
access permissions.
The list of servers for this workgroup is not currently available.
----------------------

I am still able to map folders by their ip address and ping to the server
and the other computers on the network. I also tried the same settings with
ICF turned off on the XP clients and also have NetBios enabled over TCP/IP.

Any ideas?

Regards,
Brian

Do you have a particular reason for having two NICs enabled (presumably
in the same IP subnet)? This will cause no end of problems with the browser
service. I would also disable RRAS unless you have a particular reason to
use it (ie either routing or remote access). It will do nothing but cause
problems with two NICs in the same subnet.

"Brian" <briandelicata@?no-spam?hotmail.com> wrote in message
news:%(E-Mail Removed)...
>I have just set up a new server running 2003 Server Standard. I have three
>network cards on the server: a 10/100 which is disabled and 2 Gigabit cards
>each with a class B ip address. All the clients on my network currently run
>win2k and winxp and all have class b ip addresses. I have set-up Active
>Directory (this is the first domain) which installed & automatically
>configured Routing and Remote Access on both network cards. I installed and
>configured DNS, DHCP & Wins.
>
> My problem is on WinXP & Win2K machines. I can add them to the network and
> have DHCP configured for them. Internet browsing works fine but I cannot
> browse the network from these computers - I constantly get this error when
> double clicking on the domain:
>
> ----------------------
> Domain is not accessible. You might not have permission to use this
> network resource. Contact the administrator of this server to find out if
> you have access permissions.
> The list of servers for this workgroup is not currently available.
> ----------------------
>
> I am still able to map folders by their ip address and ping to the server
> and the other computers on the network. I also tried the same settings
> with ICF turned off on the XP clients and also have NetBios enabled over
> TCP/IP.
>
> Any ideas?
>
> Regards,
> Brian
>

The server was shipped with three network cards and since it will be the
domain controller, have dns, wins etc running on it I thought that
configuring two network cards might ease the networking load - though on
second thoughts there will only be around 40 client machines connected. And
yes both network cards are configured on the same subnet.

Will try your suggestion and disable one of the nic's & RRAS and see if I
will get any more master browser issues.

Brian

"Bill Grant" <not.available@online> wrote in message
news:OFGZg8$(E-Mail Removed)...
> Do you have a particular reason for having two NICs enabled (presumably
> in the same IP subnet)? This will cause no end of problems with the
> browser service. I would also disable RRAS unless you have a particular
> reason to use it (ie either routing or remote access). It will do nothing
> but cause problems with two NICs in the same subnet.
>
> "Brian" <briandelicata@?no-spam?hotmail.com> wrote in message
> news:%(E-Mail Removed)...
>>I have just set up a new server running 2003 Server Standard. I have three
>>network cards on the server: a 10/100 which is disabled and 2 Gigabit
>>cards each with a class B ip address. All the clients on my network
>>currently run win2k and winxp and all have class b ip addresses. I have
>>set-up Active Directory (this is the first domain) which installed &
>>automatically configured Routing and Remote Access on both network cards.
>>I installed and configured DNS, DHCP & Wins.
>>
>> My problem is on WinXP & Win2K machines. I can add them to the network
>> and have DHCP configured for them. Internet browsing works fine but I
>> cannot browse the network from these computers - I constantly get this
>> error when double clicking on the domain:
>>
>> ----------------------
>> Domain is not accessible. You might not have permission to use this
>> network resource. Contact the administrator of this server to find out if
>> you have access permissions.
>> The list of servers for this workgroup is not currently available.
>> ----------------------
>>
>> I am still able to map folders by their ip address and ping to the server
>> and the other computers on the network. I also tried the same settings
>> with ICF turned off on the XP clients and also have NetBios enabled over
>> TCP/IP.
>>
>> Any ideas?
>>
>> Regards,
>> Brian
>>
>
>

If you are running WINS, check that there are not any stale records left
behind for the domain master browser (ie domainname 1B) pointing to the
"wrong" IP address.

"Brian" <briandelicata@?no-spam?hotmail.com> wrote in message
news:(E-Mail Removed)...
> The server was shipped with three network cards and since it will be the
> domain controller, have dns, wins etc running on it I thought that
> configuring two network cards might ease the networking load - though on
> second thoughts there will only be around 40 client machines connected.
> And yes both network cards are configured on the same subnet.
>
> Will try your suggestion and disable one of the nic's & RRAS and see if I
> will get any more master browser issues.
>
> Brian
>
> "Bill Grant" <not.available@online> wrote in message
> news:OFGZg8$(E-Mail Removed)...
>> Do you have a particular reason for having two NICs enabled (presumably
>> in the same IP subnet)? This will cause no end of problems with the
>> browser service. I would also disable RRAS unless you have a particular
>> reason to use it (ie either routing or remote access). It will do nothing
>> but cause problems with two NICs in the same subnet.
>>
>> "Brian" <briandelicata@?no-spam?hotmail.com> wrote in message
>> news:%(E-Mail Removed)...
>>>I have just set up a new server running 2003 Server Standard. I have
>>>three network cards on the server: a 10/100 which is disabled and 2
>>>Gigabit cards each with a class B ip address. All the clients on my
>>>network currently run win2k and winxp and all have class b ip addresses.
>>>I have set-up Active Directory (this is the first domain) which installed
>>>& automatically configured Routing and Remote Access on both network
>>>cards. I installed and configured DNS, DHCP & Wins.
>>>
>>> My problem is on WinXP & Win2K machines. I can add them to the network
>>> and have DHCP configured for them. Internet browsing works fine but I
>>> cannot browse the network from these computers - I constantly get this
>>> error when double clicking on the domain:
>>>
>>> ----------------------
>>> Domain is not accessible. You might not have permission to use this
>>> network resource. Contact the administrator of this server to find out
>>> if you have access permissions.
>>> The list of servers for this workgroup is not currently available.
>>> ----------------------
>>>
>>> I am still able to map folders by their ip address and ping to the
>>> server and the other computers on the network. I also tried the same
>>> settings with ICF turned off on the XP clients and also have NetBios
>>> enabled over TCP/IP.
>>>
>>> Any ideas?
>>>
>>> Regards,
>>> Brian
>>>
>>
>>
>
>

"Brian" <briandelicata@?no-spam?hotmail.com> wrote in message
news:(E-Mail Removed)...
> The server was shipped with three network cards and since it will be the
> domain controller, have dns, wins etc running on it I thought that
> configuring two network cards might ease the networking load - though on

No it won't. Run only one NIC.


272294 - Active Directory Communication Fails on Multihomed Domain
Controllers
http://support.microsoft.com/default...b;en-us;272294

191611 - Symptoms of Multihomed Browsers
http://support.microsoft.com/default...b;EN-US;191611

175767 - Expected Behavior of Multiple Adapters on Same Network
http://support.microsoft.com/default...b;EN-US;175767

157025 - Default Gateway Configuration for Multihomed Computers
http://support.microsoft.com/default...roduct=win2000

--

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

I reconfigured the server today and got everything working whilst disabling
the other two nic's. I even tried to set up the server by using the nic
teaming but was still getting some errors when browsing the domain.

Now with this setup I cannot enable ICF since it is the domain controller -
enabling ICF on the server results in all clients not able to access the
server. Are there any other options (maybe by re-enabling one of the
disabled network cards) to re-enable icf to shield it from the internet)?

Brian

ICF is for home users. They should have never included it in the "server"
version of the OS, it just confuses people. Assuming this is the server
version of the OS use RRAS's NAT features.

To handle the Nics properly run only two. Make sure the LAN Nic remains at
the "top" of the priority list. The second Nic should only have TCP/IP bound
to it but nothing else ( no MS Networking, no F/P Sharing). The priority
list is found in the properties of Network Places, then "Advanced" from the
menu at the top and then "Advanced Settings..." from the dropdown
menu,...then the list is in the upper "box",...use the side arrows to
adjust.

How the second one (Internet one) is configured depends on what kind of
Internet connection you have and what kind of hardware you use to interface
with the Line.

(Same for 2003)
299801 - HOW TO: Configure a Windows 2000 Server as a Network Address
Translation Server
http://support.microsoft.com/default...;en-us;Q299801

310357 - HOW TO: Configure the NAT Service in Windows 2000
http://support.microsoft.com/default...b;en-us;310357


--

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


"Brian" <briandelicata@?no-spam?hotmail.com> wrote in message
news:%(E-Mail Removed)...
> I reconfigured the server today and got everything working whilst
disabling
> the other two nic's. I even tried to set up the server by using the nic
> teaming but was still getting some errors when browsing the domain.
>
> Now with this setup I cannot enable ICF since it is the domain
controller -
> enabling ICF on the server results in all clients not able to access the
> server. Are there any other options (maybe by re-enabling one of the
> disabled network cards) to re-enable icf to shield it from the internet)?
>
> Brian
>
>

Sorry, I was thinking of ICS instead of ICF. Yes, ICF can cause problems on
the DC as you described.


--

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

"Phillip Windell" <@.> wrote in message
news:(E-Mail Removed)...
> ICF is for home users. They should have never included it in the "server"
> version of the OS, it just confuses people. Assuming this is the server
> version of the OS use RRAS's NAT features.
>
> To handle the Nics properly run only two. Make sure the LAN Nic remains at
> the "top" of the priority list. The second Nic should only have TCP/IP
bound
> to it but nothing else ( no MS Networking, no F/P Sharing). The priority
> list is found in the properties of Network Places, then "Advanced" from
the
> menu at the top and then "Advanced Settings..." from the dropdown
> menu,...then the list is in the upper "box",...use the side arrows to
> adjust.
>
> How the second one (Internet one) is configured depends on what kind of
> Internet connection you have and what kind of hardware you use to
interface
> with the Line.
>
> (Same for 2003)
> 299801 - HOW TO: Configure a Windows 2000 Server as a Network Address
> Translation Server
> http://support.microsoft.com/default...;en-us;Q299801
>
> 310357 - HOW TO: Configure the NAT Service in Windows 2000
> http://support.microsoft.com/default...b;en-us;310357
>
>
> --
>
> Phillip Windell [MCP, MVP, CCNA]
> www.wandtv.com
>
>
> "Brian" <briandelicata@?no-spam?hotmail.com> wrote in message
> news:%(E-Mail Removed)...
> > I reconfigured the server today and got everything working whilst
> disabling
> > the other two nic's. I even tried to set up the server by using the nic
> > teaming but was still getting some errors when browsing the domain.
> >
> > Now with this setup I cannot enable ICF since it is the domain
> controller -
> > enabling ICF on the server results in all clients not able to access the
> > server. Are there any other options (maybe by re-enabling one of the
> > disabled network cards) to re-enable icf to shield it from the
internet)?
> >
> > Brian
> >
> >
>
>

Thanks for the note Philip.

This was the original setup I wanted to have but was having a lot of master
browser issues once I enabled two network cards on the server. This is the
first server on the network and am using Class B IP addresses (this is a
college setup). All the clients (around 40) have a class B IP address which
I cannot change since it enables them to use the resources outside the
college.

So my problem right now is that the server is not shielded from any attacks
other than the router which blocks some inbound traffic. I cannot lock down
the router since it will disable a lot of apps running on the client
machines.

If I enable another network card for ICF on the server what settings should
I put in since it will also have a class B ip?

Brian


"Phillip Windell" <@.> wrote in message
news:(E-Mail Removed)...
> ICF is for home users. They should have never included it in the "server"
> version of the OS, it just confuses people. Assuming this is the server
> version of the OS use RRAS's NAT features.
>
> To handle the Nics properly run only two. Make sure the LAN Nic remains at
> the "top" of the priority list. The second Nic should only have TCP/IP
> bound
> to it but nothing else ( no MS Networking, no F/P Sharing). The priority
> list is found in the properties of Network Places, then "Advanced" from
> the
> menu at the top and then "Advanced Settings..." from the dropdown
> menu,...then the list is in the upper "box",...use the side arrows to
> adjust.
>
> How the second one (Internet one) is configured depends on what kind of
> Internet connection you have and what kind of hardware you use to
> interface
> with the Line.
>
> (Same for 2003)
> 299801 - HOW TO: Configure a Windows 2000 Server as a Network Address
> Translation Server
> http://support.microsoft.com/default...;en-us;Q299801
>
> 310357 - HOW TO: Configure the NAT Service in Windows 2000
> http://support.microsoft.com/default...b;en-us;310357
>
>
> --
>
> Phillip Windell [MCP, MVP, CCNA]
> www.wandtv.com
>
>
> "Brian" <briandelicata@?no-spam?hotmail.com> wrote in message
> news:%(E-Mail Removed)...
>> I reconfigured the server today and got everything working whilst
> disabling
>> the other two nic's. I even tried to set up the server by using the nic
>> teaming but was still getting some errors when browsing the domain.
>>
>> Now with this setup I cannot enable ICF since it is the domain
> controller -
>> enabling ICF on the server results in all clients not able to access the
>> server. Are there any other options (maybe by re-enabling one of the
>> disabled network cards) to re-enable icf to shield it from the internet)?
>>
>> Brian
>>
>>
>
>

Well, I think you are a bit screwed. You are trying to take what might be
consided a bad design (or at least an insecure design) and make it behave as
if it is a good design.

No one should ever use actual Public IP#s within the private
network,...*especially* schools with a bunch of "brats" on the machines.
You should run Private IP#s for the protected machines and use at *least*
some kind of NAT Device to "translate" between the Public and Private side
of the system.

I am assuming when you say Class B you mean an address block the school
actually owns, and when you say Router you really mean a *real* router and
not an Internet NAT device. The dictionary has been horribly butered in
recent times by the SOHO Cable/DSL "[so called] router" market.

--

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


"Brian" <briandelicata@?no-spam?hotmail.com> wrote in message
news:%(E-Mail Removed)...
> Thanks for the note Philip.
>
> This was the original setup I wanted to have but was having a lot of
master
> browser issues once I enabled two network cards on the server. This is the
> first server on the network and am using Class B IP addresses (this is a
> college setup). All the clients (around 40) have a class B IP address
which
> I cannot change since it enables them to use the resources outside the
> college.
>
> So my problem right now is that the server is not shielded from any
attacks
> other than the router which blocks some inbound traffic. I cannot lock
down
> the router since it will disable a lot of apps running on the client
> machines.
>
> If I enable another network card for ICF on the server what settings
should
> I put in since it will also have a class B ip?
>
> Brian
>
>
> "Phillip Windell" <@.> wrote in message
> news:(E-Mail Removed)...
> > ICF is for home users. They should have never included it in the
"server"
> > version of the OS, it just confuses people. Assuming this is the server
> > version of the OS use RRAS's NAT features.
> >
> > To handle the Nics properly run only two. Make sure the LAN Nic remains
at
> > the "top" of the priority list. The second Nic should only have TCP/IP
> > bound
> > to it but nothing else ( no MS Networking, no F/P Sharing). The priority
> > list is found in the properties of Network Places, then "Advanced" from
> > the
> > menu at the top and then "Advanced Settings..." from the dropdown
> > menu,...then the list is in the upper "box",...use the side arrows to
> > adjust.
> >
> > How the second one (Internet one) is configured depends on what kind of
> > Internet connection you have and what kind of hardware you use to
> > interface
> > with the Line.
> >
> > (Same for 2003)
> > 299801 - HOW TO: Configure a Windows 2000 Server as a Network Address
> > Translation Server
> > http://support.microsoft.com/default...;en-us;Q299801
> >
> > 310357 - HOW TO: Configure the NAT Service in Windows 2000
> > http://support.microsoft.com/default...b;en-us;310357
> >
> >
> > --
> >
> > Phillip Windell [MCP, MVP, CCNA]
> > www.wandtv.com
> >
> >
> > "Brian" <briandelicata@?no-spam?hotmail.com> wrote in message
> > news:%(E-Mail Removed)...
> >> I reconfigured the server today and got everything working whilst
> > disabling
> >> the other two nic's. I even tried to set up the server by using the nic
> >> teaming but was still getting some errors when browsing the domain.
> >>
> >> Now with this setup I cannot enable ICF since it is the domain
> > controller -
> >> enabling ICF on the server results in all clients not able to access
the
> >> server. Are there any other options (maybe by re-enabling one of the
> >> disabled network cards) to re-enable icf to shield it from the
internet)?
> >>
> >> Brian
> >>
> >>
> >
> >
>
>