Link to home
Start Free TrialLog in
Avatar of si-support
si-support

asked on

Windows Server 2008 R2 can't ping across wireless bridge

I just installed our first Windows Server 2008 R2 standard server on our network, running on an HP Proliant ML350g6.  I'm trying to communicate with devices through a wireless bridge (layer 2) from our main office to a warehouse.  I can ping devices at the warehouse from any server (Win2k3 or W2k) or pc at the office - except this new server.  I get "destination host unreachable".   The server is using settings from DHCP, though I also tried setting a static ip with appropriate Gateway\DNS\WINS settings.  I've disabled the firewall and IPv6.  I've wiped the server and reinstalled the OS - no change.  I've swapped the ports on the dual-port nic - no change.

Any idea why this one server would not be able to ping to the remote devices?

TIA - Roger
SOLUTION
Avatar of naykam
naykam
Flag of Australia image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Have you checked the path and where it fails. Try tracert and pathping.
Avatar of Darius Ghassem
Disable one of the Network Cards not being used.
Avatar of si-support
si-support

ASKER

Thanks for the responses.

Naykam - on this side of the wireless, everything can ping the server - and the server can ping everything.  From the other side, nothing can ping the server.  

sfossupport - since it's all on the same local subnet, there is no route to trace.  It just times out.

dariusg - there is one network card with two ports.  Disabling one portand using the other does not resolve the problem.
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Post ipconfig /all
thanks sfossupport - nslookup works fine for anything on this side of the wireless.  Nothing on the other side.  There is a primary and secondary DNS on this side of the wireless, and everything seems to function properly from those servers.
Here's the ipconfig /all:

Windows IP Configuration

   Host Name . . . . . . . . . . . . : host1
   Primary Dns Suffix  . . . . . . . : company1.local
   Node Type . . . . . . . . . . . . : Hybrid
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No
   DNS Suffix Search List. . . . . . : company1.local

Ethernet adapter Local Area Connection 2:

   Connection-specific DNS Suffix  . : company1.local
   Description . . . . . . . . . . . : HP NC326i PCIe Dual Port Gigabit Server Adapter #2
   Physical Address. . . . . . . . . : F4-CE-46-B6-12-98
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   IPv4 Address. . . . . . . . . . . : x.x.x.125(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.0.0
   Lease Obtained. . . . . . . . . . : Thursday, March 25, 2010 8:30:31 AM
   Lease Expires . . . . . . . . . . : Wednesday, March 31, 2010 8:30:31 AM
   Default Gateway . . . . . . . . . : x.x.x.253
   DHCP Server . . . . . . . . . . . : x.x.x.2
   DNS Servers . . . . . . . . . . . : x.x.x.2
                                       x.x.x.4
                                       x.x.x.5
                                       x.x.x.12
   Primary WINS Server . . . . . . . : x.x.x.2
   Secondary WINS Server . . . . . . : x.x.x.4
   NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter Local Area Connection:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : HP NC326i PCIe Dual Port Gigabit Server Adapter
   Physical Address. . . . . . . . . : F4-CE-46-B6-12-99
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes

Tunnel adapter isatap.company1.local:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . : company1.local
   Description . . . . . . . . . . . : Microsoft ISATAP Adapter
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes

Tunnel adapter isatap.{F9335B1D-6033-48D3-927C-D90190C8402E}:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
I had disabled the 2nd nic before, with no effect.  I had reinstalled the OS and forgot to disable it again.  I just disabled it.  Still no connection.
Some additional info.  When I go to a pc on the far side of the wireless connection at our warehouse, I can login and connect to the old servers at the office across the wireless.  But, when I run tracert to the new server by name, it properly resolves the ip address but times out.
That is fine but you still need to have the second NIC disabled. Or you need to have the enabled NIC higher in the binding order.
The second nic was disabled (see two comments back). Still no flow.
I see that you have multiple dns servers. Do these dns servers share information (ie zone transfers) or are they separate. Are these all primary dns for a specific zone ? When you tested using nslookup, did you try using each name server to see which one worked best. Is there a reason that you have 4 dns servers. As a test use only one dns server.
You can try dcdiag /fix to fix dns.
  Good luck
How about your binding order?
ASKER CERTIFIED SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
.