Re: Old Server can stil Ping
- From: v-haozou@xxxxxxxxxxxxxxxxxxxx (Kenxl Zou (MSFT))
- Date: Thu, 09 Mar 2006 09:33:59 GMT
Hello ,
Thank you for posting.
From your post, my understanding on this issue is: You have found that youcan still ping the server name that had been changed already. You want to
know how to resolve this. If I'm off base, please feel free to let me know.
Based on my reseach, you may follow the steps below to troubleshoot this
problem:
1. Delete the WINS record related to the old server name
2. On the client computer where you initialize the ping, type "ipconfig
/flushdns" in the command
3. Try ping the old server name in FQDN format to see if it still can be
reached.
4. On the Windows 2003 member server check the NetBIOS name:
Right click on my "computer", select "Properties"
Select "Computer Name" tab, click "change"
In "Computer Name Changes" window, click "more", to see if the "NetBIOS
computer name" has been changed to the new name.
After you finish all the steps, please check the problem again.
Please let me know the result. I am looking forward to your reply.
Sincerely,
Kenxl Zou
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
=====================================================
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
From: "Phillip Windell" <@.>
References: <6A942D8A-B6F7-4CA6-9A28-DDA9D4A0B039@xxxxxxxxxxxxx>
Subject: Re: Old Server can stil Ping
Date: Wed, 8 Mar 2006 17:09:48 -0600
Lines: 29
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2800.1506
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1506
Message-ID: <O6TsmVwQGHA.4960@xxxxxxxxxxxxxxxxxxxx>
Newsgroups: microsoft.public.win2000.networking
NNTP-Posting-Host: wandtv-host15.decatur.hansoninfosys.com 209.16.209.143
Path: TK2MSFTNGXA03.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP12.phx.gbl
Xref: TK2MSFTNGXA03.phx.gbl microsoft.public.win2000.networking:89746
X-Tomcat-NG: microsoft.public.win2000.networking
Delete it out of WINS. Delete it,..don't just Tombstone it.
--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com
"George Schneider" <georgedschneider@xxxxxxxxxxxxxx> wrote in message
news:6A942D8A-B6F7-4CA6-9A28-DDA9D4A0B039@xxxxxxxxxxxxxxxx
I have a server I recently changed its name form oldserver to newserver.complete
This server runs a sql 2000 db as well. I followed the procedure to
the name change in sql as well. Its been a few days since the namechange.
I can still ping the old server name. How can this be? Why would theserver
still be pinged even though the computer name does not exists in AD. Irun
a Windows 2000 Domain. This server is a Windows 2003 member server. Idon't
see it in DNS but I do see it in WINS. It has an expiration date oftomarrow
at 11:00 pm. IS there any way to force this out of my network. I don'twant
anyone to be able to reference the server by the new name which youcurrently
can do. It will cause problems because this server is running Sharepoint
team services web site.
.
- Prev by Date: Re: no network provider accepted the given network path
- Next by Date: delete a file on www
- Previous by thread: VPN IP Address Conflict
- Next by thread: delete a file on www
- Index(es):
Relevant Pages
|