|
Home > Archive > alt.certification.mcse > August 2003 > SUBNET QUESTION
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
|
|
|
| Please help:
Domain1 consists of 2 NT 4 Servers, one a PDC and one a BDC. There are 8
Workstations in the domain.
The IP range is from 192.1.165.1 to 192.1.165.255.
The subnet mask is 255.255.255.0.
The Default Gateway is 192.1.165.X (this is a router interface).
Although DNS is employed on the network, it is supplied by another part of
the company and is used purely for internet name resolution. There are no
entries for any of the devices in DNS. Name resolution is done via the HOST
and ALMOST files.
Domain1 has expanded to another site and is on a different subnet:
The IP range is from 192.1.166.1 to 192.1.166.255.
The subnet mask is 255.255.255.0.
The Default Gateway is 192.1.166.X (this is a router interface).
15 Windows XP professional workstations are to be connected to Domain1.
The problem:
From one of the XP devices you can ping both Default Gateways and the Domain
controller. However when you try to join the domain an error message comes
back saying "the domain "Domain1" cant be contacted, either it is not
available or does not exist" (or word to that effect).
There is an entry in LMHOST file on the XP box's:
192.1.165.XX SERVER1 #PRE #DOM OMAIN1
Having looked on other newsgroups one possible problem may be that a route
has not been set-up on the routers to enable the two subnets to communicate.
If this is so, can I check this from the XP workstations ? (the routers are
managed by a third party)
Any comments or suggestions would be greatly appreciated
TIA
Jim
| |
| Michael O'Neill 2003-08-21, 4:32 pm |
| make sure you make forward lookup zones
"Jimbo" <Jim@garner21.freeserve.co.uk> wrote in message
news:bi0h6i$8ga$1@newsg2.svr.pol.co.uk...
> Please help:
>
> Domain1 consists of 2 NT 4 Servers, one a PDC and one a BDC. There are 8
> Workstations in the domain.
>
> The IP range is from 192.1.165.1 to 192.1.165.255.
> The subnet mask is 255.255.255.0.
> The Default Gateway is 192.1.165.X (this is a router interface).
>
> Although DNS is employed on the network, it is supplied by another part of
> the company and is used purely for internet name resolution. There are no
> entries for any of the devices in DNS. Name resolution is done via the
HOST
> and ALMOST files.
>
> Domain1 has expanded to another site and is on a different subnet:
>
> The IP range is from 192.1.166.1 to 192.1.166.255.
> The subnet mask is 255.255.255.0.
> The Default Gateway is 192.1.166.X (this is a router interface).
>
> 15 Windows XP professional workstations are to be connected to Domain1.
>
> The problem:
>
> From one of the XP devices you can ping both Default Gateways and the
Domain
> controller. However when you try to join the domain an error message comes
> back saying "the domain "Domain1" cant be contacted, either it is not
> available or does not exist" (or word to that effect).
>
> There is an entry in LMHOST file on the XP box's:
>
> 192.1.165.XX SERVER1 #PRE #DOMOMAIN1
>
> Having looked on other newsgroups one possible problem may be that a route
> has not been set-up on the routers to enable the two subnets to
communicate.
> If this is so, can I check this from the XP workstations ? (the routers
are
> managed by a third party)
>
> Any comments or suggestions would be greatly appreciated
>
> TIA
>
> Jim
>
>
>
>
>
| |
| Sparky 2003-08-22, 9:25 am |
|
"Jimbo" <Jim@garner21.freeserve.co.uk> wrote in message
news:bi0h6i$8ga$1@newsg2.svr.pol.co.uk...
> Please help:
>
> From one of the XP devices you can ping both Default Gateways and the
Domain
> controller.
>
If you can ping the machine, then an IP route exists.
>
> However when you try to join the domain an error message comes
> back saying "the domain "Domain1" cant be contacted, either it is not
> available or does not exist" (or word to that effect).
>
> There is an entry in LMHOST file on the XP box's:
>
> 192.1.165.XX SERVER1 #PRE #DOMOMAIN1
>
> Having looked on other newsgroups one possible problem may be that a route
> has not been set-up on the routers to enable the two subnets to
communicate.
> If this is so, can I check this from the XP workstations ? (the routers
are
> managed by a third party)
>
I assuming that you have replaced ".XX" in the above entry, with the
decimal value of the final octet for the address. If you have not, that is
your problem. However, seeing that your router is managed by a third
party, one probable cause may be that they have blocked the ports for
NetBIOS Service over TCP/UDP. Please check to see that the router does not
block traffic to any of the following ports:
NetBIOS Name Service: port 137/TCP & UDP
NetBIOS Datagram Service: port 138/UDP
NetBIOS Session services: port 139/TCP
Additionally, WINS uses port 42 to exchange NetBIOS name databases.
You may wish to familiarize yourself with NetBIOS Service over TCP/UDP. It
is outlined in RFCs 1001 and 1002. While Microsoft's (MS) implementation is
superset of this specification, these two RFCs will give you a greater
understanding of what is going on under the hood. You need to remember that
file and print is implement using the SMB protocol, and it was originally
designed to operate over NetBIOS. While W2K and XP can send SMB traffic
directly over TCP (via port 445), NT still uses NetBIOS (either NetBEUI or
NetBIOS over TCP/UDP).
Hopefully, this information will get you started in the right direction. :-)
|
|
|
|
|