Tag Info

New answers tagged

1

Do you have a non-beta Chrome version you could try just in case it's a bug with Chrome? Another thing you could try is to code those hostnames and configure the VirtualHosts to access the IP address of your machine instead of 127.0.0.1, even though in theory using 127.0.0.1 should be legitimate.


1

Does your computer have a firewall ? If yes, try to open your HTTP port on the computer serving your website. netsh advfirewall firewall add rule name="HTTP TCP Port 80" dir=in action=allow protocol=TCP localport=80 netsh advfirewall firewall add rule name="HTTP TCP Port 139" dir=out action=allow protocol=TCP localport=80 Does your IIS server is listening ...


7

It's probably not going to break much of anything on your local machine, assuming no Windows domain nor DHCP is involved. However, the identifier 'localhost' specifically and always is defined to mean the local machine. This means that any other computer that wants to connect to you by name will be unable to do so, because attempting to connect to ...


4

I'm pretty sure that's OK to use. I don't have a test computer at the moment to test it...you can easily do so. But to prove my answer...here's the actual list of reserved words according to: http://support.microsoft.com/en-us/kb/909264 Table of reserved words +--------------------------+----+----+------+   |Reserved words for names | NT4| 2K | ...



Top 50 recent answers are included