I'm trying to write a really simple webpage on a Win2000 Server computer, but it is giving me fits. Everytime I try and open it in IE via a terminal services client, IE crashes, telling me it can't find a component of the file. All links are relative, and its still being a bitch. The weird thing is that I can log in as administrator to the machine locally and run the webpages just fine. Users within the domain can also run the webpages just fine. But, anyone logging in through our multi-user terminal services server cannot access the webpages. The aforementioned error results. I have checked file and directory permissions, and all of that is square and good.Here is the index page:
1/4/2006 4:55:18 PM
bttmft
1/5/2006 10:18:20 AM
1/5/2006 10:23:58 AM
I'm not using the IIS, actually. I've got the webpage on a share that the entire company can access. Ironically, the only way I can get it to work for remote users is to use IIS, though (local server, doesn't go outside of the firewall). Of course, can't make a freaking shortcut on the desktop for the people, as I get a similar error, only without the prompt that says it can't find a component of the file.Here's the kicker. While I can't make a shortcut, the remote user can just type the address of the "webserver" and it runs just fine.
1/5/2006 2:14:57 PM
Have you checked to make sure the URL/target in the shortcut is identical to the path that gets to the page?A while back I had a problem where some shorcuts would not work and would cause an error message with bad grammar to appear (it was missing a file name and looked funny). When I recreated the shortcuts again (despite having the same target) they worked. Distributing shortcuts to people on a network sometimes causes the targets to change relative to the PC you are using to send them. This predictably will cause a huge mess.
1/5/2006 2:28:10 PM
well, the shortcut is a "local one." It existed in the "All Users\Desktop" folder, so it doesn't make sense that it didn't work. The URL was just the webserver, as well, so that one seems hard to fuck up, though I'm sure I could manage it
1/5/2006 2:51:26 PM