Discussion Locked

Intranet site going to old IP address

0 helpful
9 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
We have recently changed our IP numbering configuation and now our intranet site keeping looking for the old IP address. We have gone into the server (Proliant CL1850) Windows 2000 and have changed all the IP addresses we could find and when we do the IPCONFIG /ALL the IP addresses are correct. The individual that set up this server is no longer with our company and has not responded to our inquiries. Where else can we look so that our intranet isn't looking at the wrong IP address. FYI: The internet works.

9 replies

by gnet158

It may be a static route configuration in your routers. If the IP is configured correctly then that's were I'd start. If it's not a static route then reboot your switches and that should clear the route tables.

by some guy in seattle

Try these places:

- is the old address/hostname still on the DNS server?

- check your WINS server, if you have one, and tombstone the old information if there

- on the proliant under \\winnt\system32\drivers\etc, check the hosts and lmhostsfiles for the old information and update if necessary (will need to reboot)

hope that helps,

by rcc

There is a problem with your name resolution. See what ping returns when you try pinging the name. In your browser, try requesting the IP address instead of name, see if you get to the site. If you do, check your name servers (DNS and WINS) for a static entry: In dns look for an A or C record pointing to your web server. In WINS, check for static record in your database pointing to your server. It will also be good to look for a host or lmhost file. just to make sure wrong name resolution is not coming from there.
Regards,
Radu
I hope this helps

by raffi_

Isn't neccessarily a DNS problem. The IP may be hardcoded into IIS. Open the IIS MMC and select you site in the left window. Right click and select Properties. The window that opens will show you the IP ADDRESS: either All Unassigned or a number. Make sure that it points to your new IP.

Regards
SF

by mary.schingeck

Thanks for everyone's input. The problem was a combination of everything including the cluster server not being configured correctly. We ended up going through Microsoft support for help that lasted almost one week.

This discussion is closed to new replies.