Re: Old Server can stil Ping

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance



Hello ,

Thank you for posting.

From your post, my understanding on this issue is: You have found that you
can 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.
This server runs a sql 2000 db as well. I followed the procedure to
complete
the name change in sql as well. Its been a few days since the name
change.
I can still ping the old server name. How can this be? Why would the
server
still be pinged even though the computer name does not exists in AD. I
run
a Windows 2000 Domain. This server is a Windows 2003 member server. I
don't
see it in DNS but I do see it in WINS. It has an expiration date of
tomarrow
at 11:00 pm. IS there any way to force this out of my network. I don't
want
anyone to be able to reference the server by the new name which you
currently
can do. It will cause problems because this server is running Sharepoint
team services web site.




.



Relevant Pages

  • Re: Name resolution vs. multiple NICs
    ... Not, they cannot ping that name, not even on the same machine. ... For example I may have a private DNS server that will ... > discover the correct FQDN. ... can resolve the name on the computer you run it on. ...
    (microsoft.public.win32.programmer.networks)
  • Re: Setting up NS2
    ... I recieve "Cannot find host" when I ping the FQDN NS2.nameserver.com. ... not believe my DNS is being updated throughout the inet. ... The hosted domains I have on the server do not resolve and will not until I ...
    (microsoft.public.windows.server.dns)
  • Re: RDP can not logon error
    ... Tracert & Ping to dc on the same subnet as the server that is having trouble. ... No network provider accepted the given network path.. ... Starting test: CrossRefValidation ...
    (microsoft.public.windows.server.general)
  • Re: Cannot connect to Server
    ... Test 1 - the clients can ping one anotehr ... gpupdate/force - reboot both client and server - ping to server from client ... Suggestion 2 - ping to server works when running safe mode with networking ...
    (microsoft.public.windows.server.sbs)
  • Re: The specified network name is nolonger available
    ... My server is named FS1. ... > ping \\fs1 and I will get a successful return. ... I still can access the drives marked ... What is the point in these permissions as they can be bypassed by mapping ...
    (microsoft.public.win2000.networking)