My router recently died on me and so I had to revert to using a crappy little router supplied to me by Virgin Media my internet provider. I do a fair amount of integration work with the SagePay payment service provider and so I need to configure my router to forward ports to my local instance of IIS in order to accept callbacks from the service. I’ve never had a problem with this before except now with this router I was getting the router admin page even though it was configured not to allow administration from outside of the network, I tried using my DynDns hostname and eventually got it hitting my local instance of IIS but the page would just never complete loading and hang indefinitely.

The solution it seems was actually quite straight forward and requires an entry in your host file which you can find in one of the following locations:

• Windows 9x - (x):\Windows\Hosts
• Windows 2000 - (x):\WinNT\System32\Drivers\etc\Hosts
• Windows XP, Vista and 7 - (x):\Windows\System32\drivers\etc\Hosts

The entry to be added is your local IP address and the hostname to be used to connect to your local web server e.g.

127.0.0.1    www.example.com

For further help and information see Port Forward and Loopback Connections.

Related Posts

1. Page.User is null on IIS7 in Integrated Mode with UrlRewriting.Net

Related posts brought to you by Yet Another Related Posts Plugin.

I was recently working in a clients office where they have very little IT Support and they had a new member of staff on board without a PC. The person that setup the IT infrastructure at the beginning had left a hard drive with an image and a CD to copy the image to any new machine that was added to the network. Sounds simple so I said I would help out. It took some time but eventually the image copied across and I disconnected the slave drive and booted the machine. I joined the machine to the SBS2003 domain and got a warning about another machine on the network with the same name(oops, the image had been built with a machine name currently in use!). Next thing I know is that the user of the first machine using this name can no longer login to the network and now the new machine can’t because of the clashing workstation names. After a lot of head scratching and some reading of various forum posts on similar topics it became apparent that the best solution was to remove both machines from the domain, rename them and rejoin them to the domain., and here is how I did it.

1. Remove the workstation from the domain by moving it to a workrgoup, no reboot required although it does ask you to
2. Change the machine name to something new and unique
3. Login to SBS2003 and remove the workstation from Active Directory
4. Rejoin the workstation to the domain
5. Reeboot

Once the machines had rebooted I was able to successfully log into the domain via both workstations. Hopefully this is of some help to others, I think I have covered all of the steps I performed however I do not claim to be a Small Business Server expert I just know what I need to know and try and learn it if I don’t so would be interested to hear of other solutions to this problem in case it crops up again.

Related Posts

No related posts.

Related posts brought to you by Yet Another Related Posts Plugin.

I recently upgraded TwitterBerry to v0.8 on my Blackberry Pearl and it stopped working, every time I tried to connect I got a ‘Network Request Failed’ error. My friend Google wasn’t much help so I emailed support at Orangatame Software which yielded no result and zero response which I thought was pretty lame since I did get an auto-response back from them stating “Thank you for submitting your question to us online. Case #00001998: “Network Request Failed” has been created and a Orangatame Customer Advocate will get back to you shortly.”

Anyhow, this morning I was messing with the settings and managed to get it working by configuring it to use a connection mode of BIBS whatever that is, so I am now able to start tweeting again from my phone!

Related Posts

No related posts.

Related posts brought to you by Yet Another Related Posts Plugin.