No ping to server

Hi,

We have fresh Windows Server 2003 Enterprise R2 with all updates installed
and configured as domain controller and application server. Hardware is
Supermicro X7DVL-E with Intel® (ESB2/Gilgal) 82563EB Dual-Port Gigabit
Ethernet Controller (PRO/1000).
Only one LAN port is used with static IP. The latest hardware drivers are
installed.

The problem is:
We can not ping or connect with Remote Desktop or another other mean until
we browse this machine in network (My Network Places/Entire Network/Microsoft
Windows Network/domain/computer). After we connect like this, we can work a
while, but when the machine's address is removed from ARP cache by timeout,
we lose connection again.

Like this: start pinging the machine getting "Request timeout", then open it
in network browser and ping becomes normal immediately after I see the
machine's shares.

We have tried all possible configurations with Firewall and Routing and
Remote Access on and off.

I'm afraid we ran out of ideas. Can you please help?

Regards,
Alex

Sounds like name resolution issue. Can you ping the server by IP before
browsing the network? Any error if using nslookup? Or this search result may
help.

Name Resolution

This is name resolution issue if you can ping IP but not computer name
.... The ping command uses Windows Sockets-style name resolution to resolve a
computer ...
www.chicagotech.net/nameresolution.htm


--
Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on
http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on
http://www.HowToNetworking.com
"Alex Tkachev" <(E-Mail Removed)> wrote in message
news:C78F84D0-1F78-4B90-9E9D-(E-Mail Removed)...
> Hi,
>
> We have fresh Windows Server 2003 Enterprise R2 with all updates installed
> and configured as domain controller and application server. Hardware is
> Supermicro X7DVL-E with Intel® (ESB2/Gilgal) 82563EB Dual-Port Gigabit
> Ethernet Controller (PRO/1000).
> Only one LAN port is used with static IP. The latest hardware drivers are
> installed.
>
> The problem is:
> We can not ping or connect with Remote Desktop or another other mean until
> we browse this machine in network (My Network Places/Entire
> Network/Microsoft
> Windows Network/domain/computer). After we connect like this, we can work
> a
> while, but when the machine's address is removed from ARP cache by
> timeout,
> we lose connection again.
>
> Like this: start pinging the machine getting "Request timeout", then open
> it
> in network browser and ping becomes normal immediately after I see the
> machine's shares.
>
> We have tried all possible configurations with Firewall and Routing and
> Remote Access on and off.
>
> I'm afraid we ran out of ideas. Can you please help?
>
> Regards,
> Alex

Hi Robert,

It was not name resolution, the IP was resolved by name. It did ping IP.
This looked like ARP problem, when requests other than network browser did
not return MAC address. I know how it sounds, but I can swear: get MAC
address to ARP table by browsing and enjoy ping 2 minutes until the address
is removed by timeout.
We were going crazy here with this, decided to install different NIC,
powered off the machine, assured that we do not have compatible NIC, closed
and powered it on without changing anything in hardware - AND after 10
minutes powered off it started to work normally! Now we have all pings and
other connections!

I still wonder what it was. If you have any ideas please share. I think this
can be posted as outstanding experience somewhere.

Regards,
Alex

"Robert L. (MS-MVP)" wrote:

> Sounds like name resolution issue. Can you ping the server by IP before
> browsing the network? Any error if using nslookup? Or this search result may
> help.
>
> Name Resolution
>
> This is name resolution issue if you can ping IP but not computer name
> .... The ping command uses Windows Sockets-style name resolution to resolve a
> computer ...
> www.chicagotech.net/nameresolution.htm
>
>
> --
> Bob Lin, MS-MVP, MCSE & CNE
> Networking, Internet, Routing, VPN Troubleshooting on
> http://www.ChicagoTech.net
> How to Setup Windows, Network, VPN & Remote Access on
> http://www.HowToNetworking.com
> "Alex Tkachev" <(E-Mail Removed)> wrote in message
> news:C78F84D0-1F78-4B90-9E9D-(E-Mail Removed)...
> > Hi,
> >
> > We have fresh Windows Server 2003 Enterprise R2 with all updates installed
> > and configured as domain controller and application server. Hardware is
> > Supermicro X7DVL-E with Intel® (ESB2/Gilgal) 82563EB Dual-Port Gigabit
> > Ethernet Controller (PRO/1000).
> > Only one LAN port is used with static IP. The latest hardware drivers are
> > installed.
> >
> > The problem is:
> > We can not ping or connect with Remote Desktop or another other mean until
> > we browse this machine in network (My Network Places/Entire
> > Network/Microsoft
> > Windows Network/domain/computer). After we connect like this, we can work
> > a
> > while, but when the machine's address is removed from ARP cache by
> > timeout,
> > we lose connection again.
> >
> > Like this: start pinging the machine getting "Request timeout", then open
> > it
> > in network browser and ping becomes normal immediately after I see the
> > machine's shares.
> >
> > We have tried all possible configurations with Firewall and Routing and
> > Remote Access on and off.
> >
> > I'm afraid we ran out of ideas. Can you please help?
> >
> > Regards,
> > Alex
>
>