Error 2250

[bayanne]

This had got me beaten...

I have been unable to connect to PrimeNet and I have been getting Error 2250. This is only on 2 of the 4 boxen I have at my home pharm, the other 2 I have no problem with.

I thought that I would create a file primenet.ini with just the line Debug=1 and see what result I got.

Thus:

[Sun Dec 04 11:21:02 2005 - ver 24.14]
host = mersenne.org, port = 80
IP-addr = 0.0.0.0
Error in connect call: 10049

Can anyone advise what might be causing the problem.

[Prime95]

It can't find the IP address of mersenne.org. Perhaps it is cached on your working boxes.

You can EntropiaIP=64.66.6.250 to your primenet.ini file. That should work until the server moves to a new address.

[bayanne]

I've tried to add that to the file (exactly as you quoted) but still get an error 2250 ....

Exactly what should I put in the primenet.ini file?

Currently I have

Debug=1
EntropiaIP=64.66.6.250

I also tried

Debug=1
Host=http://64.66.6.250

and also

Debug=1
Host=http://64.66.6.250:80

Where would I flush the IP 0.0.0.0 from the system

I did get rid of any Temporary Internet files

[Prime95]

My bad. I looked at the source code and some time ago I remaned the option. Try "MersenneIP=64.66.6.250".

The 0.0.0.0 means that DNS lookups are not working on this computer. Why this is happening, I don't know. I know precious little about DNS lookups.

The cache reference was a bit of a red herring. It could be that all 4 boxes are broken, but the mersenne.org IP address happens to be cached somewhere on the two working boxes.

[bayanne]

No, that didn't work.

I am now going to have to trawl the web to see if I can find a way of clearing the cache. I did find one site which said that M$ automatic update can create a problem, but that seems to be connecting fine.

If anyone else has any suggestions ......

[PhilF]

In Windows XP, you can go to the Command Prompt (MS-DOS prompt), and type "ipconfig /flushdns" (without the quotes). I think that is true for earlier versions of Windows too. I doubt that will fix your problem though.

Do those machines have normal Internet connectivity, with only Prime95 having the problem?

[potonono]

Current MS products use ipconfig. Older products use winipcfg. Flushing the DNS only corrects the problem if the domain name servers have the correct IP and both non-working boxes have the correct DNS. "ipconfig /all" will list both DNS, so you can check to be sure the working boxes are using the same DNS as the non-working ones with. I don't recall if it's necessary or not, but I always do "ipconfig /registerdns" after flushing the current DNS, unless the DNServers are going to be changed in the interim.

You can check your hosts or lmosts file to be sure an incorrect IP isn't specified for the domain name on the non-working boxes. Assuming XP, they would both be in c:\windows\system32\drivers\etc\.

If a software or hardware firewall is inbetween the non-working boxes and your internet connection, you should check to verify if each box has the right access or priveliges.

[bayanne]

OK, ipconfig /flushdns and then ipconfig /registerdns did not change situation.
In the hosts file the ip specified is 127.0.0.1 local host

There is no firewall in place

[bayanne]

Well just to make sure I had no idea what was happening, both boxen are now communicating quite happily with the server. Definitely my first opportunity to use this emoticon...

[Frosty]

I'm a newbie. Getting the same Error 2250. Can't even browse the Mersenne.org website ... I eventually managed to find this site, locate a mirror, and downloaded Prime95 from tuatara.sdsu.edu ... but I am mystified as to the cause. I have checked out our corporate firewall (I am the IT Manager) and there are no blocks.

I can ping the server (www.mersenne.org). But FTP connections 'hang' and HTTP connections fail completely. Any ideas? I have rebooted several times. This behaviour has been observed for 24 hours now.

EDIT: Ping results show that DNS resolution seems fine:

C:\>ping www.mersenne.org

Pinging www.mersenne.org [64.66.6.250] with 32 bytes of data:

Reply from 64.66.6.250: bytes=32 time=204ms TTL=110
Reply from 64.66.6.250: bytes=32 time=201ms TTL=110
Reply from 64.66.6.250: bytes=32 time=208ms TTL=110
Reply from 64.66.6.250: bytes=32 time=205ms TTL=110

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

EDIT #2: Another 'sticky' thread shows 2250 as "server down" error, however I assumed that if its pingable its 'up'. If it is currently 'down' then if someone could just confirm that I will stop worrying about it and wait for it to sort itself out. Thanks!

[Frosty]

Came good finally, some time during the night here in Oz ... off and running now.