Connecting with FrontPage

[illdill]

I have windows SBS 2003 running on my server along with several websites. The problem I am having is accessing a specific site for editing with front page. When I connect to the site, the connection doesn't seem to last long before I start getting server busy errors. I just upgraded the RAM and while performance is cleaner, access with Front Page continues to dissapoint. This is only happening for one site on my server. Even while I am getting server busy errors on this one site, I can log into another site and work just fine. Any help would be great.

I am accessing the server that is inside my own network, however I am still resolving through the domain name. i.e.

http://website.com:81

Apache running on port 80 IIS on port 81.

Thanks

 

[monsterjta]

If you're working internally, I would suggest keeping the traffic internally. I don't see any need to traverse the Internet to access a local server...

Hope This Helps,

Good Luck!

 

[illdill]

The way my server is configured, it's just not possible. There is no real dns going on, Apacher answers the request and forwards it to the IIS dns which then resolves to the approprioate IIS site. For instance I could not navigate to 192.168.0.12:81(Server IP) because apache will not know what site on :81 to resolve.

Thanks.

 

[illdill]

I solved the problem, but I am not sure why what the problem was was only effecting that one specific site. Occasionaly, I would not be able to connect to any site, so I did some more loking around at my network and discovered an IP conflict that realy had no reason to be conflicting (I think).

I have two routers, One hard wired, the other wireless. The Hard wired router is the distribution point for my network, and the wireless router was configured simply to act as a switch (no cennection to the router itself, only the LAN ports).

Anyway, both were assigned the same IP address and when I would get thrown off the internet or get srver busy errors, when I would try to access the hardwired router, the wireless admn page would show up instead. I figured I would change the IP of the wireless router and whala! That was it, no more getting booted off, or server busy errors.

So lesson learned: Even if a router is being used as a switch, make sure it's IP address does not conflict with the network.

Thanks for all your support.

Tim