• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

OT:XP Pro and ISDN ?

ICXRa

Diamond Member
I was forced to format and reinstall my OS after a crash last Friday. It's a long story but finally (after discovering the problem was a stick of crucial RAM that had died) I made the move to XP Pro. I lost 5 days of crunching WU's thanks to this:|

I am using a 3Com US Robotics ISDN TA to dial into my ISP and having a lag between the time XP Pro tells me I am connected and actually being able to pull pages, ping or trace route. This problem does not exist while connecting with my Pipeline 75 ISDN router. Unfortunately telephone features (wife) prevent me from using the router for most of my online time due to poor BOD support. At first I had an issue with the pots ports ringing the wrong phone number but this was corrected by switching the SPID numbers (listing SPID one as SPID two and so on) in the properties. The lag issue however is still there. It takes somewhere in the area of 60 to 90 seconds before I can move packets after connection. This problem appears to be the same you would have in Win 9 X dialup connections if you had "Log into Network" checked or one of the network protocols that you don't need checked. I am dialing into an ISP which I worked for up until April of last year so I know exactly what they are doing as far as client side connectivity goes.

I am still very much a noob at XP Pro so if anyone has input on how to correct this I would greatly appreciate it😀
 


<< This problem appears to be the same you would have in Win 9 X dialup connections if you had "Log into Network" checked or one of the network protocols that you don't need checked. >>



Damn...I was reading all the way up to that point thinking that might be the problem. Are you using the XP firewall?
 
Back
Top