zenportafino
asked on
Server has only one eye
I have a development server that is also used for SUS updates. SUS stopped working when I added a new NIC and site. The new site address is .55 and the SUS server is .9. All systems can see our intranet on .9 but if I'm at the dev server and I put in http://servername, I get the .55 site.
I unchecked dynamic update on the .55 NIC and verified that there are no .55 entries in DNS. I put in a record in the hosts file as well pointing http://servername to .9 - still goes to the .55 site. I've been told that if the SUS server can't see it's own site that it won't work. How can I force this server to look at .9 when pointed to http://servername??
I unchecked dynamic update on the .55 NIC and verified that there are no .55 entries in DNS. I put in a record in the hosts file as well pointing http://servername to .9 - still goes to the .55 site. I've been told that if the SUS server can't see it's own site that it won't work. How can I force this server to look at .9 when pointed to http://servername??
Also, if you have more DNS servers, make sure to flush on all servers and/or do a Synchronisation.
*********I put in a record in the hosts file as well pointing http://servername to .9
try putting "servername .9" in the lmhosts file (make sure it saves as just lmhosts not lmhosts.txt)
also try putting "servername.domain.domain .9" into the hosts file (checking the filename as above)
then try accessing the server using both http://servername and http://servername.domain.domain if the entries are correct both of these should then point to .9 - this can be checked by pinging servername & servername.domain.domain at the command prompt
you need to edit the hosts file on the machine you are using to access the server (.9) - check youre not using a proxy
check the DNS domain of the machine you are trying to access from - then in that domain take a look for a host record "servername" make sure its not set to 55 - if using ddns then just delete the entry and create it manually (referencing .9)
if you cant ping the name and get the correct ip resolved at the command prompt - it will never work
try putting "servername .9" in the lmhosts file (make sure it saves as just lmhosts not lmhosts.txt)
also try putting "servername.domain.domain .9" into the hosts file (checking the filename as above)
then try accessing the server using both http://servername and http://servername.domain.domain if the entries are correct both of these should then point to .9 - this can be checked by pinging servername & servername.domain.domain at the command prompt
you need to edit the hosts file on the machine you are using to access the server (.9) - check youre not using a proxy
check the DNS domain of the machine you are trying to access from - then in that domain take a look for a host record "servername" make sure its not set to 55 - if using ddns then just delete the entry and create it manually (referencing .9)
if you cant ping the name and get the correct ip resolved at the command prompt - it will never work
ASKER
Did/checked all of the above and it still goes to .55 so I disabled the .55 NIC and it goes to .9. Yeah!
When I re enable the NIC it still goes to .9 for about a minute then goes over to .55. Boo!
Again, this is only on the server that has cards .9 and .55. All client and server systems go to .9 which corresponds with a records on the DNS server.
The way I am verifying this is by pinging the server by name and by opening up http://servername - both always correlating. I wonder if there is a way to use the route command to force the .55 address with a higher metric and if that would work.
When I re enable the NIC it still goes to .9 for about a minute then goes over to .55. Boo!
Again, this is only on the server that has cards .9 and .55. All client and server systems go to .9 which corresponds with a records on the DNS server.
The way I am verifying this is by pinging the server by name and by opening up http://servername - both always correlating. I wonder if there is a way to use the route command to force the .55 address with a higher metric and if that would work.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I works!! I never saw the "advanced" pull down in network places. Totally psycho! Thanks again rahandels. Know anything about Veritas logon account issues?
ASKER
By the way, no need to place a route in the table. The advanced tab was the trick.
Hi Zenportafino.
Nice to know that it works. It justed kinda popped into my head... We had to install a server once and on the paper it was stated that you had to reconfigure the order. I searched for over an hour to find it. Microsoft is so nice to let use search where they put their stuff now... ;)
But no, i don't know anything about Veritas logon account issues. I assume you mean the back-up software??? You could try and post a new thread in the Storage area.
Nice to know that it works. It justed kinda popped into my head... We had to install a server once and on the paper it was stated that you had to reconfigure the order. I searched for over an hour to find it. Microsoft is so nice to let use search where they put their stuff now... ;)
But no, i don't know anything about Veritas logon account issues. I assume you mean the back-up software??? You could try and post a new thread in the Storage area.
Did you flush the dns cache?