A Windows XP help forum. PCbanter

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Go Back   Home » PCbanter forum » Microsoft Windows 7 » Windows 7 Forum
Reload this Page Problems with connecting to Internet via Linux but Win7Pro connectseasily.
Site Map Home Register Authors List Search Today's Posts Mark Forums Read Web Partners

Problems with connecting to Internet via Linux but Win7Pro connectseasily.


« Previous Thread | Next Thread »

 
 
Thread Tools Rate Thread Display Modes
  #1  
Old March 7th 19, 12:06 PM posted to alt.windows7.general
Daniel60
external usenet poster
  
Posts: 72
Default Problems with connecting to Internet via Linux but Win7Pro connectseasily.
I dual boot this HP 6730b Laptop with Win7Pro and Mageia Linux.

I can connect to the Internet on Win7Pro using my 3G USB Dongle but
cannot via the Dongle with my Linux .... at the moment!! It did, but not
now!!

I can see the Linux trying to make a connection, but it quickly gets a
"NO CARRIER" signal. In Linux, when it did work, the sequence ended like
this ....

Feb 23 19:51:38 localhost chat[15206]: AT+CGATT?^M^M
Feb 23 19:51:38 localhost chat[15206]: +CGATT: 1^M
Feb 23 19:51:38 localhost chat[15206]: ^M
Feb 23 19:51:38 localhost chat[15206]: OK
Feb 23 19:51:38 localhost chat[15206]: -- got it
Feb 23 19:51:38 localhost chat[15206]: send (ATDT*99***3#^M)
Feb 23 19:51:38 localhost chat[15206]: timeout set to 120 seconds
Feb 23 19:51:38 localhost chat[15206]: expect (CONNECT)
Feb 23 19:51:38 localhost chat[15206]: ^M
Feb 23 19:51:38 localhost chat[15206]: ATDT*99***3#^M^M
Feb 23 19:51:38 localhost chat[15206]: CONNECT
Feb 23 19:51:38 localhost chat[15206]: -- got it
Feb 23 19:51:38 localhost chat[15206]: send (^M)
Feb 23 19:51:38 localhost chat[15206]: timeout set to 5 seconds

(Note the fourth last line .... CONNECT.)

Again, on Linux, when it doesn't work, it ended like this ....

Mar 03 16:32:52 localhost chat[12336]: AT+CGATT?^M^M
Mar 03 16:32:52 localhost chat[12336]: +CGATT: 1^M
Mar 03 16:32:52 localhost chat[12336]: ^M
Mar 03 16:32:52 localhost chat[12336]: OK
Mar 03 16:32:52 localhost chat[12336]: -- got it
Mar 03 16:32:52 localhost chat[12336]: send (ATDT*99***3#^M)
Mar 03 16:32:52 localhost chat[12336]: timeout set to 120 seconds
Mar 03 16:32:52 localhost chat[12336]: expect (CONNECT)
Mar 03 16:32:52 localhost chat[12336]: ^M
Mar 03 16:32:52 localhost chat[12336]: ATDT*99***3#^M^M
Mar 03 16:32:52 localhost chat[12336]: NO CARRIER
Mar 03 16:32:52 localhost chat[12336]: -- failed
Mar 03 16:32:52 localhost chat[12336]: Failed (NO CARRIER)

(Note the third last line ... NO CARRIER.)

I am wanting to see if the signals sent to/received from the Dongle are
similar in Win7. Does anyone know where I might look to see what's going
on when I press the "Connect" button on the Win7 Wireless Broadband
Program?? Can I look at a file/log, somewhere, that gets written to when
making a connection or something??

--
Daniel
Ads
  #2  
Old March 7th 19, 02:33 PM posted to alt.windows7.general
dave61430[_2_]
external usenet poster
  
Posts: 31
Default Problems with connecting to Internet via Linux but Win7Proconnects easily.
On Thu, 07 Mar 2019 23:06:46 +1100, Daniel60 wrote:

I dual boot this HP 6730b Laptop with Win7Pro and Mageia Linux.

I can connect to the Internet on Win7Pro using my 3G USB Dongle but
cannot via the Dongle with my Linux .... at the moment!! It did, but not
now!!

I can see the Linux trying to make a connection, but it quickly gets a
"NO CARRIER" signal. In Linux, when it did work, the sequence ended like
this ....

Not all usb wireless dongles work with linux, I find Panda models work
well.
  #3  
Old March 7th 19, 07:41 PM posted to alt.windows7.general
Paul[_32_]
external usenet poster
  
Posts: 11,873
Default Problems with connecting to Internet via Linux but Win7Pro connectseasily.
Daniel60 wrote:
I dual boot this HP 6730b Laptop with Win7Pro and Mageia Linux.

I can connect to the Internet on Win7Pro using my 3G USB Dongle but
cannot via the Dongle with my Linux .... at the moment!! It did, but not
now!!

I can see the Linux trying to make a connection, but it quickly gets a
"NO CARRIER" signal. In Linux, when it did work, the sequence ended like
this ....

Feb 23 19:51:38 localhost chat[15206]: AT+CGATT?^M^M
Feb 23 19:51:38 localhost chat[15206]: +CGATT: 1^M
Feb 23 19:51:38 localhost chat[15206]: ^M
Feb 23 19:51:38 localhost chat[15206]: OK
Feb 23 19:51:38 localhost chat[15206]: -- got it
Feb 23 19:51:38 localhost chat[15206]: send (ATDT*99***3#^M)
Feb 23 19:51:38 localhost chat[15206]: timeout set to 120 seconds
Feb 23 19:51:38 localhost chat[15206]: expect (CONNECT)
Feb 23 19:51:38 localhost chat[15206]: ^M
Feb 23 19:51:38 localhost chat[15206]: ATDT*99***3#^M^M
Feb 23 19:51:38 localhost chat[15206]: CONNECT
Feb 23 19:51:38 localhost chat[15206]: -- got it
Feb 23 19:51:38 localhost chat[15206]: send (^M)
Feb 23 19:51:38 localhost chat[15206]: timeout set to 5 seconds

(Note the fourth last line .... CONNECT.)

Again, on Linux, when it doesn't work, it ended like this ....

Mar 03 16:32:52 localhost chat[12336]: AT+CGATT?^M^M
Mar 03 16:32:52 localhost chat[12336]: +CGATT: 1^M
Mar 03 16:32:52 localhost chat[12336]: ^M
Mar 03 16:32:52 localhost chat[12336]: OK
Mar 03 16:32:52 localhost chat[12336]: -- got it
Mar 03 16:32:52 localhost chat[12336]: send (ATDT*99***3#^M)
Mar 03 16:32:52 localhost chat[12336]: timeout set to 120 seconds
Mar 03 16:32:52 localhost chat[12336]: expect (CONNECT)
Mar 03 16:32:52 localhost chat[12336]: ^M
Mar 03 16:32:52 localhost chat[12336]: ATDT*99***3#^M^M
Mar 03 16:32:52 localhost chat[12336]: NO CARRIER
Mar 03 16:32:52 localhost chat[12336]: -- failed
Mar 03 16:32:52 localhost chat[12336]: Failed (NO CARRIER)

(Note the third last line ... NO CARRIER.)

I am wanting to see if the signals sent to/received from the Dongle are
similar in Win7. Does anyone know where I might look to see what's going
on when I press the "Connect" button on the Win7 Wireless Broadband
Program?? Can I look at a file/log, somewhere, that gets written to when
making a connection or something??


Here's an idea for Windows. I've not tried this, as
I have nothing I can rely on to generate log events.

http://www.i-helpdesk.com.au/index.p...ndows-ppp-logs

Run 'cmd' in 'startrun'

type 'netsh'

type 'ras'

type 'set tracing PPP enable'

[presumably, type 'exit' ???]

Look for C:\windows\tracing\, find PPP.log

And who knows, it might not work the same way in all Windows versions.

Since you have "No carrier" on Linux, that suggests
some module is missing to provide a driver. Or maybe
some "firmware" that needs to be loaded into the unit
during boot, that isn't happening. You could try, in
Linux, "lsmod" and review the modules in usage. Something
like that. Firmwares might be in /lib/firmware.
And run "dmesg" and review what is happening during
the boot process.

HTH,
Paul
  #4  
Old March 10th 19, 06:00 AM posted to alt.windows7.general
Daniel60
external usenet poster
  
Posts: 72
Default Problems with connecting to Internet via Linux but Win7Proconnects easily.
Paul wrote on 8/03/2019 6:41 AM:
Daniel60 wrote:
I dual boot this HP 6730b Laptop with Win7Pro and Mageia Linux.

I can connect to the Internet on Win7Pro using my 3G USB Dongle but
cannot via the Dongle with my Linux .... at the moment!! It did, but
not now!!

I can see the Linux trying to make a connection, but it quickly gets a
"NO CARRIER" signal. In Linux, when it did work, the sequence ended
like this ....

Feb 23 19:51:38 localhost chat[15206]: AT+CGATT?^M^M
Feb 23 19:51:38 localhost chat[15206]: +CGATT: 1^M
Feb 23 19:51:38 localhost chat[15206]: ^M
Feb 23 19:51:38 localhost chat[15206]: OK
Feb 23 19:51:38 localhost chat[15206]:Â* -- got it
Feb 23 19:51:38 localhost chat[15206]: send (ATDT*99***3#^M)
Feb 23 19:51:38 localhost chat[15206]: timeout set to 120 seconds
Feb 23 19:51:38 localhost chat[15206]: expect (CONNECT)
Feb 23 19:51:38 localhost chat[15206]: ^M
Feb 23 19:51:38 localhost chat[15206]: ATDT*99***3#^M^M
Feb 23 19:51:38 localhost chat[15206]: CONNECT
Feb 23 19:51:38 localhost chat[15206]:Â* -- got it
Feb 23 19:51:38 localhost chat[15206]: send (^M)
Feb 23 19:51:38 localhost chat[15206]: timeout set to 5 seconds

(Note the fourth last line .... CONNECT.)

Again, on Linux, when it doesn't work, it ended like this ....

Mar 03 16:32:52 localhost chat[12336]: AT+CGATT?^M^M
Mar 03 16:32:52 localhost chat[12336]: +CGATT: 1^M
Mar 03 16:32:52 localhost chat[12336]: ^M
Mar 03 16:32:52 localhost chat[12336]: OK
Mar 03 16:32:52 localhost chat[12336]:Â* -- got it
Mar 03 16:32:52 localhost chat[12336]: send (ATDT*99***3#^M)
Mar 03 16:32:52 localhost chat[12336]: timeout set to 120 seconds
Mar 03 16:32:52 localhost chat[12336]: expect (CONNECT)
Mar 03 16:32:52 localhost chat[12336]: ^M
Mar 03 16:32:52 localhost chat[12336]: ATDT*99***3#^M^M
Mar 03 16:32:52 localhost chat[12336]: NO CARRIER
Mar 03 16:32:52 localhost chat[12336]:Â* -- failed
Mar 03 16:32:52 localhost chat[12336]: Failed (NO CARRIER)

(Note the third last line ... NO CARRIER.)

I am wanting to see if the signals sent to/received from the Dongle
are similar in Win7. Does anyone know where I might look to see what's
going on when I press the "Connect" button on the Win7 Wireless
Broadband Program?? Can I look at a file/log, somewhere, that gets
written to when making a connection or something??


Here's an idea for Windows. I've not tried this, as
I have nothing I can rely on to generate log events.

http://www.i-helpdesk.com.au/index.p...ndows-ppp-logs


Â*Â* Run 'cmd' in 'startrun'

Â*Â* type 'netsh'

Â*Â* type 'ras'

Â*Â* type 'set tracing PPP enable'

Â*Â* [presumably, type 'exit' ???]

Â*Â* Look for C:\windows\tracing\, find PPP.log

And who knows, it might not work the same way in all Windows versions.

Since you have "No carrier" on Linux, that suggests
some module is missing to provide a driver. Or maybe
some "firmware" that needs to be loaded into the unit
during boot, that isn't happening. You could try, in
Linux, "lsmod" and review the modules in usage. Something
like that. Firmwares might be in /lib/firmware.
And run "dmesg" and review what is happening during
the boot process.

HTH,
Â*Â*Â* Paul

Thanks for this, Paul. I'll report back.
--
Daniel
  #5  
Old March 10th 19, 06:03 AM posted to alt.windows7.general
Daniel60
external usenet poster
  
Posts: 72
Default Problems with connecting to Internet via Linux but Win7Proconnects easily.
dave61430 wrote on 8/03/2019 1:33 AM:
On Thu, 07 Mar 2019 23:06:46 +1100, Daniel60 wrote:

I dual boot this HP 6730b Laptop with Win7Pro and Mageia Linux.

I can connect to the Internet on Win7Pro using my 3G USB Dongle but
cannot via the Dongle with my Linux .... at the moment!! It did, but not
now!!

I can see the Linux trying to make a connection, but it quickly gets a
"NO CARRIER" signal. In Linux, when it did work, the sequence ended like
this ....

Not all usb wireless dongles work with linux, I find Panda models work
well.

Thanks, Dave, but the one that I use did connect, nightly, for several
days following my updating the system .... then stopped working without
my further updating the system again!! ;-(

--
Daniel
  #6  
Old March 10th 19, 08:50 AM posted to alt.windows7.general
Daniel60
external usenet poster
  
Posts: 72
Default Problems with connecting to Internet via Linux but Win7Proconnects easily.
Daniel60 wrote on 10/03/2019 5:00 PM:
Paul wrote on 8/03/2019 6:41 AM:
Daniel60 wrote:
I dual boot this HP 6730b Laptop with Win7Pro and Mageia Linux.

I can connect to the Internet on Win7Pro using my 3G USB Dongle but
cannot via the Dongle with my Linux .... at the moment!! It did, but
not now!!

I can see the Linux trying to make a connection, but it quickly gets
a "NO CARRIER" signal. In Linux, when it did work, the sequence ended
like this ....

Feb 23 19:51:38 localhost chat[15206]: AT+CGATT?^M^M
Feb 23 19:51:38 localhost chat[15206]: +CGATT: 1^M
Feb 23 19:51:38 localhost chat[15206]: ^M
Feb 23 19:51:38 localhost chat[15206]: OK
Feb 23 19:51:38 localhost chat[15206]:Â* -- got it
Feb 23 19:51:38 localhost chat[15206]: send (ATDT*99***3#^M)
Feb 23 19:51:38 localhost chat[15206]: timeout set to 120 seconds
Feb 23 19:51:38 localhost chat[15206]: expect (CONNECT)
Feb 23 19:51:38 localhost chat[15206]: ^M
Feb 23 19:51:38 localhost chat[15206]: ATDT*99***3#^M^M
Feb 23 19:51:38 localhost chat[15206]: CONNECT
Feb 23 19:51:38 localhost chat[15206]:Â* -- got it
Feb 23 19:51:38 localhost chat[15206]: send (^M)
Feb 23 19:51:38 localhost chat[15206]: timeout set to 5 seconds

(Note the fourth last line .... CONNECT.)

Again, on Linux, when it doesn't work, it ended like this ....

Mar 03 16:32:52 localhost chat[12336]: AT+CGATT?^M^M
Mar 03 16:32:52 localhost chat[12336]: +CGATT: 1^M
Mar 03 16:32:52 localhost chat[12336]: ^M
Mar 03 16:32:52 localhost chat[12336]: OK
Mar 03 16:32:52 localhost chat[12336]:Â* -- got it
Mar 03 16:32:52 localhost chat[12336]: send (ATDT*99***3#^M)
Mar 03 16:32:52 localhost chat[12336]: timeout set to 120 seconds
Mar 03 16:32:52 localhost chat[12336]: expect (CONNECT)
Mar 03 16:32:52 localhost chat[12336]: ^M
Mar 03 16:32:52 localhost chat[12336]: ATDT*99***3#^M^M
Mar 03 16:32:52 localhost chat[12336]: NO CARRIER
Mar 03 16:32:52 localhost chat[12336]:Â* -- failed
Mar 03 16:32:52 localhost chat[12336]: Failed (NO CARRIER)

(Note the third last line ... NO CARRIER.)

I am wanting to see if the signals sent to/received from the Dongle
are similar in Win7. Does anyone know where I might look to see
what's going on when I press the "Connect" button on the Win7
Wireless Broadband Program?? Can I look at a file/log, somewhere,
that gets written to when making a connection or something??


Here's an idea for Windows. I've not tried this, as
I have nothing I can rely on to generate log events.

http://www.i-helpdesk.com.au/index.p...ndows-ppp-logs


Â*Â*Â* Run 'cmd' in 'startrun'

Â*Â*Â* type 'netsh'

Â*Â*Â* type 'ras'

Â*Â*Â* type 'set tracing PPP enable'

Â*Â*Â* [presumably, type 'exit' ???]

Â*Â*Â* Look for C:\windows\tracing\, find PPP.log

And who knows, it might not work the same way in all Windows versions.

Since you have "No carrier" on Linux, that suggests
some module is missing to provide a driver. Or maybe
some "firmware" that needs to be loaded into the unit
during boot, that isn't happening. You could try, in
Linux, "lsmod" and review the modules in usage. Something
like that. Firmwares might be in /lib/firmware.
And run "dmesg" and review what is happening during
the boot process.

HTH,
Â*Â*Â*Â* Paul

Thanks for this, Paul. I'll report back.

Thanks, again, Paul. I did as the web page instructed and, lo and
behold, I've got a log ......

[3608] 03-10 17:12:34:767: RemoveFromTimerQ called
portid=0,Id=0,Protocol=c029,EventType=0,fAuth=0
[3608] 03-10 17:12:34:767: LcpEnd
[3608] 03-10 17:12:34:767: Post line down event occurred on port 9
[3608] 03-10 17:12:34:767: NotifyCaller(hPort=9, dwMsgId=25)
[3488] 03-10 19:01:10:730: UninitializeProtocolEngine called
[3488] 03-10 19:01:10:730: UninitializeProtocolEngine: Waiting For
Worker Thread to exit.
[3608] 03-10 19:01:10:730: All clients disconnected PPP-Stopped
[3608] 03-10 19:01:10:730: RasCpInit(80fd, FALSE)
[3608] 03-10 19:01:10:777: RasCpInit(8021, FALSE)
[3608] 03-10 19:01:11:104: RasCpInit(c223, FALSE)
[3608] 03-10 19:01:11:292: RasCpInit(c227, FALSE)
[3608] 03-10 19:01:11:292: RasCpInit(c023, FALSE)
[3340] 03-10 19:06:31:795: RasCpEnumProtocolIds
[3340] 03-10 19:06:31:795: Protocol 8021
[3340] 03-10 19:06:31:795: Protocol c029
[3340] 03-10 19:06:31:795: Protocol 80fd
[3340] 03-10 19:06:31:795: Protocol c227
[3340] 03-10 19:06:31:795: Protocol c023
[3340] 03-10 19:06:31:795: Protocol 8057
[3340] 03-10 19:06:31:795: RasCpEnumProtocolIds
[3340] 03-10 19:06:31:795: Protocol 8021
[3340] 03-10 19:06:31:795: Protocol c029
[3340] 03-10 19:06:31:795: Protocol 80fd
[3340] 03-10 19:06:31:795: Protocol c227
[3340] 03-10 19:06:31:795: Protocol c023
[3340] 03-10 19:06:31:795: Protocol 8057
[3340] 03-10 19:06:31:795: RasCpGetInfo 8057
[3340] 03-10 19:06:31:795: RasCpGetInfo c023
[3340] 03-10 19:06:31:795: RasCpInit(c023, TRUE)
[3340] 03-10 19:06:31:795: RasCpGetInfo c227
[3340] 03-10 19:06:31:795: RasCpInit(c227, TRUE)
[3340] 03-10 19:06:31:795: RasCpGetInfo 80fd
[3340] 03-10 19:06:31:795: RasCpInit(80fd, TRUE)
[3340] 03-10 19:06:31:795: RasCpGetInfo c029
[3340] 03-10 19:06:31:795: RasCpGetInfo 8021
[3340] 03-10 19:06:31:795: RasCpInit(c223, TRUE)
[3340] 03-10 19:06:31:810: PPP Initialized successfully.
[3408] 03-10 19:06:31:920: Processing protocol event
[3408] 03-10 19:06:31:920: Processing protocol event
[3408] 03-10 19:06:31:920: Adding IP

A bit worrying, though, that the log file seems to started a couple of
days ago as, at the top of my file .....

[3564] 16:32:19:486: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
|................|
[3564] 03-08 16:32:19:533:
[3564] 03-08 16:32:19:533: InsertInTimerQ called
portid=0,Id=5,Protocol=8021,EventType=0,fAuth=0,Ti meout=1
[3464] 03-08 16:32:20:531: Packet received (30 bytes) for hPort 9
[3564] 03-08 16:32:20:531: PPP packet received at 03/08/2019 05:32:20:531
[3564] 03-08 16:32:20:531: Protocol = IPCP, Type = Configure-Nak,
Length = 0x1e, Id = 0x5, Port = 9

Note the dates 03-08 !! March 8th, I'm guessing

Could it be that Win7 is always writing this log and the instructions
given merely just make the file visible, effectively??
--
Daniel
  #7  
Old March 10th 19, 01:14 PM posted to alt.windows7.general
Paul[_32_]
external usenet poster
  
Posts: 11,873
Default Problems with connecting to Internet via Linux but Win7Pro connectseasily.
Daniel60 wrote:
Daniel60 wrote on 10/03/2019 5:00 PM:
Paul wrote on 8/03/2019 6:41 AM:
Daniel60 wrote:
I dual boot this HP 6730b Laptop with Win7Pro and Mageia Linux.

I can connect to the Internet on Win7Pro using my 3G USB Dongle but
cannot via the Dongle with my Linux .... at the moment!! It did, but
not now!!

I can see the Linux trying to make a connection, but it quickly gets
a "NO CARRIER" signal. In Linux, when it did work, the sequence
ended like this ....

Feb 23 19:51:38 localhost chat[15206]: AT+CGATT?^M^M
Feb 23 19:51:38 localhost chat[15206]: +CGATT: 1^M
Feb 23 19:51:38 localhost chat[15206]: ^M
Feb 23 19:51:38 localhost chat[15206]: OK
Feb 23 19:51:38 localhost chat[15206]: -- got it
Feb 23 19:51:38 localhost chat[15206]: send (ATDT*99***3#^M)
Feb 23 19:51:38 localhost chat[15206]: timeout set to 120 seconds
Feb 23 19:51:38 localhost chat[15206]: expect (CONNECT)
Feb 23 19:51:38 localhost chat[15206]: ^M
Feb 23 19:51:38 localhost chat[15206]: ATDT*99***3#^M^M
Feb 23 19:51:38 localhost chat[15206]: CONNECT
Feb 23 19:51:38 localhost chat[15206]: -- got it
Feb 23 19:51:38 localhost chat[15206]: send (^M)
Feb 23 19:51:38 localhost chat[15206]: timeout set to 5 seconds

(Note the fourth last line .... CONNECT.)

Again, on Linux, when it doesn't work, it ended like this ....

Mar 03 16:32:52 localhost chat[12336]: AT+CGATT?^M^M
Mar 03 16:32:52 localhost chat[12336]: +CGATT: 1^M
Mar 03 16:32:52 localhost chat[12336]: ^M
Mar 03 16:32:52 localhost chat[12336]: OK
Mar 03 16:32:52 localhost chat[12336]: -- got it
Mar 03 16:32:52 localhost chat[12336]: send (ATDT*99***3#^M)
Mar 03 16:32:52 localhost chat[12336]: timeout set to 120 seconds
Mar 03 16:32:52 localhost chat[12336]: expect (CONNECT)
Mar 03 16:32:52 localhost chat[12336]: ^M
Mar 03 16:32:52 localhost chat[12336]: ATDT*99***3#^M^M
Mar 03 16:32:52 localhost chat[12336]: NO CARRIER
Mar 03 16:32:52 localhost chat[12336]: -- failed
Mar 03 16:32:52 localhost chat[12336]: Failed (NO CARRIER)

(Note the third last line ... NO CARRIER.)

I am wanting to see if the signals sent to/received from the Dongle
are similar in Win7. Does anyone know where I might look to see
what's going on when I press the "Connect" button on the Win7
Wireless Broadband Program?? Can I look at a file/log, somewhere,
that gets written to when making a connection or something??


Here's an idea for Windows. I've not tried this, as
I have nothing I can rely on to generate log events.

http://www.i-helpdesk.com.au/index.p...ndows-ppp-logs


Run 'cmd' in 'startrun'

type 'netsh'

type 'ras'

type 'set tracing PPP enable'

[presumably, type 'exit' ???]

Look for C:\windows\tracing\, find PPP.log

And who knows, it might not work the same way in all Windows versions.

Since you have "No carrier" on Linux, that suggests
some module is missing to provide a driver. Or maybe
some "firmware" that needs to be loaded into the unit
during boot, that isn't happening. You could try, in
Linux, "lsmod" and review the modules in usage. Something
like that. Firmwares might be in /lib/firmware.
And run "dmesg" and review what is happening during
the boot process.

HTH,
Paul

Thanks for this, Paul. I'll report back.

Thanks, again, Paul. I did as the web page instructed and, lo and
behold, I've got a log ......

[3608] 03-10 17:12:34:767: RemoveFromTimerQ called
portid=0,Id=0,Protocol=c029,EventType=0,fAuth=0
[3608] 03-10 17:12:34:767: LcpEnd
[3608] 03-10 17:12:34:767: Post line down event occurred on port 9
[3608] 03-10 17:12:34:767: NotifyCaller(hPort=9, dwMsgId=25)
[3488] 03-10 19:01:10:730: UninitializeProtocolEngine called
[3488] 03-10 19:01:10:730: UninitializeProtocolEngine: Waiting For
Worker Thread to exit.
[3608] 03-10 19:01:10:730: All clients disconnected PPP-Stopped
[3608] 03-10 19:01:10:730: RasCpInit(80fd, FALSE)
[3608] 03-10 19:01:10:777: RasCpInit(8021, FALSE)
[3608] 03-10 19:01:11:104: RasCpInit(c223, FALSE)
[3608] 03-10 19:01:11:292: RasCpInit(c227, FALSE)
[3608] 03-10 19:01:11:292: RasCpInit(c023, FALSE)
[3340] 03-10 19:06:31:795: RasCpEnumProtocolIds
[3340] 03-10 19:06:31:795: Protocol 8021
[3340] 03-10 19:06:31:795: Protocol c029
[3340] 03-10 19:06:31:795: Protocol 80fd
[3340] 03-10 19:06:31:795: Protocol c227
[3340] 03-10 19:06:31:795: Protocol c023
[3340] 03-10 19:06:31:795: Protocol 8057
[3340] 03-10 19:06:31:795: RasCpEnumProtocolIds
[3340] 03-10 19:06:31:795: Protocol 8021
[3340] 03-10 19:06:31:795: Protocol c029
[3340] 03-10 19:06:31:795: Protocol 80fd
[3340] 03-10 19:06:31:795: Protocol c227
[3340] 03-10 19:06:31:795: Protocol c023
[3340] 03-10 19:06:31:795: Protocol 8057
[3340] 03-10 19:06:31:795: RasCpGetInfo 8057
[3340] 03-10 19:06:31:795: RasCpGetInfo c023
[3340] 03-10 19:06:31:795: RasCpInit(c023, TRUE)
[3340] 03-10 19:06:31:795: RasCpGetInfo c227
[3340] 03-10 19:06:31:795: RasCpInit(c227, TRUE)
[3340] 03-10 19:06:31:795: RasCpGetInfo 80fd
[3340] 03-10 19:06:31:795: RasCpInit(80fd, TRUE)
[3340] 03-10 19:06:31:795: RasCpGetInfo c029
[3340] 03-10 19:06:31:795: RasCpGetInfo 8021
[3340] 03-10 19:06:31:795: RasCpInit(c223, TRUE)
[3340] 03-10 19:06:31:810: PPP Initialized successfully.
[3408] 03-10 19:06:31:920: Processing protocol event
[3408] 03-10 19:06:31:920: Processing protocol event
[3408] 03-10 19:06:31:920: Adding IP

A bit worrying, though, that the log file seems to started a couple of
days ago as, at the top of my file .....

[3564] 16:32:19:486: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
|................|
[3564] 03-08 16:32:19:533:
[3564] 03-08 16:32:19:533: InsertInTimerQ called
portid=0,Id=5,Protocol=8021,EventType=0,fAuth=0,Ti meout=1
[3464] 03-08 16:32:20:531: Packet received (30 bytes) for hPort 9
[3564] 03-08 16:32:20:531: PPP packet received at 03/08/2019 05:32:20:531
[3564] 03-08 16:32:20:531: Protocol = IPCP, Type = Configure-Nak,
Length = 0x1e, Id = 0x5, Port = 9

Note the dates 03-08 !! March 8th, I'm guessing

Could it be that Win7 is always writing this log and the instructions
given merely just make the file visible, effectively??

Might the log have been turned on previously ?

That's probably the easiest explanation.

Paul
 



« Previous Thread | Next Thread »

Thread Tools
Display Modes Rate This Thread
Linear Mode Linear Mode
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
vB code is On
Smilies are On
[IMG] code is On
HTML code is Off






All times are GMT +1. The time now is 02:18 AM.

Feed Icon - Contact Us - Windows XP Help Forum home - FAQ - Links - Privacy Statement - Top

Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2023, Jelsoft Enterprises Ltd.
Copyright ©2004-2023 PCbanter.
The comments are property of their posters.