Re: Network path name

The parth would not be

\\192.68.0.7\appname\appname.exe

unless appname is a network share you are exporting, and appname.exe is in the root of
that share. Or, if you are using http:, if the executable is in your default HTTP folder.
But that's because of how HTTP: expands the path. A CreateFile does not apply the same
rules to expanding the path. You are comparing what a Web server does to what the file
system does underneath it, without asking how the Web server finds the file. You would
have to apply on the client side the same transformation the Web server applies on the
server side. Why should you be surprised that they are incompatible?
joe

On Sat, 7 Feb 2009 20:38:01 -0800, jc <jc@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:

Joe,

Thank you for your response.

I am unfamiliar, with trying to programmatically access network files.
But, this is kind of strange to me.

If I execute the application from the "Start" "Run" command, then
the program finds the configuration file OK (without the share name).
run: \\192.68.0.7\\appname\appname.exe

But, If I try to execute the program from a browser
http://192.168.0.7/appname/appname.exe. The application runs,
but it does not find the configuration file??

I hardcoded the configuration file path \\192.168.0.7\\appname\appname.cfg.
So, the application is using the same path, regardless if it was started from
the "Run" command or from a browser.

Any ideas?

Thanks,
-jc


.

Bu

"Joseph M. Newcomer" wrote:

Is the C: drive shared out as "C"? Is it shared at all? I tried a few experiments here,
and it only works when I use the proper sharename (for example, one of my machines shares
its C: drive as Q:, so \\192.168.168.4\c\*.* does not work, but \\192.168.168.4\q\*.*
works as expected).
joe

On Sat, 7 Feb 2009 19:02:01 -0800, jc <jc@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:

Hello,

I am having trouble accessing a file through our intranet.
I specify, in the application, the following path:

\\\\192.168.0.7\\c\\appname\\appname.cfg

The actual path on the 192.168.0.7 server is:
c:\appname\appname.cfg

What am I not including, in my application, for the path?

TIA,
-jc

Joseph M. Newcomer [MVP]
email: newcomer@xxxxxxxxxxxx
Web: http://www.flounder.com
MVP Tips: http://www.flounder.com/mvp_tips.htm

Joseph M. Newcomer [MVP]
email: newcomer@xxxxxxxxxxxx
Web: http://www.flounder.com
MVP Tips: http://www.flounder.com/mvp_tips.htm
.

Relevant Pages

  • Re: Network Help
    ... > try to open an http: on the box, or on one of the other computers on ... > the network, it fails and has the network error: ... OR to not having any web server running on your box. ... 4- or..in a strange setup, you may have apache running from your inetd, ...
    (freebsd-questions)
  • Re: Network path name
    ... I apologize for wasting everyone's time with this issue. ... Or, if you are using http:, if the executable is in your default HTTP folder. ... without asking how the Web server finds the file. ... the program finds the configuration file OK. ...
    (microsoft.public.vc.mfc)
  • Re: Security risks when running IIS without static ip as localhost
    ... > access this web server, it is purely for developing asp pages which will ... > network to a security risk. ... For example, one vector of compromise is someone receives, say, a worm email ...
    (microsoft.public.inetserver.iis.security)
  • [NEWS] Trend Micro InterScan VirusWall HTTP Proxy Content Scanning Circumvention
    ... Trend Micro InterScan VirusWall contains an HTTP proxy that prevents users ... from downloading virus-infected content by scanning the data received from ... a web server before passing it to the client. ... The Trend Micro InterScan VirusWall HTTP proxy contains a configuration ...
    (Securiteam)
  • Re: How vulnerable server will become if placed on DMZ ?
    ... >> I have a type of Web Server. ... > protect your internal network from a compromised web server. ... A DMZ can ... > network as compared to what you probably have now, a single firewall. ...
    (microsoft.public.win2000.security)
Quantcast