almcnicoll

Just to add to effigy's comments, as you're new to this sort of thing, the relevant section of your router setup is probably called "port forwarding" or "virtual servers". You enter the incoming port or range of ports, then the machine you want it to route to, then the port on that machine that you want it to route to. For instance, my FTP server is set up on local IP 192.168.2.4. The entry in "Virtual Servers" reads: Port 21 -> 192.168.2.4 -> Port 21 and then my FTP server listens on port 21 (the usual for FTP)

Hi Debbie, as with other people, I see your new site when I browse to that link. It's not entirely clear from your email what exact steps you've tried, so forgive me if these are things you've already tried: 1. Wait 24 hours (I don't know how long it's been) as DNS servers aroudn the globe sometimes take time to update and point to the new site - you may be accessing the old site via a DNS server that hasn't already updated - unlikely though. 2. Hit F5 (refresh) several times in close succession in case your old site is cached in your browser. 3. Try browsing to a slightly different address which may not have existed on the old site - for instance http://www.debsellsfast.com/home, which is also the home page. For your login problems, the solution depends on a couple of things. Can you post the link that you use to log onto your webmaster site (obviously not your login details, but just the link that you go to) as that may give us an idea? Regards, Al

Unfortunately, changing the port number makes no difference. Got the server listening on port 8888 and tried both localhost:8888 and 127.0.0.1:8888 - nada. tracert gives me a perfect trace (<1ms) for localhost and 127.0.0.1, so I guess the problem isn't there. Incidentally, I uninstalled 2.2 and reinstalled 2.0 as PHP is essential for me - same problem, so it's not a specific Apache2.2 config problem. I have a working Apache2.0 installation on another (XP home) machine, so I'll try trawling through the config files for differences... Thanks for your help - if you do have any more ideas, please do let me know! Al

Hi there, there may well be a way of changing that .html into .php, but maybe you could explain why you need to do it? There's probably a better solution... Regards, Al

Thanks for the post. Apache is running on port 80 - and I get the same behaviour if I explicitly ask for http://localhost:80. I'd like to find out whether the packets are being blocked somewhere, or whether I've done something to the server to stop it responding correctly - is there a tool I can use to "ping" a specific port? Thanks for the heads-up on PHP/Apache2.2 - guess I should have checked that before upgrading! Al

Hi there, just wondering if anyone else has come across this issue? I've got Apache2.2 running on a WinXP Pro laptop. Originally it was crashing with a whole load of errors in the error log, and searching on those led me to use the DisableAcceptEx directive. Now the server starts, the Apache Monitor says it's happy, and the error log is clean. BUT ... Browsing to localhost or 127.0.0.1 just keeps seeking the page forever! It doesn't timeout the near side of 30 minutes, and there's no entries in the error or access logs. My firewall program (AVG Network Edition) prompted me to allow or deny and I created an Allow rule so it isn't being blocked there... Last and not least, when including the relevant LoadModule directives to enable PHP, the server refuses to start (they're the standard PHP LoadModule lines, and I installed it in the standard location of c:/php) Can anyone help? I can give more technical details on request. Al McNicoll

[quote author=masgas link=topic=102720.msg408113#msg408113 date=1154530400] My inet connection is of 4MB download (150 KB upload! ) though, and my IP is static. [/quote] Remember of course that that's a 4MB/s download speed and 150KB/s speed for YOU. For someone accessing pages off your server, their maximum DOWNload speed is going to be 150KB/s if they're the only person connecting to the site, and it would only take three people to request pages at the same time for your site to load as though they were on dial-up (56KB/s)! Their UPload speed would be a share of the 4MB/s... Just a thought! Al