WinXPro IIS from another PC on LAN

[JDP@Work]

I've seen similar posts regarding remote debugging, but I'm not sure if that's
what I'm looking for.

FYI: My laptop has one of those low & wide monitors which never quite matches my
clients CRT.

What I want to do is open the ASP.Net web in...

First to just view the page output in the browser on a machine where I can
easily set the resolution similar to the client's, make changes in the app
(while not in debug mode) and re-test to prefect the UI experience.

Secondly, develop from my larger monitor desktop but have all the pieces live on
my WinXPro laptop.

I do this so that everything is always on my laptop and I can go to the client
with everything, I PKZip copies to my local server for safety & burn CD's from
there, but otherwise all the original components reside on my laptop, too many
times I've been at the client and realized that I'd forgotten to bring
something.

.... posted earlier in MS WinXP General

Before I go fixing and changing is there something that a standard WinXPro SP2
system should have changed to enable viewing web pages from another PC on a LAN?

I have a .Net application that I can access locally on my WinXPro system as

http://Box02/CompReq.Dev/ or http://localhost/CompReq.Dev/

Both open my default page, however I cannot access this from any other
system running Win2KPro or Win2KServer on my LAN.

The only element that I notice in Properties for the root web folder, |Security
is the addition of Internet Guest Accountno (Box02\USR_Box02) on this WinXPro
system.

Everyone is set to Read & Exec, List and Read = Allow.

Any clues are appreciated.

TIA

JeffP....
P.S. I've seen some workarounds for remote debugging, but since I'm not eager to
open my security and I'm not remote debugging this doesn't seem like a good
choice.

 

[S. Justin Gengo]

JDP,

A few things I can think of:

First is the XP firewall on? If it's off / told to allow the computer trying
to connect to it then you should be able to connect to the application with:
http://[XP Box Name Here]/CompReq.Dev/

As far as viewing the window in the screen resolution of the client I use a
few javascripts added to my favorites to do that:

javascript:window.moveTo(0,0);window.resizeTo(640,460);window.moveTo((screen.availWidth-640)/2,(screen.availHeight-460)/2);

javascript:window.moveTo(0,0);window.resizeTo(800,580);window.moveTo((screen.availWidth-800)/2,(screen.availHeight-580)/2);

javascript:window.moveTo(0,0);window.resizeTo(1024,740);window.moveTo((screen.availWidth-1024)/2,(screen.availHeight-740)/2);

When clicked on (like a link) from my favorites folder each of these scripts
reset the browser window that currently has focus to the given size and
centers the window on the screen. Note that each window's height is 20
pixels less than the standard resolution to account for users who don't
auto-hide their start bar. I program everything on my local machine and when
I'm debugging I resize the window with a quick call to my favorites folder
in order to see the page in these various common sizes. These scripts work
in any browser.

--
Sincerely,

S. Justin Gengo, MCP
Web Developer / Programmer

www.aboutfortunate.com

"Out of chaos comes order."
Nietzsche

 

[JDP@Work]

S. Justin,

Thanks for your comprehensive reply.

Yes the firewall is on, that's SP2's way.

I tried the browser adjustment, it is darkside of the moon COOL, mostly because
it is so simple.

I'd still like to find a solution, when I'm collaborating, I like to peek at the
pages on my desktop to coach my associates on what's right or wrong back on the
laptop.

My workaround is to host the whole project to my LAN Win2K server, but that
means that I have to spend nearly an hour updating moving & testing all the
databases and any path issues just to have a working version on my laptop, which
cramps my style when it's time to go out to a client.

JeffP....

JDP,

A few things I can think of:

First is the XP firewall on? If it's off / told to allow the computer trying
to connect to it then you should be able to connect to the application with:
http://[XP Box Name Here]/CompReq.Dev/

As far as viewing the window in the screen resolution of the client I use a
few javascripts added to my favorites to do that:

javascript:window.moveTo(0,0);window.resizeTo(640,460);window.moveTo((screen.ava
ilWidth-640)/2,(screen.availHeight-460)/2);javascript:window.moveTo(0,0);window.resizeTo(800,580);window.moveTo((screen.ava
ilWidth-800)/2,(screen.availHeight-580)/2);javascript:window.moveTo(0,0);window.resizeTo(1024,740);window.moveTo((screen.av
ailWidth-1024)/2,(screen.availHeight-740)/2);

When clicked on (like a link) from my favorites folder each of these scripts
reset the browser window that currently has focus to the given size and
centers the window on the screen. Note that each window's height is 20
pixels less than the standard resolution to account for users who don't
auto-hide their start bar. I program everything on my local machine and when
I'm debugging I resize the window with a quick call to my favorites folder
in order to see the page in these various common sizes. These scripts work
in any browser.

--
Sincerely,

S. Justin Gengo, MCP
Web Developer / Programmer

www.aboutfortunate.com

"Out of chaos comes order."
Nietzsche

I've seen similar posts regarding remote debugging, but I'm not sure if
that's
what I'm looking for.

FYI: My laptop has one of those low & wide monitors which never quite
matches my
clients CRT.

What I want to do is open the ASP.Net web in...

First to just view the page output in the browser on a machine where I can
easily set the resolution similar to the client's, make changes in the app
(while not in debug mode) and re-test to prefect the UI experience.

Secondly, develop from my larger monitor desktop but have all the pieces
live on
my WinXPro laptop.

I do this so that everything is always on my laptop and I can go to the
client
with everything, I PKZip copies to my local server for safety & burn CD's
from
there, but otherwise all the original components reside on my laptop, too
many
times I've been at the client and realized that I'd forgotten to bring
something.

... posted earlier in MS WinXP General

Before I go fixing and changing is there something that a standard WinXPro
SP2
system should have changed to enable viewing web pages from another PC on
a LAN?

I have a .Net application that I can access locally on my WinXPro system
as

http://Box02/CompReq.Dev/ or http://localhost/CompReq.Dev/

Both open my default page, however I cannot access this from any other
system running Win2KPro or Win2KServer on my LAN.

The only element that I notice in Properties for the root web folder,
|Security
is the addition of Internet Guest Accountno (Box02\USR_Box02) on this
WinXPro
system.

Everyone is set to Read & Exec, List and Read = Allow.

Any clues are appreciated.

TIA

JeffP....
P.S. I've seen some workarounds for remote debugging, but since I'm not
eager to
open my security and I'm not remote debugging this doesn't seem like a
good
choice.