This almost sounds like video drivers got corrupted.
Just for SnGs boot from an XP CD, choose recovery console, and run the chkdsk /F /R command just in case there is any bad blocks or bad sectors.
Once that completes, see if you can log in. Once you can, then run sfc to check all the files...
Well finally got it fixed and it was the carrier.
Just an FYI...
The circuit was configured for 5ESS and it should of been DMS250, and the Swtich type was set to DEFAULT and it should of been set to MERIDIAN.
This was all on the carrier side. Of course, they played stupid and said "I am...
I asked our phone tech about this and what we did was put the CSU in loopback and the B channels went idle and stayed idle, so he thinks the card is fine.
We also confirmed that the D channel is configured as DMS 250, but need our carrier to confirm.
John,
I tried as suggested and I get a bunch of PRI227. The carrier(verizon is playing dumb) cannot confirm if there is the SL1PROF enabled on the circuit.
I did not have enough time to do the self test as this particular D channel is the source clock for a bunch of other TDMI tie lines.
Also, I see a bunch of PRI 227 errors
I am wondering if Verizon removed the SL1 Profile during some maintenance. I just found it odd that the Verizon tech did not know what I was talking about. I think he thought it was DMS 100.
We have one T1 coming from Verizon. Last Thursday I was notified that we could not make long distance calls, but local(because we have a route to send it through POTs lines).
I looked at the system and I saw errors of the D channel going down, then come back up. I ran a stat on loop 1, in ld...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.