• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 184
  • Last Modified:

Problems Changing Windows SBS DC IP

History:
We needed to change the IP scheme for a network to allow new equipment to be utilized on the network. The new equipment does not allow the network to remain 192.168.1.0. We decided on changing it to a 10.0.1.0 network.

Problem:
We did the research on changing IPs on DC, and we completed the IP Scheme change and 1 of the DC will not allow you to ping it by name or IP from any of the clients. You can ping the clients from the server, but you can't ping the server from any of the clients.

Issue:
We know this is an AD/ DNS issue but we can't resolve it.

What we have done.
We cleared dns cache. cleared arp tables. restarted dns. purged the old 192 a records. verified the new server a records. attempted to use the sbs change ip utility which failed. attempted to force replication between dc which failed-it gave a DNS error.

HELP!!!!

0
marine7275
Asked:
marine7275
  • 7
  • 6
1 Solution
 
Jay_Jay70Commented:
Hi marine7275,

have you registered DNS?

when you run nslookup on the server, can you resolve yourself?

Cheers!
0
 
marine7275Author Commented:
Can you direct me how to??
0
 
marine7275Author Commented:
nslookup resolves with correct info from server
0
Restore individual SQL databases with ease

Veeam Explorer for Microsoft SQL Server delivers an easy-to-use, wizard-driven interface for restoring your databases from a backup. No expert SQL background required. Web interface provides a complete view of all available SQL databases to simplify the recovery of lost database

 
Jay_Jay70Commented:
marine7275,

alright so DNS is registered   what do the event logs say on the server

and whats the error you get when you try and ping the server from the client  - does it time out or give an error
0
 
marine7275Author Commented:
Criticals errors from ad. Is there any way to force an update for dns besdies restarting dns?

Also, you interested in talking with us to assist us? We are at a client and only have 5 hours to get this working.
0
 
marine7275Author Commented:
The error from the client is that it times out.
0
 
Jay_Jay70Commented:
no firewall services installed and enabled that myabe blocking?

any use of DHCP?
0
 
marine7275Author Commented:
we disabled windows firewall. The Watchguard firewall is doing DHCP for the network.
0
 
Jay_Jay70Commented:
is that firewall blocking any incoming ICMP requests or anthing like that    when you changed the IP address   did you edit it in the firewall?
0
 
marine7275Author Commented:
no the firewall seems to be ok.

Here is the latest:
We removed dns and wins from the server and then re-installed it. When we reboot, we can actually ping the server for about 3 mins until it finishes preparing network connections. Then the ping times out. We have tried another nic, cable switch,etc. no luck.

any ideers?
0
 
Jay_Jay70Commented:
have you run dcdiag on your DC? might be worth narrowing down a few possibilities
0
 
marine7275Author Commented:
Jay Jay - I really appreciate the help. We ended up calling MS to resolve the issue. You were right! It was a ISA firewall issue. It retained old network information in the LAT. We updated it and it worked! I really appreicate all the late night assistance.
0
 
Jay_Jay70Commented:
thats no problem my friend, glad you were able to resolve :)
0

Featured Post

Free Tool: Subnet Calculator

The subnet calculator helps you design networks by taking an IP address and network mask and returning information such as network, broadcast address, and host range.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

  • 7
  • 6
Tackle projects and never again get stuck behind a technical roadblock.
Join Now