Computer won't allow me to dial for 1 min+ after first showing the desktop

[megalomando]

Hi,

I just got connected to SBC Ameritech DSL. When the modem (D-Link 530TX+) is connected to the modem, I can not access the network connections or the shortcut for the modem on the desktop right away. I click on the shortcut and nothing happens. I click on start & connect to & nothing happens except the computer selectively locks certain functions like search. Other functions like add/remove programs always work.

Nothing happens for awhile and then the system clears all at once and all the things I clicked on happen in sequence but 60 seconds after I clicked on them. After this point everything seems to occur perfectly till I reboot the computer and the hang happens again.

The taskbar does not fill in the items it should display when I start either. When the tray is full, things are fine.

Here's what might help someone help me; If I turn off the 5360 DSL modem or unplug the lan cable to it, the problem goes away. So it's definitely related to the modem being connected.

Nothing shows in the device manager, I went to the D-link site and downloaded the newest firmware but all was current. I went to the motherboard manufacturer and flashed the newest bios to no change.

Somehow there are conflicts at bootup that do not allow me to open the device manager while they're happening and go away at the same time I can access the device manager.



Any ideas?
Thanks,

MM

[YeOldeStonecat]

I don't know what OS you are on....but I'll wager a bet it's Win2K or XP. NT based OS's are still "starting services" even when you get to desktop. They are still in the process of booting up. Unlike Win9X years ago, when you got to the desktop, the machine is pretty much done booting up.....you can get into things quickly.

[megalomando]

Hi YeOldeStonecat,

Yes, it's the dreaded XP I'm running.

Here's the rub: If I remove the CAT-5 cable from the ethernet card & start windows, I can immediately click on the icon to connect the DSL & immediately trys to connnect (but the card is not connected).

If... I then immediately connect the CAT-5 to the ethernet card when the desktop first shows, I can immediately connect to the internet.

If the Speedstream 5360 modem is connected when I start up, it takes well over a minute before I can connect.

ALso, If I choose to try to start the DSL connection by going to start > connect to; nothing happens (till the wait is over) but when the wait time is over I see the dropdown menu to select the connection (or "show all connections") appear and it persists on the desktop. It can't be moved or removed. Only a reboot removes it.

If I instead click on the desktop icon to connect & don't go through start button > connect to, nothing later persists on the screen but then again nothing appears to happen for those 80 seconds or so of limbo & then it does what I asked & connects.

Screwy, eh?

Now I'm having much trouble shutting down. I've never had problems with XP before, just when I installed the modem.

I think this expensive OS I bought sucks. (If it's microsoft's problem). There's nothing in their updates relating to this.

Any suggestions how to make things copasethic?

Thanks,

Meg

[YeOldeStonecat]

The 5360 is a great DSL modem, very fast. I've setup a lot of networks on it. But I use routers, with their PPPoE support, and don't have much experience using WinXP's built in PPPoE support....I'm guessing it's related to that.

Don't hold anything against XP....I think it's a great OS.

Not having much experience with XP's PPPoE and firewall, I'll let someone else step in.

[bmwrob]

I have the exact same problem. I’m using XP Pro and since I installed my 3com 3C905C-TX, I can use my computer for approx. 1.5 min after boot up. I used the “bootvis” program to see what was going on. It says “LOG+SERV” for approx 77 seconds. If I disconnect the RJ45 to the ADSL modem everything is okay. During this “hanging” if I start Win Explorer and try to access any drives I just get the search torch!

Would be great if someone knew what the problem was.

[megalomando]

Hi all,

I have a solution but no clear understanding as to what is happening. I connected a router in-between the modem and computer and all problems were immediately resolved.

I first went with the D-link DI-604 which did solve the problem of the enlongated delay & shut down but the documentation with the router was horrible and their tech help was worse than the documentation and they were unable to answer the most minimum of questions I had to call them about.

I returned the Dlink and bought a Linksys BEFSR41 Router for $49 after rebate & the directions with it were perfect & it only took 5 min to set it up & forget it.

Anyway, the reason for the XP bogging down appears to be some unmet command that is not being accessed when there is a 10/100 card in place but no router or equivilent in line.

Go figure...

Thanks

Meg

[bmwrob]

Finally my ?hanging boot? problem is solved! A technician from my ISP called me today. According to him, the problem occurs with some Win XP (Pro?) and NICs combinations, If DHCP is enabled! If this is the case the system tries to retrieve an IP address right after boot up. To solve it, he recommended adding a ?virtual? IP address. Basically I could pick anyone. Well I did and everything works as it should. If I check my configuration, I can see that the virtual IP used for the Ethernet adapter and one different for the PPP adapter which I guess is derived from the network.