With some messing around I could make this work on my setup, but I found
it much easier to develop locally and use the handy little "Copy
Project" button to send my project to the production machine. It also
gives you the option to only copy files needed to run, so you don't
clutter up the production environment with all of VS's extra files.

Your server  needs to have either Frontpage Extensions installed, or you
network access to a shared folder which houses your web  stuff. The server
admins need to either give you author privledges on a web (frontpage), or
network privledges to a share on the webserver.

We had this problem when starting our projects too. I believe VS.net
attempts to connect to the project via FrontPage extentions first (which is
why it tried http://161.#.##.##/crews/WebApplication1
<http://161.#.##.##/crews/WebApplication1> first) then it'll try to access
the project via network shares (which is why it then tried to access it via
the UNC path \\$$$.wku.edu\wwwroot$\crews\WebApplication1'
<file://\\$$$.wku.edu\wwwroot$\crews\WebApplication1'> ) For some reason
VS.net added the $ at the end of the wwwroot share name - so when we removed
the $ it worked for us... so try connecting to
\\$$$.wku.edu\wwwroot\crews\WebApplication1
<file://\\$$$.wku.edu\wwwroot\crews\WebApplication1> (notice - no $ after
wwwroot). If that doesn't work -- see if you can access
\\$$$.wku.edu\wwwroot$\crews\ <file://\\$$$.wku.edu\wwwroot$\crews\> from
your windows explorer. If not, then it could be a permissions problem...

FYI, the $ on the end of the share name means that the share is
hidden, which is recommend in an environment where you don't want
certian users to see your shares.

The reason VS.Net adds that dollar symbol on is because a share name
followed by a $ indicates a hidden share. That is, a share which exists, but
won't show up in network neighborhood. By default, windows creates wwwroot$
when you install IIS.