Advertisement
If you have a new account but are having problems posting or verifying your account, please email us on hello@boards.ie for help. Thanks :)
Hello all! Please ensure that you are posting a new thread or question in the appropriate forum. The Feedback forum is overwhelmed with questions that are having to be moved elsewhere. If you need help to verify your account contact hello@boards.ie
Hi all! We have been experiencing an issue on site where threads have been missing the latest postings. The platform host Vanilla are working on this issue. A workaround that has been used by some is to navigate back a page or two to re-sync the thread and this will then show latest posts. Thanks, Mike.

Infuriating Dial up networking problem..HELP!

  • 06-04-2005 2:17pm
    #1
    Registered Users, Registered Users 2 Posts: 6,949 ✭✭✭


    okay, so a PC with using ISDN, running Win XP Pro sp2, one day decided that it is "unable to establish connection" and usually on the 5th attempt, it will say invalid username or password (which is BS!). Heres what I have tried so far.....

    1. Tried different ISP's no's & usernames etc, same problem with all of them!

    2. Tried same ISDN line with another computer with a USB ISDNmodem, works perfect!

    3. Tried same USB modem with Pc in question, same issue as above.

    4. Uninstalled & reinstalled necassary network protocols & clients, same problem.

    5. Ran a windows repair with SP1, no difference.

    6. Installed a 56k analogue modem for the crack after all the above, same problem as ISDN!

    Im out of ideas with the exception of a reinstall of windows as this seems to be an underlying OS problem.

    Numerous scans for virii with Nod32 & AVG turned nothing!

    Just wondering if anybody has had this issue before?


Comments

  • Registered Users, Registered Users 2 Posts: 931 ✭✭✭moridin


    Try connecting using your modem and hyperterminal going directly to the COM port.

    Whereby modem I mean the analogue modem, not your ISDN TA.

    Commands you could try running:
    AT&F
    ATx3DT12345 there 123435 is the number of your ISP.

    If you get a prompt on the screen looking for a login then you're able to get to the stage where the connection asks for a username/password.


  • Registered Users, Registered Users 2 Posts: 1,391 ✭✭✭fatherdougalmag


    I assume you plug your analog modem into the POTS/phone port on the ISDN box?

    What make is your ISDN adapter?


  • Moderators, Recreation & Hobbies Moderators, Science, Health & Environment Moderators, Technology & Internet Moderators Posts: 92,385 Mod ✭✭✭✭Capt'n Midnight


    http://support.microsoft.com/default.aspx?scid=kb;en-us;299357
    How to reset Internet Protocol (TCP/IP) in Windows XP

    netsh int ip reset resetlog.txt
    netsh int ip reset c:\resetlog.txt

    Don't think it will help but you can't uninstall TCP/IP in XP this refreshes the registry

    And I'm still stuck with an Error 50: the request is not supported / all devices connected

    try this too
    1890 923 204 / oceanfree / oceanfree


  • Registered Users, Registered Users 2 Posts: 6,949 ✭✭✭SouperComputer


    The PCI ISDN modem is an Eicon Diva.

    the machine is at home with me, but i have no ISDN, not that it matters as the issue occurs with andy dial-up connection.

    @moridin:

    I tried those commands, this is what I got:
    AT
    OK
    AT&F
    OK
    atx3dt1892150150
    CONNECT 49333 V42bis



    Successful Profile


    Entering PPP Session.
    IP address is 159.134.209.88
    MTU is 1524.
    ~ }#À!}!}!} }2}!}$}%ô}"}&} }*} } }'}"}(}"„~~ }#À!}!}!} }2}!}$}%ô}"}&} }*} } }'}
    "}(}"„~~ }#À!}!}!} }2}!}$}%ô}"}&} }*} } }'}"}(}"„~~ }#À!}!}!} }2}!}$}%ô}"}&} }
    *} } }'}"}(}"„~~ }#À!}!}!} }2}!}$}%ô}"}&} }*} } }'}"}(}"„~~ }#À!}!}!} }2}!}$}%
    ô}"}&} }*} } }'}"}(}"„~~ }#À!}!}!} }2}!}$}%ô}"}&} }*} } }'}"}(}"„~~ }#À!}!}!}
    }2}!}$}%ô}"}&} }*} } }'}"}(}"„~~ }#À!}!}!} }2}!}$}%ô}"}&} }*} } }'}"}(}"„~~ }#
    À!}!}!} }2}!}$}%ô}"}&} }*} } }'}"}(}"„~~ }#À!}!}!} }2}!}$}%ô}"}&} }*} } }'}"}(}
    "„~
    NO CARRIER



    im guessing that it is waiting for username and password at this stage.

    Having tried both your's and Capt'n ideas I still have the same problem.

    Im making an image of the HD so ill probably come back to it later to see if it can be solved. In the meantime, I have to get this running ASAP so im starting a reinstall now.

    thanks for your help


  • Registered Users, Registered Users 2 Posts: 1,391 ✭✭✭fatherdougalmag


    That's PPP starting to talk from the other side of the connection (i.e. that's good).


  • Advertisement
  • Registered Users, Registered Users 2 Posts: 6,949 ✭✭✭SouperComputer


    results of a ditrace
    C:\>ditrace -p <modem.txt
    12:42:36.902 R 0 DIMAINT - drv # 0 = 'DIMAINT' registered
    12:42:36.902 L 0 Maintenance_Tools maint/2.srv/nt 101-315 (Feb 8 2001 15:46:24)

    12:42:36.902 L 0 Microsoft (R) Windows NT [TM] 5.0 [Build 2600] UP
    12:42:36.902 L 0 Processor 0 - Vendor: GenuineIntel
    12:42:36.902 L 0 Processor 0 - Ident : x86 Family 15 Model 0 Stepping 7
    12:42:36.902 L 0 Processor 0 - Speed : ~1285 MHz
    12:42:36.902 L 0 Physical Memory : 255 MB
    12:42:36.902 L 0 SystemBiosDate : 11/30/00
    12:42:36.902 L 0 SystemBiosVersion : DELL - 1
    12:42:36.902 L 0 DiddRegisterAdapter - virtual IDI_DIDDPNP adapter on VSlot 0
    12:42:36.902 L 0 <Didd> - Loaded
    12:42:36.902 L 0 <Ioctl> - Loaded
    12:42:36.902 L 0 <DiMaint> - Loaded
    12:42:41.558 R 0 DIMAINT - drv # 1 = 'DIWAN' registered
    12:42:41.558 L 1 DIWAN - WAN Miniport Driver diwan/2.srv/nt 101-700 (Apr 12 2001
    19:25:03)
    12:42:41.558 L 1 DIWAN - NDIS 4.0 interface version registered
    12:42:41.558 R 0 DIMAINT - drv # 1 = 'DIWAN' deregistered
    --
    12:42:48.739 R 0 DIMAINT - drv # 1 = 'DIWAN' registered
    12:42:48.739 R 1 wmpInit - VendorSpecific\Logging = 0x1
    12:42:48.739 R 1 wmpInit - BusType = 0x5
    12:42:48.739 L 1 sys_ParseEnv - read of (ULONG) 'AutomaticReset' failed
    12:42:48.739 R 1 ialInit - CheckTimerInterval = 1000 ms
    12:42:48.739 R 1 ialInit - NoAnswerTimeout = 20 sec.
    12:42:48.739 R 1 ialInit - Protocol = "HDLC Transparent"
    12:42:48.739 R 1 idiInit - VendorSpecific\CardTypeNum = 0x27
    12:42:48.749 R 1 idiInit - WanEndpoints = 0x2
    12:42:48.749 R 1 idiInit - IsdnNumDChannels = 0x1
    12:42:48.749 R 1 idiInit - IsdnSwitchTypes = 0x3f6
    12:42:48.749 R 1 idiInit - IsdnSwitchType = 0x80
    12:42:48.749 L 1 sys_ParseEnv - read of (ULONG) 'ExtendedSwitchType' failed
    12:42:48.749 R 1 idiInit - environment variable 'ExtendedSwitchType' not found !
    !
    12:42:48.749 M 1 readMSNs - alloc addr 0x819c5790 / 1267 bytes
    12:42:48.749 L 1 sys_ParseEnv - read of (ULONG) 'NumberTypeMSN' failed
    12:42:48.749 R 1 idiInit - Line 0 NumberTypeMSN not available
    12:42:48.749 L 1 sys_ParseEnv - read of (ULONG) 'LineEndPoints' failed
    12:42:48.749 R 1 idiInit - Line 0 - set no number check
    12:42:48.749 L 1 DIVA-MULTI: DIVA Protocol Drivers for Windows NT (V7) protocol/
    3/nt.v7 101-31 Protocol 6.03(V7) 101-43 [NT5] (Apr 12 2001 18:59:23)
    12:42:48.749 R 1 SoParseNumbers:
    12:42:48.749 R 1 GetConfig: Cardtype 39 - "DIVA 2.01 S/T PCI"
    12:42:48.749 R 1 GetConfig: Protocol=ETSI Nt2=0 StableL2=1 Permanent=0 Tei=0
    12:42:48.749 R 1 GetResources: Memory#1 0xfbffd000 / len 4096
    12:42:48.749 E 1 GetResources: ignore resource type 0x81
    12:42:48.749 R 1 GetResources: Memory#2 0xfbffc000 / len 4096
    12:42:48.749 E 1 GetResources: ignore resource type 0x81
    12:42:48.749 R 1 GetResources: IRQ level 3 / vector 3
    12:42:48.749 R 1 GetResources: Memory#1 0xfbffd000 / len 4096
    12:42:48.749 E 1 GetResources: ignore resource type 0x81
    12:42:48.749 R 1 GetResources: Memory#2 0xfbffc000 / len 4096
    12:42:48.749 E 1 GetResources: ignore resource type 0x81
    12:42:48.749 R 1 GetResources: IRQ level 24 / vector 51
    12:42:48.749 L 1 #0: Use Memory 0xFBFFD000 / 0xFBFFC000 / IRQ 3
    12:42:48.949 L 0 DiddRegisterAdapter - Board DIVA 2.01 S/T PCI, VSlot 1, Cardtyp
    e 0x27
    12:42:48.949 L 1 idiInit - Adapter 1 (DIVA 2.01 S/T PCI) - ETSI 2 channels liste
    n Line 1
    12:42:48.949 L 1 idiInit - Adapter 1 (DIVA 2.01 S/T PCI) - ETSI number of B chan
    nels is 2
    12:42:48.949 M 1 ialInit - alloc addr 0xff6af000 / 4368 bytes
    12:42:48.949 R 1 ialSigInitialize - Line 0 ==> protocol code takes all numbers
    12:42:48.949 R 1 ialSigInitialize - Line 1 ==> protocol code takes all numbers
    12:42:48.949 L 1 ialInit - 1 card(s) 2 Instance(s) - Build 101-700 (Apr 12 2001/
    19:24:31)
    12:42:48.949 R 1 wmpInit - registration of IDI Abstraction Layer OK
    12:42:48.949 M 1 asyncInit - alloc addr 0xff6ac000 / 9444 bytes
    12:42:48.949 R 1 asyncInit - VendorSpecific\CheckFCS = 0xa
    12:42:48.949 R 1 wmpInit - registration of ASYNC/SYNC Conversion Layer OK
    12:42:48.949 M 1 shCbInit - alloc addr 0xff6ab008 / 1804 bytes
    12:42:48.949 R 1 shCbInit - VendorSpecific\ShortholdMode = 0x0
    12:42:48.949 R 1 shCbInit - VendorSpecific\ShortholdTime = 0x0
    12:42:48.949 R 1 shCbInit - VendorSpecific\IgnoreCallbackNumber = 0x1
    12:42:48.949 R 1 shCbInit - VendorSpecific\NumberChecking = 0x0
    12:42:48.949 R 1 shCbInit - VendorSpecific\NumberCheckingFile = ""
    12:42:48.949 R 1 shCbInit - VendorSpecific\CallbackPrefix = ""
    12:42:48.949 R 1 shCbInit - VendorSpecific\ForceAnalogBcOnCallback = 0x0
    12:42:48.949 R 1 wmpInit - registration of Shorthold/Callback Layer OK
    12:42:48.949 M 1 pppInit - alloc addr 0xff6aa008 / 2568 bytes
    12:42:48.949 R 1 pppInit - VendorSpecific\DiwanFeatures = 0x0
    12:42:48.949 R 1 wmpInit - registration of PPP Filter Layer OK
    12:42:48.949 M 1 tapiInit - alloc addr 0xff6a6000 / 13248 bytes
    12:42:48.949 R 1 tapiInit - VendorSpecific\DisabledServicesMask = 0x0
    12:42:48.949 R 1 tapiInit - VendorSpecific\DriverInstance = "2"
    12:42:48.949 R 1 tapiInit - NetworkAddress = 64.0.236.113.135.144
    12:42:48.949 R 1 wmpInit - registration of NDIS/TAPI Layer OK
    12:42:48.959 R 1 Line 0 ==> Signaling Entity 2 assigned [F#0007]
    12:42:48.959 R 1 Line 1 ==> Signaling Entity 3 assigned [F#0007]
    --
    12:44:20.010 R 0 DIMAINT - drv # 2 = 'CAPI20' registered
    12:44:20.010 L 2 CAPI20: Loading Build CAPI 2.0 for Windows NT capi/nt/1.srv 101
    -390 Feb 28 2001/09:44:51
    12:44:20.010 R 2 RegGetVal: DeviceName --> CAPI201
    12:44:20.010 R 2 RegGetVal: Manufacturer --> Eicon Technology
    12:44:20.010 R 2 RegGetVal: Logging --> 0x00000001
    12:44:20.010 R 2 RegGetVal: Manufacturer --> Eicon Technology
    12:44:20.010 L 2 CAPI20: Check DeviceName=CAPI201
    12:44:20.010 L 2 CAPI20: new adapter 0 --> Channels=2 Fax=0 Codec=0
    12:44:20.010 R 2 RegGetVal: ControllerCount --> 0x00000000
    12:44:20.010 R 2 CAPI20 - adapter DIVA 2.01 S/T PCI is controller 1 and 2 B-chan
    nels are possible
    12:44:20.010 R 2 RegGetVal: Manufacturer --> Eicon Technology
    12:44:20.010 L 2 CAPI20: Configuration stored in registry
    12:44:20.010 L 2 CAPI20: Loaded

    C:\>

    the log did not grow when I tried to establish the connection. It should also be noted that this log was run when trying a connetion thru a 56k modem as dont have ISDN here.


  • Registered Users, Registered Users 2 Posts: 1,391 ✭✭✭fatherdougalmag


    ditrace is the logging/diagnostic utility used with Eicon ISDN adapters - it won't log anything you do with your analog modem.

    Also, the idea is to redirect output to a file. Your 'ditrace -p <modem.txt' should actually be 'ditrace -p > modem.txt'. So do that, try your ISDN dial-up and when/if it fails, go back to the command prompt and hit CTRL-C. All of the ISDN activity will be logged to modem.txt.


  • Moderators, Recreation & Hobbies Moderators, Science, Health & Environment Moderators, Technology & Internet Moderators Posts: 92,385 Mod ✭✭✭✭Capt'n Midnight


    it says your MTU is 1524 - that sounds ok but you could check on the ISP side if you have ton of time to waste - second half of page
    http://www.mdgx.com/newtip8.htm

    http://support.microsoft.com/default.aspx?scid=kb;en-us;826159&Product=winxp
    Microsoft Windows Server 2003, Microsoft Windows 2000, and Microsoft Windows XP use a fixed MTU size of 1500 bytes for all PPP connections and use a fixed MTU size of 1400 bytes for all VPN connections.

    Check what it is on the working pc too.


  • Registered Users, Registered Users 2 Posts: 6,949 ✭✭✭SouperComputer


    ditrace is the logging/diagnostic utility used with Eicon ISDN adapters - it won't log anything you do with your analog modem.

    [penny drops!]

    hmm mtu semms to be ok.

    im giving up on this.............for now.

    any ideas what would have caused this> it only occured recently


  • Registered Users, Registered Users 2 Posts: 931 ✭✭✭moridin


    sorry, I forgot that I'd posted to this thread till now ;)

    Any luck on the re-install?

    IIRC, The no carrier generally means that you weren't able to correctly establish a connection to the other side.

    Given that it's happening on both your modem and ISDN it'd point towards a TCP/IP problem rather than a modem/TA one. The only way that I know of refreshing this in XP is the method that Capt posted.

    Sorry I can't be any more help, stuff like that is really screwed up :(


  • Advertisement
  • Moderators, Recreation & Hobbies Moderators, Science, Health & Environment Moderators, Technology & Internet Moderators Posts: 92,385 Mod ✭✭✭✭Capt'n Midnight


    With my RAS problem I'm getting similar junk in the script pop up box instead of Ascii

    http://www.michna.com/kb/wxnet.htm - I'm stepping through this

    This lot are for a different problem - PCMCIA / USB NIC's that did not uninstall completely just in case it had a knock on effect
    . http://support.microsoft.com/?kbid=315539
    . http://support.microsoft.com/?kbid=825826
    . http://support.microsoft.com/?kbid=269155


  • Registered Users, Registered Users 2 Posts: 1,391 ✭✭✭fatherdougalmag


    You might also be interested in this KB just in case the connection failure is due to some PPP negotiation failure.


  • Registered Users, Registered Users 2 Posts: 6,949 ✭✭✭SouperComputer


    as suspected, after a clean install the problem has been solved.

    F*** M$


Advertisement