very odd asp.net problem

I am working on making a site in asp.net, and here is the issue I am having.

My asp.net app goes from a login page, to a main page, to an accounts page

when i run it in debug mode on my PC, everything works fine

when i run by opening IE, and navigating to http://192.168.20.101/MyAspApp/
it works fine (my local IP of course)

now here is the problem, I go to the OTHER computer at my desk, its also an XP machine (all updates/sp/.net 1.1sp1 etc...) and I open IE and go to http://192.168.20.101/MyAspApp/, it works fine until i get to the accounts page. It just displays a blank page.... Custom errors are set to off in the config file to spit out error messages... so i dont think its that.. and why should it have an error on one machine but not the other?

i know i probably wont get a good answer on this unless someone has had the same issue, but i figured i would give it a shot...

stange indeed.

Enable tracing.

Quote:

---

Originally Posted by nemaroller

stange indeed.

Enable tracing.

---

how would I go about that? the trace constant is checked in config because its in debug mode.. but how would I actually trace back to try to see whats going on?

I found that if I get the blank page, if I keep hitting refresh in the browser, it will eventually show the page, then sometimes it wont, and then it will, etc...

any idea what could be causing this?? there should be no sort of lag or connection problem, these systems are running all on the same network..

could it be an issue with the IIS on XP Pro since its not the full IIS server? I don't know how this could be the case.. no one else is trying to connect to it, and if I remember right, that was the only main difference of the XP Pro version versus server version... the connection limit..

Start the process in debug on your machine...

put a breakpoint in the load of the suspect page.

Then use the remote machine to connect to the site and access the suspect page. It will fire off the breakpoint because you have attached the debug process to the framework.

Matt,

Can't be of much help at the moment, but I have a similar problem. My app works fine on my dev machine. I put it on the test machine and it works fine there too if you use it through localhost but the minute you try to connect to the test server from another machine, the whole world falls apart. Basically, I'm not getting the postback triggered. The progress bar "pretends" that IE is up to something, but when I try to debug remotely, it never goes into break mode (and yes it is still a debug config). I originally thought it was to do with a heavy use of Autopostback on the form, but having spent most of yesterday investigating, I then discovered even the simple pages fail randomly.

However, if I connect to the dev box from another machine, everything works swimmingly. We're going to try reinstalling IIS and the framework on the test box to see if that makes any difference at all.

I'll keep you posted. Let me know if you have any luck!

Lil Ms S