This is a wierd one... My boinc client will not connect. I shut down my firewall and virus programs and I still couldn't connect. When I used your application for diagnosing my Windows' network. It said "Could not ping your localhost successfully...i.e. yourself!"
If anyone out there has an idea please reply to this message or mail me at [email protected]

---

Ok, WHO WROTE THAT BATCH FILE? I opened it up to see what it does, and either microsoft has chaneged the syntax for bactch files and tracert since WIN98, or the writer was not versed in MS-DOS! (I hope it's the earlier!) Anyhow, I ran the checks that the file was trying to preform, and have eliminated my ENTIRE NETWORK from the list of suspects. So now either it's whoever wrote boinc 4.45, which I doubt (Everyone else on this message board seems to have gotten theirs working), or v4.45 is incompatable with WIN98SE. So unless anyone else has any bright ideas (which you can mail to me... [email protected] or reply to this post...) I will search for either an older version of boinc manager, or a more compatable and equally stable OS (yea, right)

---

Which batch file are you talking about? Where did you get it from? What application for Windows network diagnosing? Are you the person with the external modem? If you dare to test it, would you dare to test development version 4.72 which has better modem support? (Get it from this download list)

---

... or reply to this post ...

oops, sorry. I replied to your other post in this thread disconnected

---

ralic's law of forums: Irrespective of any prior research done, you will find the solution to your question shortly after posting it to a public Internet forum, resulting in readers concluding that you have done no research on the matter whatsoever.

Ageless, I AM the person with the external modem, and I downloaded the batch file from Boinc Wiki. I read the disconnected post and found a link left for a person who also could not get their boinc manager to connect and followed the diagnosis instructions there. The batch file would not acknowledge my system passing the first test because of how the file was written (written for win xp maybe?) so I read the batch file and ran the checks manually (any good MS-DOS user can do that) starting with pinging the various sites (yes including 127.0.0.1) and then used traceroute to trace a route to the boinc server my boinc manager was trying to access.
All the checks worked fine, but the manager still wouldn't connect. I hope I have given you enough information to help me.
Thank you.

P.S. I don't really want to use 4.72 until it's OFFICALLY released. Unless someone with WIN98SE can personally vouch for the beta version...

---

Although we point to the Wiki at any possible time, do know it's written by people who crunch through Boinc for the projects. It's not officially written by UCB, the makers of Boinc. Hence the name of the Unofficial Boinc Wiki. ;)

Anyway, let me check around for that file. Can't say I tripped over it yet, can you give me a link?

---

Jord,

We have a little diagnostic batch file in the How-To on network troubleshooting.

The best guess I have is that the firewall is not letting BOINC out. I have also seen where prior installations that are working fine stop all of a sudden when you apply patches ... happened to me yesterday as a matter of fact. So, I had to add port 1043 to the firewall as an exception to a system that HAD been working fine.

---

Ah, found it and ran it... I see what's being said about who wrote that file. It thinks my default gateway lives on 0.0.0.138 ... right... Bad boy Tigher. ;)

One would also think it would open command.com instead of cmd.exe; if only since command.com is the DOS commandline.

If you take out the whole part of pinging the default gateway, it runs fine.

---

If you take out the whole part of pinging the default gateway, it runs fine.

Ok, even after a couple of drinks, I'm not sure if Neil is trying to connect from BOINC on his local host to his localhost or to another system. Time to summarise the problem here and determine the solution....methinks

[edit]
I mean, if you can't ping localhost, but you can ping 127.0.0.1, I'm open to further suggestions.
Beer talk, if you're offended, please excuse me. :)
[/edit]

---

ralic's law of forums: Irrespective of any prior research done, you will find the solution to your question shortly after posting it to a public Internet forum, resulting in readers concluding that you have done no research on the matter whatsoever.

I can ping localhost by handle and by 127.0.0.1, and tracert to both boinc sites works fine. I've theorized that the problem is not neccesarly with my system alone. It may be that my system just conflicts with the boinc manager, or boinc just doesn't like my system... EVERYTHING works fine except for the boinc manager. Even WITHOUT the firewall the boinc manager will not work.
Thank you for all your help and support, I will keep checking into this thread, and other dark aspects of my system to see if I can isolate a cause...
In the meantime I wait for microslop to stop supporting winXP, because by that time XP will run smoothly w/o MS intervention.

"If you can't make it good, at least make it look good" -Bill Gates

---

Ah, found it and ran it... I see what's being said about who wrote that file. It thinks my default gateway lives on 0.0.0.138 ... right... Bad boy Tigher. ;)

One would also think it would open command.com instead of cmd.exe; if only since command.com is the DOS commandline.

If you take out the whole part of pinging the default gateway, it runs fine.

Huh? Oh dear a complaint. tell me more? What version of Windows?
Ian

---

I can ping localhost by handle and by 127.0.0.1, and tracert to both boinc sites works fine. I've theorized that the problem is not neccesarly with my system alone. It may be that my system just conflicts with the boinc manager, or boinc just doesn't like my system... EVERYTHING works fine except for the boinc manager. Even WITHOUT the firewall the boinc manager will not work.
Thank you for all your help and support, I will keep checking into this thread, and other dark aspects of my system to see if I can isolate a cause...
In the meantime I wait for microslop to stop supporting winXP, because by that time XP will run smoothly w/o MS intervention.

"If you can't make it good, at least make it look good" -Bill Gates

Send me an ethereal trace if you want...saved as a libpcap file type. I will take a look and see what might be happening. Also what messages are you getting when trying to connect?

---

ooops mistake sorry

---

[quote]Ah, found it and ran it... I see what's being said about who wrote that file. It thinks my default gateway lives on 0.0.0.138 ... right... Bad boy Tigher. ;)

Just as I said, your little program believes my gateway sits on 0.0.0.138 ... it misses the 10 at the start. ;)

So without the default gateway correctly identified, it will error out. Telling me as much as: You do not have an internet connection, go fix that first.

Weird that.
(me sends this off through pigeon carrier :D)

---

Just as I said, your little program believes my gateway sits on 0.0.0.138 ... it misses the 10 at the start. ;)

So without the default gateway correctly identified, it will error out. Telling me as much as: You do not have an internet connection, go fix that first.

Weird that.
(me sends this off through pigeon carrier :D)

LOL :)
Are you using XP?
I was only able to test it on XP and Win 2003 Server Enterprise Edition. It worked OK on them.

---

No, I am using Windows 2000 SP4, ADSL connected via a multi-PC modem that contains a switch.

XP... brrrr... blasphemy, go wash your mouth and fingers. ;)

---

No, I am using Windows 2000 SP4, ADSL connected via a multi-PC modem that contains a switch.

XP... brrrr... blasphemy, go wash your mouth and fingers. ;)

Hmmmm OK all washed up here now :)
Would you run "ipconfig /all" and redriect to a file so you can copy and paste it here please. Also I presume your gateway address started "10." yes?

Thanks

(ps - as an ex Win 2k user I can say Xp is actually very stable - I like it. The best thing MS have ever done I think.)

---

Windows 2000 IP Configuration

Host Name . . . . . . . . . . . . : {censored}
Primary DNS Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Broadcast
IP Routing Enabled. . . . . . . . : Yes
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : lan

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . : lan
Description . . . . . . . . . . . : Realtek RTL8139/810x Family Fast Eth
ernet NIC
Physical Address. . . . . . . . . : 00-50-FC-72-68-99
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 10.0.0.151
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 10.0.0.138
DHCP Server . . . . . . . . . . . : 10.0.0.138
DNS Servers . . . . . . . . . . . : 10.0.0.138
Lease Obtained. . . . . . . . . . : 25 September 2005 18:07:05
Lease Expires . . . . . . . . . . : 25 September 2005 20:07:05

---

Windows 2000 IP Configuration

Host Name . . . . . . . . . . . . : {censored}
Primary DNS Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Broadcast
IP Routing Enabled. . . . . . . . : Yes
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : lan

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . : lan
Description . . . . . . . . . . . : Realtek RTL8139/810x Family Fast Eth
ernet NIC
Physical Address. . . . . . . . . : 00-50-FC-72-68-99
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 10.0.0.151
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 10.0.0.138
DHCP Server . . . . . . . . . . . : 10.0.0.138
DNS Servers . . . . . . . . . . . : 10.0.0.138
Lease Obtained. . . . . . . . . . : 25 September 2005 18:07:05
Lease Expires . . . . . . . . . . : 25 September 2005 20:07:05

Thanks. OK. I have to pick out this data based on position as dos string functions are basicially awful. It looks like win 2000 output is different to both XP and win 2003 server. I will ask Paul to note this in the Wiki so people know. If I find a string somewhere that will tell me its win 2000 I will try a condition around it and see if we can take the warning off. Thanks for pointing it out.

Regards
Ian

---

It looks the same to me ... what is different and what did you want me to add to the Wiki?

---