Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Westi on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Client connections to W2K Server from another subnet.

Status
Not open for further replies.

pessimist

Technical User
May 6, 2003
9
CA
Good Morning

Our network in our company has changed a little. The old system had just one router that all traffic went thru, now the new system has a router for each building. I am not the person responsible for the changes to the network, nore do I have control how it is implemented. Each building has its own subnet as well. XXX.XXX.23.1 and XXX.XXX.38.1 for example

My question is how do I configure my Windows 2000 Server with DNS installed to allow clients in another building to authenticate and move data between my server and the client system. I have been told that I will have to make changes to the DNS settings to allow my client system to see the server.

Right now the server points to itself

Client machines are all XP pro.
Windows 2000 Server - domain controler
(Will be upgrading to Windows 2003 Server Standard in the next couple months.
Active Directory installed.
Forward Lookup Zone has only the server listed
- only secrue updates
- active directory-integrated
- name servers (only the one server listed- itself)
- no zone transfers listed
- WINS forward lookup not listed

I'm sure that I need a lot more information to allow you to advise me, but am not sure what is required. Please give me list of required information and I will post.

Thanks in advance for your help
 
You should only have to assign a new IP Address and Subnet Mask(if required) to the machines that are on the new subnet(s). If your DC/DNS server subnet has not changed, no change required on the server.

You would only be required to make DNS A record changes to hosts that do not support dynamic DNS. Since you are using XP workstatins, confirm dynamic DNS updates are enabled in your TCP/IP properties.

Other than that, if you are still having issues - ask the network team if they have an ACL that may be blocking port 53 from being routed.
 
The server will also have its subnet changed to match the new subnet for the building along with all the client stations in this building and the other ones.
 
Then you will need to change the DNS ip within your clients TCP/IP settings to point to the DNS servers new IP Address.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top