From: Ace Fekay [MVP-DS, MCT] on
"Cameron Shaw" <camerons(a)newsgroup.nospam> wrote in message
news:eybkjIgnKHA.4392(a)TK2MSFTNGP05.phx.gbl...
>I didn't, just dns...Next time it happens. I'll try that. Have you heard of
>something like this before.


I've heard of something like this before when the DNS settings are not
correct, including if the DNS settings included an ISP's DNS or the router
as a DNS address, but you are trying to ping an internal machine by its
internal FQDN name. Another reason is the Primary DNS Suffix may not have
been set correctly for the internal domain, therefore leaving the Search
Suffix blank, resulting in when trying to ping by single name, it had
nothing to suffix the name with, therefore nothing to lookup in DNS.

For all practical purposes, to check internal communication, first run an
ipconfig /all. Make sure the Primary DNS Suffix is correct for the domain
(which will populate when you join the machine or manually setting it), the
subnet mask is correct, the DNS addresses are ONLY pointing to internal DNS
server(s), and the gateway is correct.

Then ping itself to make sure the networking services are running, then ping
the gateway. If both ping by IP, then try pinging a name. If name resolution
fails, then go back and look at your DNS and other settings I've mentioned.
If trying to connect by RDP and not responding by IP, then that could mean
you haven't allowed RDP into the system. It's off by default on a fresh
installation.

Also check your Windows Firewall settings. If not sure of the settings,
simply disable all firewalls on the machine for testing. If it works, hence
there's the issue.

Also check your Event logs for any possible errors.

If you could post an ipconfig /all (unedited, of course), of this machine
and a working internal machine, that can help provide a starting point
towards a more specific diagnosis. Also post event log errors, if
applicable.

--
Ace

This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

Please reply back to the newsgroup or forum for collaboration benefit among
responding engineers, and to help others benefit from your resolution.

Ace Fekay, MVP, MCT, MCITP EA, MCTS Windows 2008 & Exchange 2007, MCSE &
MCSA 2003/2000, MCSA Messaging 2003
Microsoft Certified Trainer
Microsoft MVP - Directory Services

If you feel this is an urgent issue and require immediate assistance, please
contact Microsoft PSS directly. Please check http://support.microsoft.com
for regional support phone numbers.


From: Dave Patrick on
Yes, if by address works then it is more than likely a DNS issue. If it
fails then I'd replace the network interface.



--

Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

"Cameron Shaw" wrote:
>I didn't, just dns...Next time it happens. I'll try that. Have you heard of
>something like this before.

From: David Shen [MSFT] on
Hello customer,

The managed support service of the microsoft.public.windows.server.general
is now available instead on General forum:
http://social.technet.microsoft.com/Forums/en-US/winservergen/threads.
Would you please repost the question in the forum with the Windows Live ID
used to access your Subscription benefits? Our engineers will assist you in
the new platform.

The web link http://technet.microsoft.com/en-us/subscriptions/ms788697.aspx
introduces more information about the migration. In the future, please post
your Print-related questions directly to the forums. If you have any
questions or concerns, please feel free to contact us: tngfb(a)microsoft.com

David Shen
Microsoft Online Technical Support

From: Nime on
Here someone -an employee- did a shortcircuit on an 8 port switch, say port 2 and port 7 were "connected".
It was really difficult to fix (found) the problem. At server, one of two NIC card couldnt ping anywhere.



"Cameron Shaw" <camerons(a)newsgroup.nospam>, iletide �unu yazd� news:eybkjIgnKHA.4392(a)TK2MSFTNGP05.phx.gbl...
> I didn't, just dns...Next time it happens. I'll try that. Have you heard of something like this before.
> "Dave Patrick" <DSPatrick(a)nospam.gmail.com> wrote in message news:OSZPBXfnKHA.1304(a)TK2MSFTNGP06.phx.gbl...
>> "Will not respond to ping/rdp"
>>
>> Have you also tried by address?
>>


From: Ace Fekay [MVP-DS, MCT] on
"Nime" <eminakbulut(a)gmail.com> wrote in message
news:D5CFD164-7685-43C6-AA83-778826662865(a)microsoft.com...
> Here someone -an employee- did a shortcircuit on an 8 port switch, say
> port 2 and port 7 were "connected".
> It was really difficult to fix (found) the problem. At server, one of two
> NIC card couldnt ping anywhere.
>


If someone jumped two ports on the same switch, I wouldn't call it short
circuiting, rather it introduced a feedback to itself, for a lack of a
better word. All traffic being sent out on the one port was going back to
itself causing a problem with the switch's alorithm to handle the traffic,
essentially not knowing what to do with it. I've seen older switches do the
same with two NICs that are teamed, not able to handle it, causing a traffic
surge.

Ace