Huge problem joining windows 2003 domain

  • Thread starter Thread starter antiparadox@gmail.com
  • Start date Start date
A

antiparadox@gmail.com

Guest
Okay the situation is as follows, I have a network that looks like
this,

http://i9.tinypic.com/54adu29.jpg

as you can, I do not have a switch, and on each PC there are 2 NIC's,
so on each PC there's 2 UTP cables coming in.

PC1 and PC3 are my clients running windows XP professional
PC2 is my server running windows 2003 server

The NIC's on my server are configured as follows,

Adapter : LAN1

Host Name. . . . . . . . . : Myserver
IP Address . . . . . . . . : 192.168.2.80
Subnet Mask. . . . . . . . : 255.255.255.0
Default Gateway. . . . . . :
Dns Servers. . . . . . . . : 192.168.2.80

Adapter : LAN2

Host Name. . . . . . . . . : Myserver
IP Address . . . . . . . . : 192.168.2.83
Subnet Mask. . . . . . . . : 255.255.255.0
Default Gateway. . . . . . :
Dns Servers. . . . . . . . : 192.168.2.80

And the NIC on PC1 is configured as follows,

Adapter : PC1

Host Name. . . . . . . . . : Myclient1
IP Address . . . . . . . . : 192.168.2.82
Subnet Mask. . . . . . . . : 255.255.255.0
Default Gateway. . . . . . :
Dns Servers. . . . . . . . : 192.168.2.80

And the NIC on PC3 is configured as follows,

Adapter : PC3

Host Name. . . . . . . . . : Myclient3
IP Address . . . . . . . . : 192.168.2.81
Subnet Mask. . . . . . . . : 255.255.255.0
Default Gateway. . . . . . :
Dns Servers. . . . . . . . : 192.168.2.80

The problem I am having now is as follows, PC3 can join the domain
without any problem whatsoever, I just go to SYSTEM PROPERTIES,
COMPUTERNAME, click the CHANGE button, fill in my domain and poof it
says, Welcome to the domain plz restart your computer. When I do this
same thing on PC1 it just doesn't work, then it gives me following
error,

Note: This information is intended for a network administrator. If
you are not your network's administrator, notify the administrator
that you received this information, which has been recorded in the
file C:\WINDOWS\debug\dcdiag.txt.

The following error occurred when DNS was queried for the service
location (SRV) resource record used to locate a domain controller for
domain fileserver.local:

The error was: "DNS name does not exist."
(error code 0x0000232B RCODE_NAME_ERROR)

The query was for the SRV record for _ldap._tcp.dc._msdcs.mydomain.com

Common causes of this error include the following:

- The DNS SRV records required to locate a domain controller for the
domain are not registered in DNS. These records are registered with a
DNS server automatically when a domain controller is added to a
domain. They are updated by the domain controller at set intervals.
This computer is configured to use DNS servers with following IP
addresses:

192.168.2.80

- One or more of the following zones do not include delegation to its
child zone:

mydomain.com
local
.. (the root zone)

As a result, I cannot join my domain, now here's the kicker of the
story, when I change around the network cables on my server, and I
plug the cable coming from PC1 in LAN1, and I plug the cable coming
from PC3 in LAN2 then all of a sudden PC1 can join the domain without
any problem???? But if I do it like this, then PC3 will end up having
the same problems PC1 was having.


How in God's name do you configure DNS when you have 2 NIC's on your
server, cuz its clear to me the problem is with me having 2 NIC's. I'm
not an expert in this, so plz steer me in the right direction, I
really want this problem sorted. Someone told me this was the right
place to ask with lots of knowledgeable people:)

thnx
 
Re: Huge problem joining windows 2003 domain

hello,

what a funny (dirty dirty) network ;)

Does the 2 pc need to communicate each other ? (hope no)


I have some tips for you, but this design is REALLY poor...for god, buy a
switch !

First, you should change your network mask:

192.168.2.X for PC1 and server
192.168.3.X for pc2 and server.

So the server will send good packets through the good network card.

Then you must be sure your Server has its two ip in the dns.

That's dirty and bad even this way...

--
Cordialement,
Mathieu CHATEAU
http://lordoftheping.blogspot.com


<antiparadox@gmail.com> wrote in message
news:1187641157.619053.261210@w3g2000hsg.googlegroups.com...
> Okay the situation is as follows, I have a network that looks like
> this,
>
> http://i9.tinypic.com/54adu29.jpg
>
> as you can, I do not have a switch, and on each PC there are 2 NIC's,
> so on each PC there's 2 UTP cables coming in.
>
> PC1 and PC3 are my clients running windows XP professional
> PC2 is my server running windows 2003 server
>
> The NIC's on my server are configured as follows,
>
> Adapter : LAN1
>
> Host Name. . . . . . . . . : Myserver
> IP Address . . . . . . . . : 192.168.2.80
> Subnet Mask. . . . . . . . : 255.255.255.0
> Default Gateway. . . . . . :
> Dns Servers. . . . . . . . : 192.168.2.80
>
> Adapter : LAN2
>
> Host Name. . . . . . . . . : Myserver
> IP Address . . . . . . . . : 192.168.2.83
> Subnet Mask. . . . . . . . : 255.255.255.0
> Default Gateway. . . . . . :
> Dns Servers. . . . . . . . : 192.168.2.80
>
> And the NIC on PC1 is configured as follows,
>
> Adapter : PC1
>
> Host Name. . . . . . . . . : Myclient1
> IP Address . . . . . . . . : 192.168.2.82
> Subnet Mask. . . . . . . . : 255.255.255.0
> Default Gateway. . . . . . :
> Dns Servers. . . . . . . . : 192.168.2.80
>
> And the NIC on PC3 is configured as follows,
>
> Adapter : PC3
>
> Host Name. . . . . . . . . : Myclient3
> IP Address . . . . . . . . : 192.168.2.81
> Subnet Mask. . . . . . . . : 255.255.255.0
> Default Gateway. . . . . . :
> Dns Servers. . . . . . . . : 192.168.2.80
>
> The problem I am having now is as follows, PC3 can join the domain
> without any problem whatsoever, I just go to SYSTEM PROPERTIES,
> COMPUTERNAME, click the CHANGE button, fill in my domain and poof it
> says, Welcome to the domain plz restart your computer. When I do this
> same thing on PC1 it just doesn't work, then it gives me following
> error,
>
> Note: This information is intended for a network administrator. If
> you are not your network's administrator, notify the administrator
> that you received this information, which has been recorded in the
> file C:\WINDOWS\debug\dcdiag.txt.
>
> The following error occurred when DNS was queried for the service
> location (SRV) resource record used to locate a domain controller for
> domain fileserver.local:
>
> The error was: "DNS name does not exist."
> (error code 0x0000232B RCODE_NAME_ERROR)
>
> The query was for the SRV record for _ldap._tcp.dc._msdcs.mydomain.com
>
> Common causes of this error include the following:
>
> - The DNS SRV records required to locate a domain controller for the
> domain are not registered in DNS. These records are registered with a
> DNS server automatically when a domain controller is added to a
> domain. They are updated by the domain controller at set intervals.
> This computer is configured to use DNS servers with following IP
> addresses:
>
> 192.168.2.80
>
> - One or more of the following zones do not include delegation to its
> child zone:
>
> mydomain.com
> local
> . (the root zone)
>
> As a result, I cannot join my domain, now here's the kicker of the
> story, when I change around the network cables on my server, and I
> plug the cable coming from PC1 in LAN1, and I plug the cable coming
> from PC3 in LAN2 then all of a sudden PC1 can join the domain without
> any problem???? But if I do it like this, then PC3 will end up having
> the same problems PC1 was having.
>
>
> How in God's name do you configure DNS when you have 2 NIC's on your
> server, cuz its clear to me the problem is with me having 2 NIC's. I'm
> not an expert in this, so plz steer me in the right direction, I
> really want this problem sorted. Someone told me this was the right
> place to ask with lots of knowledgeable people:)
>
> thnx
>
 
Re: Huge problem joining windows 2003 domain

Hello antiparadox@gmail.com,

For a pc pc connection you have to use cross cables, so check that both network
cables are crossed. I think one of them is straight.

And you should really think about buying a switch, they are not expensive
and it will make the live easier.

Also you have to configure a default gateway, otherwise you can not connect
over the router to the internet, if you will do that.

So my recommendation would be, buy a switch, configure youre network like
this:

Server: IP 192.168.2.80 SM 255.255.255.0 DNS 192.168.2.80 DG 192.168.2.1
(also the router has to get this ip ofcourse)
PC1 IP 192.168.2.81 SM 255.255.255.0 DNS 192.168.2.80 DG 192.168.2.1
PC3 IP 192.168.2.82 SM 255.255.255.0 DNS 192.168.2.80 DG 192.168.2.1

All 3 machines connected with one NIC to the switch.

The DNS server has to become a Forwarder for the ISP's DNS.

Best regards

Meinolf Weber (Myweb)
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.

> Okay the situation is as follows, I have a network that looks like
> this,
>
> http://i9.tinypic.com/54adu29.jpg
>
> as you can, I do not have a switch, and on each PC there are 2 NIC's,
> so on each PC there's 2 UTP cables coming in.
>
> PC1 and PC3 are my clients running windows XP professional PC2 is my
> server running windows 2003 server
>
> The NIC's on my server are configured as follows,
>
> Adapter : LAN1
>
> Host Name. . . . . . . . . : Myserver
> IP Address . . . . . . . . : 192.168.2.80
> Subnet Mask. . . . . . . . : 255.255.255.0
> Default Gateway. . . . . . :
> Dns Servers. . . . . . . . : 192.168.2.80
> Adapter : LAN2
>
> Host Name. . . . . . . . . : Myserver
> IP Address . . . . . . . . : 192.168.2.83
> Subnet Mask. . . . . . . . : 255.255.255.0
> Default Gateway. . . . . . :
> Dns Servers. . . . . . . . : 192.168.2.80
> And the NIC on PC1 is configured as follows,
>
> Adapter : PC1
>
> Host Name. . . . . . . . . : Myclient1
> IP Address . . . . . . . . : 192.168.2.82
> Subnet Mask. . . . . . . . : 255.255.255.0
> Default Gateway. . . . . . :
> Dns Servers. . . . . . . . : 192.168.2.80
> And the NIC on PC3 is configured as follows,
>
> Adapter : PC3
>
> Host Name. . . . . . . . . : Myclient3
> IP Address . . . . . . . . : 192.168.2.81
> Subnet Mask. . . . . . . . : 255.255.255.0
> Default Gateway. . . . . . :
> Dns Servers. . . . . . . . : 192.168.2.80
> The problem I am having now is as follows, PC3 can join the domain
> without any problem whatsoever, I just go to SYSTEM PROPERTIES,
> COMPUTERNAME, click the CHANGE button, fill in my domain and poof it
> says, Welcome to the domain plz restart your computer. When I do this
> same thing on PC1 it just doesn't work, then it gives me following
> error,
>
> Note: This information is intended for a network administrator. If
> you are not your network's administrator, notify the administrator
> that you received this information, which has been recorded in the
> file C:\WINDOWS\debug\dcdiag.txt.
>
> The following error occurred when DNS was queried for the service
> location (SRV) resource record used to locate a domain controller for
> domain fileserver.local:
>
> The error was: "DNS name does not exist."
> (error code 0x0000232B RCODE_NAME_ERROR)
> The query was for the SRV record for _ldap._tcp.dc._msdcs.mydomain.com
>
> Common causes of this error include the following:
>
> - The DNS SRV records required to locate a domain controller for the
> domain are not registered in DNS. These records are registered with a
> DNS server automatically when a domain controller is added to a
> domain. They are updated by the domain controller at set intervals.
> This computer is configured to use DNS servers with following IP
> addresses:
>
> 192.168.2.80
>
> - One or more of the following zones do not include delegation to its
> child zone:
>
> mydomain.com
> local
> . (the root zone)
> As a result, I cannot join my domain, now here's the kicker of the
> story, when I change around the network cables on my server, and I
> plug the cable coming from PC1 in LAN1, and I plug the cable coming
> from PC3 in LAN2 then all of a sudden PC1 can join the domain without
> any problem???? But if I do it like this, then PC3 will end up having
> the same problems PC1 was having.
>
> How in God's name do you configure DNS when you have 2 NIC's on your
> server, cuz its clear to me the problem is with me having 2 NIC's. I'm
> not an expert in this, so plz steer me in the right direction, I
> really want this problem sorted. Someone told me this was the right
> place to ask with lots of knowledgeable people:)
>
> thnx
>
 
Re: Huge problem joining windows 2003 domain

On Aug 20, 10:29 pm, "Mathieu CHATEAU" <gollum...@free.fr> wrote:
> hello,
>
> what a funny (dirty dirty) network ;)
>
> Does the 2 pc need to communicate each other ? (hope no)
>
> I have some tips for you, but this design is REALLY poor...for god, buy a
> switch !
>
> First, you should change your network mask:
>
> 192.168.2.X for PC1 and server
> 192.168.3.X for pc2 and server.
>
> So the server will send good packets through the good network card.
>
> Then you must be sure your Server has its two ip in the dns.
>
> That's dirty and bad even this way...
>
> --
> Cordialement,
> Mathieu CHATEAUhttp://lordoftheping.blogspot.com


Hahahahah yeah I know it is dirty, but I am a cheapass who didn't want
to fork out extra cash for a switch, but with you again confirming
this is dirty dirty bad bad boystuff I will go out and buy one. PC1
and PC3 don't need to communicate to each other no, so I thought I
could set it up like this, but in the end it gave me more headaches
then its worth. I can access my fileshares from PC1 though, but I have
to go through a loophole where I have to join my domain via the SYSTEM
PROPERTIES, COMPUTERNAME, and there I have to click the NETWORK ID
button and go through 3 screens of providing details(admin password,
domain, then again username and domain and finally domain user who may
join computers to a domain), and then I can join my PC1 to the domain.
But its a bad fix because,

a) I can't ping my server, nor on the computername, nor on the IP, nor
on the domainname
b) many netdiag tests will just fail, like the DC test, trust test,
DNS tests, etc

Remote desktop only works when I supply PC1 with the IP of the NIC its
connected to(so in my case 192.168.2.83).

And as a matter a fact, my first try with this network was the way you
described it, to have,

192.168.2.X for PC1 and server
192.168.3.X for pc2 and server

and I had exactly the same problems I am describing now. Before I had
it like this,

NIC's on the server

Adapter : LAN1


Host Name. . . . . . . . . : Myserver
IP Address . . . . . . . . : 192.168.2.80
Subnet Mask. . . . . . . . : 255.255.255.0
Default Gateway. . . . . . :
Dns Servers. . . . . . . . : 192.168.2.80


Adapter : LAN2


Host Name. . . . . . . . . : Myserver
IP Address . . . . . . . . : 192.168.3.80
Subnet Mask. . . . . . . . : 255.255.255.0
Default Gateway. . . . . . :
Dns Servers. . . . . . . . : 192.168.2.80


And the NIC on PC1 was configured as follows,


Adapter : PC1


Host Name. . . . . . . . . : Myclient1
IP Address . . . . . . . . : 192.168.3.81
Subnet Mask. . . . . . . . : 255.255.255.0
Default Gateway. . . . . . :
Dns Servers. . . . . . . . : 192.168.2.80


And the NIC on PC3 was configured as follows,


Adapter : PC3


Host Name. . . . . . . . . : Myclient3
IP Address . . . . . . . . : 192.168.2.81
Subnet Mask. . . . . . . . : 255.255.255.0
Default Gateway. . . . . . :
Dns Servers. . . . . . . . : 192.168.2.80

But since you'r the second person now who is hammering me about my
poor choice of network, I will order a switch tomorrow and then I'll
just rebuild my DNS from scratch cuz it probably doesn't know its head
from its arse anymore:LOL:

thnx for your valuable input,

Cupid
 
Re: Huge problem joining windows 2003 domain

You messed up here:

Adapter : PC1


Host Name. . . . . . . . . : Myclient1
IP Address . . . . . . . . : 192.168.3.81
Subnet Mask. . . . . . . . : 255.255.255.0
Default Gateway. . . . . . :
Dns Servers. . . . . . . . : 192.168.2.80


That must be 192.168.3.80 as dns, or PC1 won't be able to join dns (the
other network is not reachable without a gateway)


--
Cordialement,
Mathieu CHATEAU
http://lordoftheping.blogspot.com


<antiparadox@gmail.com> wrote in message
news:1187643394.571577.286570@22g2000hsm.googlegroups.com...
> On Aug 20, 10:29 pm, "Mathieu CHATEAU" <gollum...@free.fr> wrote:
>> hello,
>>
>> what a funny (dirty dirty) network ;)
>>
>> Does the 2 pc need to communicate each other ? (hope no)
>>
>> I have some tips for you, but this design is REALLY poor...for god, buy a
>> switch !
>>
>> First, you should change your network mask:
>>
>> 192.168.2.X for PC1 and server
>> 192.168.3.X for pc2 and server.
>>
>> So the server will send good packets through the good network card.
>>
>> Then you must be sure your Server has its two ip in the dns.
>>
>> That's dirty and bad even this way...
>>
>> --
>> Cordialement,
>> Mathieu CHATEAUhttp://lordoftheping.blogspot.com
>
>
> Hahahahah yeah I know it is dirty, but I am a cheapass who didn't want
> to fork out extra cash for a switch, but with you again confirming
> this is dirty dirty bad bad boystuff I will go out and buy one. PC1
> and PC3 don't need to communicate to each other no, so I thought I
> could set it up like this, but in the end it gave me more headaches
> then its worth. I can access my fileshares from PC1 though, but I have
> to go through a loophole where I have to join my domain via the SYSTEM
> PROPERTIES, COMPUTERNAME, and there I have to click the NETWORK ID
> button and go through 3 screens of providing details(admin password,
> domain, then again username and domain and finally domain user who may
> join computers to a domain), and then I can join my PC1 to the domain.
> But its a bad fix because,
>
> a) I can't ping my server, nor on the computername, nor on the IP, nor
> on the domainname
> b) many netdiag tests will just fail, like the DC test, trust test,
> DNS tests, etc
>
> Remote desktop only works when I supply PC1 with the IP of the NIC its
> connected to(so in my case 192.168.2.83).
>
> And as a matter a fact, my first try with this network was the way you
> described it, to have,
>
> 192.168.2.X for PC1 and server
> 192.168.3.X for pc2 and server
>
> and I had exactly the same problems I am describing now. Before I had
> it like this,
>
> NIC's on the server
>
> Adapter : LAN1
>
>
> Host Name. . . . . . . . . : Myserver
> IP Address . . . . . . . . : 192.168.2.80
> Subnet Mask. . . . . . . . : 255.255.255.0
> Default Gateway. . . . . . :
> Dns Servers. . . . . . . . : 192.168.2.80
>
>
> Adapter : LAN2
>
>
> Host Name. . . . . . . . . : Myserver
> IP Address . . . . . . . . : 192.168.3.80
> Subnet Mask. . . . . . . . : 255.255.255.0
> Default Gateway. . . . . . :
> Dns Servers. . . . . . . . : 192.168.2.80
>
>
> And the NIC on PC1 was configured as follows,
>
>
> Adapter : PC1
>
>
> Host Name. . . . . . . . . : Myclient1
> IP Address . . . . . . . . : 192.168.3.81
> Subnet Mask. . . . . . . . : 255.255.255.0
> Default Gateway. . . . . . :
> Dns Servers. . . . . . . . : 192.168.2.80
>
>
> And the NIC on PC3 was configured as follows,
>
>
> Adapter : PC3
>
>
> Host Name. . . . . . . . . : Myclient3
> IP Address . . . . . . . . : 192.168.2.81
> Subnet Mask. . . . . . . . : 255.255.255.0
> Default Gateway. . . . . . :
> Dns Servers. . . . . . . . : 192.168.2.80
>
> But since you'r the second person now who is hammering me about my
> poor choice of network, I will order a switch tomorrow and then I'll
> just rebuild my DNS from scratch cuz it probably doesn't know its head
> from its arse anymore:LOL:
>
> thnx for your valuable input,
>
> Cupid
>
 
Re: Huge problem joining windows 2003 domain

On Aug 20, 11:08 pm, "Mathieu CHATEAU" <gollum...@free.fr> wrote:
> You messed up here:
>
> Adapter : PC1
>
> Host Name. . . . . . . . . : Myclient1
> IP Address . . . . . . . . : 192.168.3.81
> Subnet Mask. . . . . . . . : 255.255.255.0
> Default Gateway. . . . . . :
> Dns Servers. . . . . . . . : 192.168.2.80
>
> That must be 192.168.3.80 as dns, or PC1 won't be able to join dns (the
> other network is not reachable without a gateway)

I tried adding 192.168.3.80 to Myclient1's DNS servers(as an alternate
dns server), but that didn't work, probably because I don't know what
I should do on my server to make 192.168.3.80 a DNS IP as well. I
still am gonna buy a switch, but would love to know how I could have
set up that second DNS server, when I click on MANAGE MY SERVER, it
doesn't open the wizard anymore so I can't enter 192.168.3.80
anywhere. Do I need to add a bunch of records to my forward lookup
zone, but which ones, NS records, SOA, SRV, pointer records, A
records, or whatever is in there.

So when I get my switch can I set it up like this,

http://i14.tinypic.com/5zfbtsj.jpg

so PC1 and PC3 are getting their internet from the router, and for my
internal LAN I am using the switch and only one NIC will be used on my
server? Or do you really need a gateway, and do I absolutely have to
do it like this,

So my recommendation would be, buy a switch, configure youre network
like
this:


Server: IP 192.168.2.80 SM 255.255.255.0 DNS 192.168.2.80 DG
192.168.2.1
(also the router has to get this ip ofcourse)
PC1 IP 192.168.2.81 SM 255.255.255.0 DNS 192.168.2.80 DG
192.168.2.1
PC3 IP 192.168.2.82 SM 255.255.255.0 DNS 192.168.2.80 DG
192.168.2.1


Because remember, I don't want my server connected to the internet,
only PC1 and PC3 should have internet access.
 
Re: Huge problem joining windows 2003 domain

hello,
connect your router on your switch.

Your station won't be able to surf, as their dns (your dc), won't be abe to
resolve google & co.

Your server will need internet access for windows update & co..
that is false security to think it is protected without having internet
access.
Real security practice is not surf on the web from your server.


--
Cordialement,
Mathieu CHATEAU
http://lordoftheping.blogspot.com


<antiparadox@gmail.com> wrote in message
news:1187646413.752719.216550@50g2000hsm.googlegroups.com...
> On Aug 20, 11:08 pm, "Mathieu CHATEAU" <gollum...@free.fr> wrote:
>> You messed up here:
>>
>> Adapter : PC1
>>
>> Host Name. . . . . . . . . : Myclient1
>> IP Address . . . . . . . . : 192.168.3.81
>> Subnet Mask. . . . . . . . : 255.255.255.0
>> Default Gateway. . . . . . :
>> Dns Servers. . . . . . . . : 192.168.2.80
>>
>> That must be 192.168.3.80 as dns, or PC1 won't be able to join dns (the
>> other network is not reachable without a gateway)
>
> I tried adding 192.168.3.80 to Myclient1's DNS servers(as an alternate
> dns server), but that didn't work, probably because I don't know what
> I should do on my server to make 192.168.3.80 a DNS IP as well. I
> still am gonna buy a switch, but would love to know how I could have
> set up that second DNS server, when I click on MANAGE MY SERVER, it
> doesn't open the wizard anymore so I can't enter 192.168.3.80
> anywhere. Do I need to add a bunch of records to my forward lookup
> zone, but which ones, NS records, SOA, SRV, pointer records, A
> records, or whatever is in there.
>
> So when I get my switch can I set it up like this,
>
> http://i14.tinypic.com/5zfbtsj.jpg
>
> so PC1 and PC3 are getting their internet from the router, and for my
> internal LAN I am using the switch and only one NIC will be used on my
> server? Or do you really need a gateway, and do I absolutely have to
> do it like this,
>
> So my recommendation would be, buy a switch, configure youre network
> like
> this:
>
>
> Server: IP 192.168.2.80 SM 255.255.255.0 DNS 192.168.2.80 DG
> 192.168.2.1
> (also the router has to get this ip ofcourse)
> PC1 IP 192.168.2.81 SM 255.255.255.0 DNS 192.168.2.80 DG
> 192.168.2.1
> PC3 IP 192.168.2.82 SM 255.255.255.0 DNS 192.168.2.80 DG
> 192.168.2.1
>
>
> Because remember, I don't want my server connected to the internet,
> only PC1 and PC3 should have internet access.
>
 
Re: Huge problem joining windows 2003 domain

Hello Mathieu,

I think the same way and that's the reason that i recommend you the ip configuration.

Best regards

Meinolf Weber (Myweb)
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.

> hello,
> connect your router on your switch.
> Your station won't be able to surf, as their dns (your dc), won't be
> abe to resolve google & co.
>
> Your server will need internet access for windows update & co..
> that is false security to think it is protected without having
> internet
> access.
> Real security practice is not surf on the web from your server.
> <antiparadox@gmail.com> wrote in message
> news:1187646413.752719.216550@50g2000hsm.googlegroups.com...
>
>> On Aug 20, 11:08 pm, "Mathieu CHATEAU" <gollum...@free.fr> wrote:
>>
>>> You messed up here:
>>>
>>> Adapter : PC1
>>>
>>> Host Name. . . . . . . . . : Myclient1
>>> IP Address . . . . . . . . : 192.168.3.81
>>> Subnet Mask. . . . . . . . : 255.255.255.0
>>> Default Gateway. . . . . . :
>>> Dns Servers. . . . . . . . : 192.168.2.80
>>> That must be 192.168.3.80 as dns, or PC1 won't be able to join dns
>>> (the other network is not reachable without a gateway)
>>>
>> I tried adding 192.168.3.80 to Myclient1's DNS servers(as an
>> alternate dns server), but that didn't work, probably because I don't
>> know what I should do on my server to make 192.168.3.80 a DNS IP as
>> well. I still am gonna buy a switch, but would love to know how I
>> could have set up that second DNS server, when I click on MANAGE MY
>> SERVER, it doesn't open the wizard anymore so I can't enter
>> 192.168.3.80 anywhere. Do I need to add a bunch of records to my
>> forward lookup zone, but which ones, NS records, SOA, SRV, pointer
>> records, A records, or whatever is in there.
>>
>> So when I get my switch can I set it up like this,
>>
>> http://i14.tinypic.com/5zfbtsj.jpg
>>
>> so PC1 and PC3 are getting their internet from the router, and for my
>> internal LAN I am using the switch and only one NIC will be used on
>> my server? Or do you really need a gateway, and do I absolutely have
>> to do it like this,
>>
>> So my recommendation would be, buy a switch, configure youre network
>> like
>> this:
>> Server: IP 192.168.2.80 SM 255.255.255.0 DNS 192.168.2.80 DG
>> 192.168.2.1
>> (also the router has to get this ip ofcourse)
>> PC1 IP 192.168.2.81 SM 255.255.255.0 DNS 192.168.2.80
>> DG
>> 192.168.2.1
>> PC3 IP 192.168.2.82 SM 255.255.255.0 DNS 192.168.2.80
>> DG
>> 192.168.2.1
>> Because remember, I don't want my server connected to the internet,
>> only PC1 and PC3 should have internet access.
>>
 
Re: Huge problem joining windows 2003 domain

Okay roger that, thnx Meinolf and Mathieu, I'll do it the suggested
way:)
 
Back
Top