Hi, I've got a little situation here, which is generally linked to this subforum.
Basically, I've got a few HTML/Text modules across the site, which sometimes have hyperlinks in them to other pages. Normally, not a problem, a user can go to the page and copy the link, then past it in the HTML module. 
However, the DNN URL contains the current running culture, meaning the link being copied is not very useable because it will not consider any user's current language when clicking that link.

What I did in my development environment was try to use the physical path e.g. /ParentPageName/SubPageName.aspx. And it works perfectly. On the other hand, when I try the same, on the same site/server (IIS on dev PC in network) from another PC, I get a resource not found 404 exception. The same with various hyperlinks that may reside in custom modules.

I also have custom user controls in the skin which build a menu using a asp:menu control with items bound from an xml file on the server. The navigateURLs in the xml file also refer to the pages this way, but obviously suffer the same issues when attempting to use them from another PC.

I suppose it's something like not allowing users to list contents of a folder, but I'm not listing a folder, but accessing an actual page. Any idea what the problem is and how to fix it?

Well, by physical path, I meant the path as you'd see it in the treeview on the pages page.

Basically a link in a menu with navigateURL "~/custompage.aspx" will work on the dev pc, but clicking that same link on the external connecting pc gives a 404.
Same for "~/custompage/subcustompage.aspx" actually. Kinda strange. URL in the browser's correct though.

The app itself is hosted in IIS under a root site as per usual. The dev pc of course doesn't have a DNS configured and the site's connection string goes to localhost. I connect to the site using the PC's IP/sitename. If any of that rings a bell as to why that would result in a 404 ...