Hey all,

I've installed Fedora Core 3 a number of times on multiple platforms. I've just installed Core 4 on an IBM Desktop as a dual boot machine with WindowsXP (personal computer in my office).

The install went fine - no problem. The problem I'm having is with SSH. When I try to connect; on the same network or elsewhere, it takes about 4 minutes to authenticate.

After I'm connected I have problems with lag (when connected off network).

When I ssh from the same network, it takes the same amount of time to authenticate, however I don't experience problems with lag.

It is my belief that something is up with this particular box, specifically with the OS. When I terminal into the same box using windows I have no problems.

I also have a FC3 server running in the same building down the hall. I don't experience any problems when I attempt to SSH into that machine. I'm currently connecting to the problem box through the aforementioned server so I don't experience lag once connected.

Any ideas???

I'm running ssh version OpenSSH_4.0p1, OpenSSL 0.9.7f 22 Mar 2005

Connecting through putty.

Try to shut down the firewall and make a test.

Thanks very much for the reply!

I thought of that myself. I shutdown the firewall last night and made another attempt - there was no change.

However I do have additional information for all of you to chew on.... When I arrived in my office this morning the entire computer was "acting" up. It took approximatly 3 to 4 mintues just to open terminal, I looked for memory leaks, but didn't find any. There were no processes taking abnormal amount of resources, and swap was not being used.

This is an IBM ThinkCentre. Running an Intel P4 3.06 HT, 512MB ram, Intel integrated graphics (intel 82865G), and I'm running Linux 2.6.11-1.1369_FC4smp.

Thanks again!

-D

Try a live CD to ensure this isn't a hardware problem. Knoppix or Slax will just do it.

Thanks for the reply!

After doing some research, it appears this is an IBM ThinkCentre problem. I've seen many forums with similar problems that I listed.

Example: http://lists.debian.org/debian-user/.../msg00698.html

Has anybody run across this? Have a quick fix?

Thanks!

reverse DNS?

Have similar issue with IBM Thinkcentre S50's, running 2.6.x kernels from several distros.

Fixed by updating BIOS to 2005/08/23.