What the hell?

[Sidoh]

Contents of my hosts file (C:\WINDOWS\System32\drivers\etc\hosts):

Code: [Select]

# Copyright (c) 1993-1999 Microsoft Corp.
#
# This is a sample HOSTS file used by Microsoft TCP/IP for Windows.
#
# This file contains the mappings of IP addresses to host names. Each
# entry should be kept on an individual line. The IP address should
# be placed in the first column followed by the corresponding host name.
# The IP address and the host name should be separated by at least one
# space.
#
# Additionally, comments (such as these) may be inserted on individual
# lines or following the machine name denoted by a '#' symbol.
#
# For example:
#
#      102.54.94.97     rhino.acme.com          # source server
#       38.25.63.10     x.acme.com              # x client host
127.0.0.1       localhost
10.0.0.15 sidoh.no-ip.org
10.0.0.15 www.sidoh.org
10.0.0.15 sidoh.org
And now the odd part:

C:\>ping sidoh.no-ip.org -n 1

Pinging sidoh.no-ip.org [66.28.80.30] with 32 bytes of data:

Reply from 66.28.80.30: bytes=32 time<1ms TTL=64

C:\>ping www.sidoh.org -n 1

Pinging sidoh.org [66.28.80.30] with 32 bytes of data:

Reply from 66.28.80.30: bytes=32 time<1ms TTL=64

C:\>ping sidoh.org -n 1

Pinging sidoh.org [66.28.80.30] with 32 bytes of data:

Reply from 66.28.80.30: bytes=32 time<1ms TTL=64

I'm going to try the "Windows fix" (Restart).  This may end up in the trash can soon enough. 

[deadly7]

You can ping yourself? wtfcopter since when

[Sidoh]

You can ping yourself? wtfcopter since when

No, the addresses should be resolving to 10.0.0.15 (the private address of my server), not my public IP address. (66.28.80.30).

Notice:

Code: [Select]

10.0.0.15      sidoh.no-ip.org

C:\>ping sidoh.no-ip.org -n 1

Pinging sidoh.no-ip.org [66.28.80.30] with 32 bytes of data:

And by the way... restart didn't fix it. 

[Newby]

Hmm... this worked fine for me when I was in Windows!

newby@impaler:~$ cat /mnt/old-drive/WINDOWS/system32/drivers/etc/hosts
# Copyright (c) 1993-1999 Microsoft Corp.
#
# This is a sample HOSTS file used by Microsoft TCP/IP for Windows.
#
# This file contains the mappings of IP addresses to host names. Each
# entry should be kept on an individual line. The IP address should
# be placed in the first column followed by the corresponding host name.
# The IP address and the host name should be separated by at least one
# space.
#
# Additionally, comments (such as these) may be inserted on individual
# lines or following the machine name denoted by a '#' symbol.
#
# For example:
#
#      102.54.94.97     rhino.acme.com          # source server
#       38.25.63.10     x.acme.com              # x client host

127.0.0.1       localhost
192.168.169.2   mom
192.168.169.5   impaler
192.168.169.5   newby.x86labs.org
192.168.169.5   impaler.x86labs.orgnewby@impaler:~$

[Quik]

I've had this issue with my own network for weeks now. My problem is that when I try to visit the domain from the same lan that my server is on, I get sent to my own IP address, which sees that I'm inside the router and puts me to the router's config page. I have a similar config file, no avail. I'm hoping that my future network changes (might not be possible for you) will fix this issue.

[Sidoh]

I've been using a HOSTS file to bypass sidoh.org resolving to my public IP address since I've had my server (about 1.5 years now), it's always worked.  It just stopped working today and I'm unsure why.

[iago]

root@slayer:/home/iago# ping www.javaop.com -c1
PING iago.dnsalias.com (142.161.170.188) 56(84) bytes of data.
64 bytes from wnpgmb11dc1-170-188.dynamic.mts.net (142.161.170.188): icmp_seq=1 ttl=149 time=1.71 ms
--- iago.dnsalias.com ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 1.712/1.712/1.712/0.000 ms

root@slayer:/home/iago# echo "192.168.1.3 www.javaop.com" >> /etc/hosts

root@slayer:/home/iago# ping www.javaop.com -c1
PING www.javaop.com (192.168.1.3) 56(84) bytes of data.
64 bytes from darkside (192.168.1.3): icmp_seq=1 ttl=64 time=2.77 ms
--- www.javaop.com ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 2.771/2.771/2.771/0.000 ms

*shrug*

The reason I don't do that, however, is because I tend to move my laptop around a lot, and I usually take awhile to realize why I can't get here

[Sidoh]

The reason I don't do that, however, is because I tend to move my laptop around a lot, and I usually take awhile to realize why I can't get here

Hehe.  I guess I may have to switch to using the private IP address for everything.

I was wondering if maybe it got shut down or something (because I couldn't get to most of the services it was running -- including SSH), but then I realized I was still listening to Dry Kill Logic (Samba)!

You don't think this would have anything to do with it, do you?

C:\>ipconfig -all

Windows IP Configuration

        Host Name . . . . . . . . . . . . : chris
        Primary Dns Suffix  . . . . . . . :
        Node Type . . . . . . . . . . . . : Hybrid
        IP Routing Enabled. . . . . . . . : No
        WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

        Connection-specific DNS Suffix  . :
        Description . . . . . . . . . . . : NVIDIA nForce Networking Controller
        Physical Address. . . . . . . . . : 00-11-2F-62-A4-56
        Dhcp Enabled. . . . . . . . . . . : No
        IP Address. . . . . . . . . . . . : 10.0.0.25
        Subnet Mask . . . . . . . . . . . : 255.255.255.0
        Default Gateway . . . . . . . . . : 10.0.0.2
        DNS Servers . . . . . . . . . . . : 10.0.0.2

I would imagine Windows should consult the hosts file before it queries a DNS server, but I suppose I could be wrong.  I have all my network settings statically configured, DHCP is disabled on my router, my server is DMZ'd (and I haven't bothered setting up a DHCP server on Linux yet) and I accidentally disabled the HTTP server on my router (T_T).  I may have to restore settings on it or something soon to fix that...

[iago]

Haha

By the way, did you try rebooting? That would probably fix it. 

If not, make sure every line is right in the hosts file.  One bad line might screw up the whole thing.  Also, check Windows' event log, see if there's any new errors?

[Sidoh]

Haha

By the way, did you try rebooting? That would probably fix it. 

If not, make sure every line is right in the hosts file.  One bad line might screw up the whole thing.  Also, check Windows' event log, see if there's any new errors?

Hehe, I sure did!

I'm going to try the "Windows fix" (Restart). This may end up in the trash can soon enough.

Haha, I was pretty sure that would fix it, but it didn't. 

Great ideas, checking on those now.

Edit --

The file looked fine, at least for everything I checked for (extra line-breaks, etc).

I looked at the event log, I didn't notice anything suspicious, except for maybe this (which only seemed slightly suspcious because I didn't recognize it):

Event Type:   Warning
Event Source:   Userenv
Event Category:   None
Event ID:   1517
Date:      11/16/2005
Time:      6:46:20 PM
User:      NT AUTHORITY\SYSTEM
Computer:   CHRIS
Description:
Windows saved user CHRIS\sidoh registry while an application or
service was still using the registry during log off. The memory 
used by the user's registry has not been freed. The registry will 
be unloaded when it is no longer in use. 

This is often caused by services running as a user account, 
try configuring the services to run in either the LocalService or 
NetworkService account.

For more information, see Help and Support Center at 
http://go.microsoft.com/fwlink/events.asp.

[Sidoh]

I just tried this too:

C:\>ipconfig /flushdns

Windows IP Configuration

Successfully flushed the DNS Resolver Cache.

Didn't work. 

[Sidoh]

I've been poking around on Google and found a few suggestions... none of which worked.

One recommended disabling the DNS service (which didn't work), another suggested it was a virus that changed the path for the hosts file.  I found the registry entry (also listed in google groups) and found it's in the correct path:

 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters \
DataBasePath] = %SystemRoot%\System32\drivers\etc

[Sidoh]

Sorry for the mega-multiposting here, I just think it helps seperate things.

Found the solution!

Follow these steps:

Go to Control Panel -> Network Connections -> Right-click <YOUR CONNECTION> -> Properties



Click on "Install":



Click on "Protocol" then click the "Add" button:



Click on the "Have Disk..." button:



In the box below the label "Copy manufacturer's files from:", type "\windows\inf" and click on the "OK" button:



Click on "Internet Protocol (TCP/IP)" and then click "OK".

Reboot!

Worked great!

C:\>ping sidoh.org

Pinging sidoh.org [10.0.0.15] with 32 bytes of data:

Reply from 10.0.0.15: bytes=32 time<1ms TTL=64

[iago]

Why clue why you had to do all that crap?

[Sidoh]

Why clue why you had to do all that crap?

Haha, apparently it's a lot easier on SP2:

C:\> netsh winsock reset catalog

But I don't have SP2 for obvious reasons, so I had to manually re-add TCP/IP.

There was actually a very strange problem on the w98 machines at my school that was fixed by this solution as well (it was a login issue).

But I think the answer you're looking for is closer to something like: BECAUSE IT'S WINDOWS!

[iago]

Why clue why you had to do all that crap?

Haha, apparently it's a lot easier on SP2:

C:\> netsh winsock reset catalog

But I don't have SP2 for obvious reasons, so I had to manually re-add TCP/IP.

There was actually a very strange problem on the w98 machines at my school that was fixed by this solution as well (it was a login issue).

But I think the answer you're looking for is closer to something like: BECAUSE IT'S WINDOWS!

Well, I was more wondering what happened that made you have to go through that work.  Like, what could have changed to cause that?

I'm not trying to say that Windows sucks (I don't have to), I'm just wondeirng what caused this particular problem

[Sidoh]

I'm just wondeirng what caused this particular problem

BECAUSE IT'S WINDOWS!

Hehe, sorry.  Couldn't resist!

But I'm not at all sure, actually.  I didn't change any network settings to my knowledge.  I suppose I could have, but I don't remember doing them!

[Blaze]

I started up my computer and my sound stopped working.  I ended up having to remove my card, restart, turn off, put it back in and start again on many different occasions on different machines with different hardware.

It is

BECAUSE IT'S WINDOWS!

[Screenor]

>ping sidoh.org

Pinging sidoh.org [66.28.80.30] with 32 bytes of data:

Reply from 66.28.80.30: bytes=32 time=118ms TTL=45
Reply from 66.28.80.30: bytes=32 time=108ms TTL=45
Reply from 66.28.80.30: bytes=32 time=110ms TTL=45
Reply from 66.28.80.30: bytes=32 time=106ms TTL=45

Ping statistics for 66.28.80.30:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 106ms, Maximum = 118ms, Average = 110ms

[Sidoh]

>ping sidoh.org

Pinging sidoh.org [66.28.80.30] with 32 bytes of data:

Reply from 66.28.80.30: bytes=32 time=118ms TTL=45
Reply from 66.28.80.30: bytes=32 time=108ms TTL=45
Reply from 66.28.80.30: bytes=32 time=110ms TTL=45
Reply from 66.28.80.30: bytes=32 time=106ms TTL=45

Ping statistics for 66.28.80.30:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 106ms, Maximum = 118ms, Average = 110ms

If you would read the entire topic, maybe you'd understand that the problem was with my computer, not with my network.

[Ergot]

>ping sidoh.org

Pinging sidoh.org [66.28.80.30] with 32 bytes of data:

Reply from 66.28.80.30: bytes=32 time=118ms TTL=45
Reply from 66.28.80.30: bytes=32 time=108ms TTL=45
Reply from 66.28.80.30: bytes=32 time=110ms TTL=45
Reply from 66.28.80.30: bytes=32 time=106ms TTL=45

Ping statistics for 66.28.80.30:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 106ms, Maximum = 118ms, Average = 110ms

If you would read the entire topic, maybe you'd understand that the problem was with my computer, not with my network.

The problem isn't the computer, it's the OS.

[Sidoh]

The problem isn't the computer, it's the OS.

When I say "there's a problem with my computer," it generally entails the possibility of the problem resonating in the OS.

[Ergot]

The problem isn't the computer, it's the OS.

When I say "there's a problem with my computer," it generally entails the possibility of the problem resonating in the OS.

Usually when your CPU is on fire, it's a problem with your computer and not your OS. However, with Windows... Anything can happen.

[Sidoh]

Usually when your CPU is on fire, it's a problem with your computer and not your OS. However, with Windows... Anything can happen.

I don't think you understood what I said, so I'll rephrase.

I said there's a problem with my computer; that implys that the problem could be with the OS, not just with hardware.

[iago]

Stop being difficult! You know what he means :-P

[Sidoh]

Stop being difficult! You know what he means :-P

I know what he thinks he means, but I don't think he knows what I mean!

[Screenor]

The problem is Sidoh.

[Sidoh]

The problem is Sidoh.

Haha.  Well, it WAS my problem.

[iago]

Stop being difficult! You know what he means :-P

I know what he thinks he means, but I don't think he knows what I mean!

I meant that both ways.  I think he's just being difficult

[Sidoh]

I meant that both ways.  I think he's just being difficult

Hahaha

[Ergot]

Stop being difficult! You know what he means :-P

I know what he thinks he means, but I don't think he knows what I mean!

I meant that both ways.  I think he's just being difficult

I prefer you use the word HARD instead of difficult
I'm only being difficult because Sidoh is hiding on my Buddy List

[Sidoh]

I prefer you use the word HARD instead of difficult
I'm only being difficult because Sidoh is hiding on my Buddy List

Haha.  That sounds like your problem, then!

[Sidoh]

GAH HA!!

I found what caused this issue.  Fucking MSN Messenger.  It's been overloaded with so much junk.  Back to gaim, I guess!

MSN has this "troubleshooting" tool which automatically launches when it can't figure out how to connect; oddly enough, windows messneger/gaim had no problems connecting!

I was looking more closely at it and it had a list of things it was checking up on, including "DNS", "Connection" and "Hosts File".  Once I saw that (this was after having fixed this problem already through the re-installation of TCP/IP on windows), I wondered if it was causing my problem.

Sure enough:

C:\>ping www.sidoh.org

Pinging sidoh.org [66.28.80.30] with 32 bytes of data:

Reply from 66.28.80.30: bytes=32 time<1ms TTL=64
Reply from 66.28.80.30: bytes=32 time<1ms TTL=64
Reply from 66.28.80.30: bytes=32 time<1ms TTL=64
Reply from 66.28.80.30: bytes=32 time<1ms TTL=64

Ping statistics for 66.28.80.30:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 0ms, Average = 0ms

Code: [Select]

127.0.0.1 localhost
10.0.0.15 sidoh.org
10.0.0.15 www.sidoh.org
10.0.0.15 sidoh.no-ip.org
Lession learned:  Don't use MSN Messenger.