GoDaddy/dns problems

[ChoboSeki]

**EDIT**
When my brother goes to the domain, it works (he's on wireless, on the same network as I am) and then it works ONCE for me, like what I said happens to me below.
**EDIT**
Friend got a new domain, it uses GoDaddy's forward IP: 64.202.187.170.

My friend and I are both having this problem:

Comp #1: RJ45 - > Router > Modem
Comp #2: Wireless - > Router > Modem

When we use Comp #2 and ping 64.202.187.170 or go to the domain, it doesn't work.

When we try to use the Comp #1, it works, both pinging the IP and going to the domain.

When we go back to Comp #2, we ping the IP:
Reply from 64.202.189.170: bytes=32 time=80ms TTL=113
Request timed out.
Request timed out.
Request timed out.
Still on Comp #2, we go to the domain, fails to load.

We go back to Comp #1, reload the domain and/or ping it, it works.

Going back to Comp #2, go to the domain, works! Wait, can't ping it anymore, can't load the domain anymore.



It seems we have to go to the website via wired connection to be able to get to it on wireless connection, once we do use it on wireless connection, it stops working after the first time.


My friend:
Router: Linksys wtr54g
ISP: Cox Communication @ Omaha, NE
OS: Windows XP Home SP1

Me:
Router: D-Link DI-524
ISP: Cox Communication @ Roanoke, VA
OS: Windows XP Pro SP2

If anyone has had this problem or knows how to fix this, please help!

[glc]

Friend got a new domain, it uses GoDaddy's forward IP: 64.202.187.170.

Reply from 64.202.189.170: bytes=32 time=80ms TTL=113

Is this a typo?

[ChoboSeki]

Originally Posted by glc Is this a typo?

That isn't a typo. I copy/pasted it. The problem still occurs:

My friend and I can't go to the domain ( http://stankyou.com ) on our wireless unless the wired connection has gone there first. But, even then, it will only work one time for us on wireless, then stop working until the wired connection goes there again.

Why did you ask if that was a typo? Sometimes, the wired can't even ping it, so just omit the ping part. Let's just replace it with telneting the server.



His server computer (wired):
C:\Documents and Settings\Administrator.GMDEV-OO9I6SADN>ping stankyou.com

Pinging stankyou.com [64.202.189.170] with 32 bytes of data:

Reply from 64.202.189.170: bytes=32 time=95ms TTL=115
Request timed out.


Even though it stopped pinging, it could still telnet and access the website.

[glc]

I asked if it was a typo because you posted 2 different IP's. My DNS lookup does show the 189 one to be correct. I can load your website but I cannot ping it. This is the page that loads:

http://serverm8.no-ip.info:82/news.php

What are you doing - hosting it on your own network with a nonstandard port and a dynamic DNS service? If that's the case, you have a firewall issue.

[ChoboSeki]

Originally Posted by glc I asked if it was a typo because you posted 2 different IP's. My DNS lookup does show the 189 one to be correct. I can load your website but I cannot ping it. This is the page that loads: http://serverm8.no-ip.info:82/news.php What are you doing - hosting it on your own network with a nonstandard port and a dynamic DNS service? If that's the case, you have a firewall issue.

Thanks for your reply, glc.

This isn't my server, it is my friend's. Even though you can't ping the IP, you still should be able to telnet it and be able to get forwarded from the domain. Nor his or my wireless computer can.

I have dual boot with the same OS on my other HDD. I tried that, and I could get to the website. The NIC was set for DHCP and had the IP of 192.168.0.16; on my main OS, I use a static IP, 192.168.0.165. Then, I thought it could be the router, since in Cisco's IT class I was in, we had that problem a lot where the router wouldn't let a computer using a certain IP access certain things.

I tried changing my IP to .16 and it didn't help.

I don't use any firewall or anti virus at all, and I have disabled the XP firewall service.

[glc]

Okay - then your friend may have a firewall issue. It appears to be reasonably secure because I can't ping it, it might be just a bit too secure. I have no idea why you are only having issues with wireless, but I'm giving you that info in hopes that it may contain a clue for you to go on. DNS appears to be fine being that I can load the website.