Windows Forum

Ask something
Discussion Locked

An "Invisible" Server

0 helpful
11 replies

by artcabot

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

At Corporate we have 4 Win2K servers, one of which is running Exchange 2000. A Cisco 2621 here connects to a branch office over frame relay with a Cisco 1751 at the remote site (which is on an SMC wireless network). Here's the mystery (at least to me!):

From any branch office workstation I can ping 3 of the 4 servers at Corporate, but not the Exchange box. Neither can I ping ANY of the TCP/IP addresses on the remote network from the Exchange server. I CAN, however, ping the Corporate Exchange server from a Telnet session to the remote router and CAN ping the LAN interface of the remote router from the Exchange server.

It would seem that something on the remote network (the SMC wireless one) is blocking this one IP address. The remotesubnet is 10.0.4 and the corporate Exchange server is at 10.0.0.2. Where should I be looking?

11 replies

by artcabot

That would've been my guess, too, except that I can get to it from all the other remote offices, just not this one.

by maximk

If not a wrong default gateway, my second guess would be a wrong subnet mask.
If not, please give more information like the current IP settings etc. And some info on your routing tables. There must be some error in your configuration...

by frobo

The default gateway on the Exchange Server is missing or wrong!

regards

frobo

by ciscofred

Do you have dns and wins setup? If so have you tried using nslookup? Can you resolve names to ip and do a reverse lookup?

by artcabot

Some additional "isolating" troubleshooting has been done:

Our trainer plugged directly into the SMC Barricade receiver/hub and was able to reach the server at 10.0.0.2. So, it appears certain that SOMETHING on the wireless network is blocking that address for all the machines transmitting through the air. The literature says the SMC box also acts as a cable router, presenting one IP address to its WAN port (which we're not using). Maybe something in the receiver/hub's IP setup is involved, though it would seem that that scenario would affect the RJ45 ports, too.

by artcabot

Turned out to be the IP setup INSIDE the wireless box. Actually, it was more than just a receiver/hub access point as I had been led to believe. Further investigation showed it was actually a wireless router and the IP stuff hadn't been set up at all.

This discussion is closed to new replies.