Can not browser intranet sites

I am the IT department here. :)

1. Wireless Router is in Access Point mode on the same internal network segment (192.168.0.x/32) as my computer.

2. Using IP Config, IP information on EVO vs. PC is identical except the IP address (obviously), same DNS servers (192.168.0.10 and 192.168.0.96).

3. I can access http://aptnas/ (as an example) on my PC but it won't resolve on the EVO. I can, however, access http://192.168.0.50 -- the address of the NAS on the EVO.
 
I was having a similar problem where I couldn't access my work intranet. What finally worked for me was to use opera as a browser. The explanation from my IT Dept was that when using opera as your browser everything goes through their server before being redistributed. You can get the opera browser in the marketplace.
 
It's not always random internet providers for WiFi, If you're using wifi and setup DHCP, 9 times out of 10 you can set what DNS servers to use, to forward from your ISP or even designate the router as the local DNS.

In a lot of corporate settings companies use internal DNS servers and even proxy servers to do everything from name resolution, logging, blocking, etc.

Makes sense, if they have their own web server why not have a DNS server as well. I noticed something above about trailing slashes, would that really make a difference?
 
Nope, tried Opera and Dolphin -- neither resolved any local DNS names. It's as if all DNS calls are bypassing local DNS server settings for the WiFi adapter and only using external DNS servers that don't have our custom entries. Since it's doing it on all 3 browsers, it's got to be a TCP/IP problem. I wish there was an NSLOOKUP equivalent command available.
 
Nope, tried Opera and Dolphin -- neither resolved any local DNS names. It's as if all DNS calls are bypassing local DNS server settings for the WiFi adapter and only using external DNS servers that don't have our custom entries. Since it's doing it on all 3 browsers, it's got to be a TCP/IP problem. I wish there was an NSLOOKUP equivalent command available.

NSLOOKUp does work on Android. You need to be rooted to do it though.

2vbo411.png
 
Nope, tried Opera and Dolphin -- neither resolved any local DNS names. It's as if all DNS calls are bypassing local DNS server settings for the WiFi adapter and only using external DNS servers that don't have our custom entries. Since it's doing it on all 3 browsers, it's got to be a TCP/IP problem. I wish there was an NSLOOKUP equivalent command available.

There is, try "terminal" by google in the market.
 
I've just solved this problem!
The three not-so-simple steps are this:
1. Root your phone. It's easier said than done, but fairly straightforward once you get the hang of it. The steps I took to do this:
A: Install Android SDK on your PC. This is 100% free from Google. There are steps involved in this that I won't get into.
B: Download ClockworkMod recovery. Make sure it is the image made for your device. Extract the image (Recovery.img?) and save it to the andrid-sdks\platform-tools\ folder on your PC.
C: Download the correct rooted custom ROM (in zip form) for your device and install it on the SD card.
D: In the Settings\Developer Options enable USB debugging and connect your device to the PC via USB cable.
E: Open the command prompt and navigate to the platform-tools folder.
F: From the command prompt: ADB REBOOT BOOTLOADER
FASTBOOT OEM UNLOCK (You've just voided your warrantee.)
FASTBOOT FLASH RECOVERY RECOVERY.IMG (This installs the Clockworkmod recovery program. It gives you the options you'll need to root.)
FASTBOOT REBOOT
ADB REBOOT RECOVERY
G: On your device: install zip from sdcard (You've just rooted your phone.)
2. Edit your hosts file. Download Hosts Editor from Google Play. Ping your local servers to get their IPs. If you need help with this, google is your friend.
3. Download Opera. This browser is better than the default browser and was able to function for me.
PS. don't drop your phone. it's not under warrantee.:-$