In IIS I created a virtual directory "folder" using an UNC path:
\\10.0.0.5\folder

The server has two network cards, one with address 192.168.0.5, and the
other is 10.0.0.5. The IIS is running on 192.168.0.5, while the 10.0.0.5 is
for the network share. At least that's why I have two interfaces.

Anyways, when I access the site using this:

http://192.168.0.5/folder/file.jpg

On the network share I see the web server connecting by 192.168.0.5 and not
the 10.0.0.5 IP. This is defeating the purpose as it's still going through
the same network. How do I fix this problem and make the web server use the
10.0.0.x network to access the share?

Did you configure the web server to use \\10.0.0.5\folder as the location
for the physical files for its URL binding to 192.168.0.5 ??? If you did
not use an IP address, how have you assured that the name lookup is going to
return 10.0.0.5 vs 192.168.0.5 ???

--
//David
IIS
http://blogs.msdn.com/David.Wang
This posting is provided "AS IS" with no warranties, and confers no rights.
//
[quoted text, click to view]
In IIS I created a virtual directory "folder" using an UNC path:
\\10.0.0.5\folder

The server has two network cards, one with address 192.168.0.5, and the
other is 10.0.0.5. The IIS is running on 192.168.0.5, while the 10.0.0.5 is
for the network share. At least that's why I have two interfaces.

Anyways, when I access the site using this:

http://192.168.0.5/folder/file.jpg

On the network share I see the web server connecting by 192.168.0.5 and not
the 10.0.0.5 IP. This is defeating the purpose as it's still going through
the same network. How do I fix this problem and make the web server use the
10.0.0.x network to access the share?

[quoted text, click to view]

Yes I used \\10.0.0.5\folder as the location, not the netbios name.