Computing.Net > Forums > Windows Server 2003 > unable to access server after changing the ip

Computer Problems? Computing.Net has over 1,000,000 posts about all things technology related! Over 90% answered within 24 hours! Click here to start participating now! Also, be sure to check out the New User Guide.

unable to access server after changing the ip

Reply to Message Icon

Name: akhilsah
Date: September 22, 2009 at 22:45:06 Pacific
OS: Windows server 2003
Subcategory: General
Comment:

my server is in win server 2003 in a domain and clients are in workgroup they are accessing each other successfully now i have change the ip of my server & clients from 192.168.0.x to 192.168.4.x but client are unable to access the server it gives request time out error but the server is pinging the clients now how i'll connect the client after changing the ip series



Sponsored Link
Ads by Google

Response Number 1
Name: Curt R
Date: September 23, 2009 at 07:46:34 Pacific
Reply:

Did you change the host records in DNS to reflect the IP change? If not, you'll definitely not be able to connect to it using the hostname of the server to connect.

A quick way to check if it's the DNS...........can you ping by IP but not by hostname? If yes, then it's the DNS.


0

Response Number 2
Name: Phatsta
Date: October 9, 2009 at 06:50:14 Pacific
Reply:

You changed the server to a different subnet, so as far as the clients are aware the server is gone. You need to change ip on clients as well (if you use static ip you have to do it manually but if you're using DHCP just change the scope).

The first three groups of numbers in the ip adress (192.168.4) is the subnet address and the last group is the host address. Hosts means clients, printers, servers etc, and in order to see each other they all need to be on the same subnet. Unless you use LAN routing which is a different story.


0

Response Number 3
Name: ace_omega
Date: October 9, 2009 at 08:46:51 Pacific
Reply:

You need both the DNS change and a routing change. Like said above you can not talk accross subnets with out setting up a static route or router to connect the different networks. You can simply do a

Route Add 192.168.4.0 mask 255.255.255.0 192.168.0.1

This is assuming your router is 192.168.0.1 and you are using /24 subnets.

You will also need to add the HOST (A) record as suggest above or you will not be able to use FQDN in your mappings.

Its best not to mess with your server IP unless you really know what your doing.


0

Sponsored Link
Ads by Google
Reply to Message Icon

Related Posts

See More






Use following form to reply to current message:

Login or Register to Reply
LoginRegister


Sponsored links

Ads by Google


Results for: unable to access server after changing the ip

Unable to access server by name www.computing.net/answers/windows-2003/unable-to-access-server-by-name/2196.html

Unable to access internet www.computing.net/answers/windows-2003/unable-to-access-internet-/2081.html

uanble to access server www.computing.net/answers/windows-2003/uanble-to-access-server/8166.html