asp.net accross different domains.
-
Hi All, i deployed my asp.net application into IIS, and if i run it in that server, say in Domain 1 , it works perfectly, but when i run that asp.net application from another machine, which is in the different domain, say in Domain 2, i got this error: Could not find a part of the path Domain 1\ITManagement\WarehouseData\Current. The senario in here is that a machine in Domain 1 browse into an asp.net application on a server in Domain 2, and then the asp.net application on domain 2 tries to access a shared network driver on Domain 1. i spent quite a few times to google it but without any luck, can someone in here help me plz
-
Hi All, i deployed my asp.net application into IIS, and if i run it in that server, say in Domain 1 , it works perfectly, but when i run that asp.net application from another machine, which is in the different domain, say in Domain 2, i got this error: Could not find a part of the path Domain 1\ITManagement\WarehouseData\Current. The senario in here is that a machine in Domain 1 browse into an asp.net application on a server in Domain 2, and then the asp.net application on domain 2 tries to access a shared network driver on Domain 1. i spent quite a few times to google it but without any luck, can someone in here help me plz
If I understand you correctly, you want your asp.net app to access a shared folder on a machine that is in a different windows domain. You could establish a trust relationship between the domains and add the account the app runs as in domain2 to the share permissions on the domain1 server, or you could map a drive on the server using some credentials from Domain1 and have your app use the drive letter. This really isn't an asp.net question at all which is why you may have had trouble with your google searches. It is a network share question.
-
Hi All, i deployed my asp.net application into IIS, and if i run it in that server, say in Domain 1 , it works perfectly, but when i run that asp.net application from another machine, which is in the different domain, say in Domain 2, i got this error: Could not find a part of the path Domain 1\ITManagement\WarehouseData\Current. The senario in here is that a machine in Domain 1 browse into an asp.net application on a server in Domain 2, and then the asp.net application on domain 2 tries to access a shared network driver on Domain 1. i spent quite a few times to google it but without any luck, can someone in here help me plz
AndieDu wrote:
when i run that asp.net application from another machine, which is in the different domain, say in Domain 2, i got this error: Could not find a part of the path Domain 1\ITManagement\WarehouseData\Current.
Instead of accessing ITManagement\WarehouseData\Current from the file system make it available from a web service and access it that way.
-
AndieDu wrote:
when i run that asp.net application from another machine, which is in the different domain, say in Domain 2, i got this error: Could not find a part of the path Domain 1\ITManagement\WarehouseData\Current.
Instead of accessing ITManagement\WarehouseData\Current from the file system make it available from a web service and access it that way.
Accessing files on the same local network through a web service would be bad from a performance standpoint. You would have to base64 encode, then transmit the much larger encoded version, then decode on the other end. You also don't get anywhere near the richness of the System.IO classes for checking if the file exists or examining attributes like readonly, creation date etc.