Hardware: Imac G4 700, G3 350, IBook SE DV

Software: OSX 10.2.4, FMPro 5.5 (also tried FMPro 6 Trial version)

Soooo...

we have little network set up, the Imac being the host computer and the others connecting to it as clients. Aside from speed issues this has always worked like a charm.

We have been using a local Cable service thorugh which we also connect to the host DB via TCP/IP.

Just yesterday we switched to a faster xDSL line, got a new modem, hooked it up to the router, and here's where the strange behaviour started: The host DB on the IMac takes much much longer to start up, something like 5-10 minutes or so (previously: about 20secs). If we host the DB on the other computers, however, it opens as fast as it should.

Performance, once started up, is as fast it was before.

Same goes for Filemaker Server, which we aren't using but tried, just for kicks: hosted on the G3, connected to from the IMac, it takes the same amount of time to open.

When switching back to the cable modem, the startup speed goes back to normal.

We tried different cables, tried assigning different IP numbers, checked Prefs and Settings in both OS and FMPro, everything seems to be exactly the same on all three computers.

The only difference between the two providers (Cable & xDSL) is the following: Our Cable service assigned specific IP numbers to specific Ethernet cards (or MAC Numbers?), the xDSL service gave us a range to choose from. Otherwise nothing has changed, the router connected to the modem is still the same, the cables are the same, the prefs and settings are the same.

Now, this is nothing dangerous for us, but it really makes life a lot more difficult and we just cannot for the life of us figure out what the reason could be.

any help would be greatly appreciated!!!

thanks and best regards,

bates

Duplicate post.

I had a customer who had a similar problem - - -somewhat. All network settings were correct, but his email and internet was snail slow on a DSL.

I suggested swapping the ethernet cable to the DSL modem, but turned out to be the modem itself was bad! Service provider swapped the hardware, and all is well.

Mabe a hint somewhere here that can help . . .