Open Forum → Free Server Rack Rail Kits to the Smartest Person

I think that's a great idea, and may rule out computer problems.
So I disconnected my network cable and connected the phone line to the modem port.
Then went into my connection to establish a dial up connection, but as I go through the process it doesn't let me select dial up, dial up is light gray and will not allow me to select that option.
So I rebooted (when in doubt, reboot) and same deal.
So I tried to select dial up through the advanced section and received and error:
Cannot load the remote access connection manager service. ERROR 711: a configure error on this computer is preventing this connection. For further info, bla, bla.

How do I get to where I can create a dial up connection?
Thoughts?
Paul

goto RUN, type SERVICES.MSC
make sure its set to manual (only runs on demand) or automatic (runs all the time).
EDIT....
its not recommended to set any of these services to disabled unless absolutely nesscessary

The remote access is set to manual, should I change it, I noticed yours is set to auto?
Thanks

I'm still trying to figure out why you paid so much for rails.

Check your MTU. For DSL it should probably be 1492 on the modem AND on your computer.

More fun fun stuff to try.

First would be to use an updated driver for your NIC card. Some older or offbrand cards have a problem handling DNS queries on unstable nameservers.

Second would be to see if the firewall thats with WinXP is turned off or on. Sometimes MS firewall will mess up a really nice machine. Also slows some connections on white box computers.

Third would be to go to a command prompt and run an
IPCONFIG /FLUSHDNS
then an IPCONFIG /REGISTERDNS
then a good old fashioned NBTSTAT -RR

Fourth would be to change out the NIC card entirely. Unless the box is brand schpankin new, NIC cards do fail. And considering a Worthwhile NIC is about 14.99, not that expensive of a solution.

Fifth would be to check on the DNS servers you are connecting to. If you can change to an alternate set of DNS Servers (There are listings of them alllllll over the internet) in your NIC card or router settings, do it and see if that clears up the problem.

Sixth would be to hard code (Type in the space for the DNS servers underneath the NIC card properties) the DNS addresses on the NIC card itself. This way you kind of beat a dead horse by forcing it to make sure that it looks for the DNS servers regardless of where the PPoE or Router thinks they are.

Let me know how this turns out.

Do an "ipconfig /all" at a command prompt and paste it here so we can see your IP settings.

Enter the following for a DNS server (64.246.44.72). Put that in manually under the tcp/ip settings of your network card.

Turn off any firewall you might have, and make sure you are not using a proxy server.

do "tracert www.usainfo.com" at a command prompt and let us know.

if that doesn't work then "tracert 65.199.46.80" You won't be able to trace all the way since the site blocks icmp, but we should at least see if you are getting outside your network.

Thanks,
Roger

A couple items first off:

1 - There are two sites: "www.usainfo.com" and "usainfo.com." They both resolve to different addresses and both have different content. We are interested only in the first, not the second, so any post containing "65.199.46.123" is barking up the wrong tree. On most all the DNS servers I have checked, including the authoritative servers for the domain (ns1 and ns2.usainfo.com) www.usainfo.com resolves to 65.199.46.80.

2 - OP indicates that he is trying to hit the site both by its DNS name and at IP address 205.218.243.165. This indicates that this problem is a DNS problem. Has nothing to do with the IP stack, modem, OS, etc.

Those two points should narrow the search considerably.

Now, it just so happens that 205.218.243.165 *is* in fact ns1.usainfo.com as someone mentioned in a prev post IIRC.

So the first thing I would do is type in 65.199.46.80 in your browser and see if the site comes up. I'm betting it will.

Next, compare the ipconfig /all output of the "working" and "non-working" PCs. It is possible that you may have different DNS servers on the two machines, but I am betting that is not the case. If my suspicion is correct the 98 PC has a static entry in its hosts file pointing www.usainfo.com to 65.199.46.80. That was probably how you fixed the issue the first time.

So as a temporary solution, you can duplicate the static entry in the other PC's host file.

The problem here is most likely that the organization that owns the DNS resolver that you are using has a remnant of the usainfo.com domain in a zone file. Since it recognizes the zone, it does not need to recursively look up the query, cuz it sees it locally (albeit incorrectly). I have seen this happen before especially with large (tier-one) ISPs. It is just an oversight.

If you were to contact that organization, point out to them that this is the case, they will delete their zone data for that domain, as they will recognize that they are no longer authoritative for that zone. At that point you should be able to rip out your static DNS entries and rock and roll.

HTH

kr

So now I am reading down lower, and I guess I need to retract the last post.

It seems you are in fact resolving the DNS name properly.

I would agree with the posts indicating a network problem.

Assuming that when you ping www.usainfo.com, you get the 65.199.46.80 address, then at this point you can just ignore everyone who is recommending any kind of DNS fix -- as that is not the problem and wont help you a bit.

Since you can hit everywhere else in the world except this site, that points to a filter/firewall/specific route problem, not a default gateway, global routing problem as has been suggested. Also, it is NOT trying hit 192.168.0.1 as others have suggested. NSLOOKUP states that 192.168.0.1 is the address of your DNS server (most likely the DLink that is in effect proxying DNS queries). 192.168.0.1 probably should be your def gw, as that is the address of the DLink.

The poster who recommended that you traceroute to the IP address is on the right track. Try tracing to the IP and to another site that you CAN access and see if their is any difference.

And just so we can be totally clear, when you ping www.usainfo.com (you will obviously not get an echo response as usainfo is filtering ICMP), what is the address that it resolves to? Is it in fact the 65.199.46.80 address?

kr

It would be tremendously helpful if you could post the following info from both working and non-working machines:

1 - ipconfig /all
2 - c:\windows\system32\drivers\etc\hosts
3 - ping www.usainfo.com
4 - tracert 65.199.46.80
5 - detail access method of both PCs -- are they using the same connection? do you get any different results when you plug the non-working PC into the working PCs modem/network topology?

kr

Also, when you tried to telnet earlier, you did a typo...

"Non-authoritative answer:
Name: usainfo.com
Address: 65.199.46.123

C:\>telnet 65.199.46.128 80
Connecting To 65.199.46.128...Could not open connection to the host, on port 80:
Connect failed"

Notice it resolved usainfo.com as 65.199.46.123 and then you typed telnet 65.199.46.128 80...

You might want to try that one again.

Thanks,
Roger