Wireless Network Problems


R

Richard Beilby

We are having all sorts of wireless networking problems. The router/AP
continually crashes, work-stations are re-connecting for no apparent
reason. The o/s in use are w98se, w2k and xp. If I keep on a notebook
running w98se, then the problem ease. Below is an extract from the event
log for the w2k m/c. Can anyone please explain the reasons for these
messages.

Event Type: Warning
Event Source: Dhcp
Event Category: None
Event ID: 1003
Date: 20/01/2005
Time: 08:32:55
User: N/A
Computer: BEILBYJHB
Description:
Your computer was not able to renew its address from the network (from
the DHCP Server) for the Network Card with network address
0080C82FC0A4. The following error occurred:
The semaphore timeout period has expired. . Your computer will continue
to try and obtain an address on its own from the network address (DHCP)
server.
Data:
0000: 79 00 00 00 y...

Event Type: Information
Event Source: BROWSER
Event Category: None
Event ID: 8033
Date: 20/01/2005
Time: 08:32:55
User: N/A
Computer: BEILBYJHB
Description:
The browser has forced an election on network
\Device\NetBT_Tcpip_{E984FBCE-2974-438E-BA2D-A216884CEBED} because a
master browser was stopped.

Event Type: Warning
Event Source: Dhcp
Event Category: None
Event ID: 1006
Date: 20/01/2005
Time: 08:32:57
User: N/A
Computer: BEILBYJHB
Description:
Your computer was unable to automatically configure the IP parameters
for the Network Card with the network address 0080C82FC0A4. The
following error occurred during configuration: The parameter is
incorrect. .
Data:
0000: 57 00 00 00 W...

Event Type: Warning
Event Source: Dhcp
Event Category: None
Event ID: 1003
Date: 20/01/2005
Time: 09:16:54
User: N/A
Computer: BEILBYJHB
Description:
Your computer was not able to renew its address from the network (from
the DHCP Server) for the Network Card with network address
0080C82FC0A4. The following error occured:
The semaphore timeout period has expired. . Your computer will continue
to try and obtain an address on its own from the network address (DHCP)
server.
Data:
0000: 79 00 00 00 y...

Event Type: Information
Event Source: BROWSER
Event Category: None
Event ID: 8033
Date: 20/01/2005
Time: 09:16:54
User: N/A
Computer: BEILBYJHB
Description:
The browser has forced an election on network
\Device\NetBT_Tcpip_{E984FBCE-2974-438E-BA2D-A216884CEBED} because a
master browser was stopped.

Event Type: Warning
Event Source: Dhcp
Event Category: None
Event ID: 1006
Date: 20/01/2005
Time: 09:16:56
User: N/A
Computer: BEILBYJHB
Description:
Your computer was unable to automatically configure the IP parameters
for the Network Card with the network address 0080C82FC0A4. The
following error occurred during configuration: The parameter is
incorrect. .
Data:
0000: 57 00 00 00 W...

Event Type: Error
Event Source: Server
Event Category: None
Event ID: 2505
Date: 20/01/2005
Time: 09:17:11
User: N/A
Computer: BEILBYJHB
Description:
The server could not bind to the transport \Device\NetbiosSmb because
another computer on the network has the same name. The server could not
start.
Data:
0000: 34 00 00 00 4...

Event Type: Warning
Event Source: Dhcp
Event Category: None
Event ID: 1003
Date: 20/01/2005
Time: 09:50:03
User: N/A
Computer: BEILBYJHB
Description:
Your computer was not able to renew its address from the network (from
the DHCP Server) for the Network Card with network address
0080C82FC0A4. The following error occured:
The semaphore timeout period has expired. . Your computer will continue
to try and obtain an address on its own from the network address (DHCP)
server.
Data:
0000: 79 00 00 00 y...

Event Type: Information
Event Source: BROWSER
Event Category: None
Event ID: 8033
Date: 20/01/2005
Time: 09:50:04
User: N/A
Computer: BEILBYJHB
Description:
The browser has forced an election on network
\Device\NetBT_Tcpip_{E984FBCE-2974-438E-BA2D-A216884CEBED} because a
master browser was stopped.

Event Type: Warning
Event Source: Dhcp
Event Category: None
Event ID: 1006
Date: 20/01/2005
Time: 09:50:06
User: N/A
Computer: BEILBYJHB
Description:
Your computer was unable to automatically configure the IP parameters
for the Network Card with the network address 0080C82FC0A4. The
following error occurred during configuration: The parameter is
incorrect. .
Data:
0000: 57 00 00 00 W...

Event Type: Error
Event Source: Server
Event Category: None
Event ID: 2505
Date: 20/01/2005
Time: 09:50:17
User: N/A
Computer: BEILBYJHB
Description:
The server could not bind to the transport
\Device\NetBT_Tcpip_{E984FBCE-2974-438E-BA2D-A216884CEBED} because
another computer on the network has the same name. The server could not
start.
Data:
0000: 34 00 00 00 4...

Event Type: Error
Event Source: Server
Event Category: None
Event ID: 2505
Date: 20/01/2005
Time: 09:50:17
User: N/A
Computer: BEILBYJHB
Description:
The server could not bind to the transport \Device\NetbiosSmb because
another computer on the network has the same name. The server could not
start.
Data:
0000: 34 00 00 00 4...

Event Type: Information
Event Source: BROWSER
Event Category: None
Event ID: 8033
Date: 20/01/2005
Time: 09:55:26
User: N/A
Computer: BEILBYJHB
Description:
The browser has forced an election on network
\Device\NetBT_Tcpip_{E984FBCE-2974-438E-BA2D-A216884CEBED} because a
master browser was stopped.
 
Ad

Advertisements

G

Guest

What exactly do you mean when you say your AP "continually crashes?"

This looks like a typical signal loss situation to me. Go download Net
Stumbler and start doing some analysis.
 
R

Richard Beilby

By "continually crashes", I mean exactly that. It crashes and resets
itself. No log reports, just restarts. I do not think the problems are
due to loss of signal through the signal being weak. I am confident the
problems are due to hardware or software bugs. The frequency of the
disconnection, reconnection, etc.

Below is a sample of the report from Net Stumbler:-

# $Creator: Network Stumbler Version 0.4.0
# $Format: wi-scan
# Latitude Longitude ( SSID ) Type ( BSSID ) Time (GMT) [ SNR Sig Noise
]
# $DateGMT: 2005-01-22
N 0.0000000 E 0.0000000 ( BC ) BBS ( 00:0f:3d:3a:1d:f8 ) 08:48:49 (GMT)
[ 46 95 49 ]
N 0.0000000 E 0.0000000 ( BC ) BBS ( 00:0f:3d:3a:1d:f8 ) 08:48:50 (GMT)
[ 47 96 49 ]
N 0.0000000 E 0.0000000 ( BC ) BBS ( 00:0f:3d:3a:1d:f8 ) 08:48:51 (GMT)
[ 47 96 49 ]
N 0.0000000 E 0.0000000 ( BC ) BBS ( 00:0f:3d:3a:1d:f8 ) 08:48:52 (GMT)
[ 46 95 49 ]
N 0.0000000 E 0.0000000 ( BC ) BBS ( 00:0f:3d:3a:1d:f8 ) 08:48:53 (GMT)
[ 46 95 49 ]
N 0.0000000 E 0.0000000 ( BC ) BBS ( 00:0f:3d:3a:1d:f8 ) 08:48:54 (GMT)
[ 47 96 49 ]
N 0.0000000 E 0.0000000 ( BC ) BBS ( 00:0f:3d:3a:1d:f8 ) 08:48:55 (GMT)
[ 47 96 49 ]
N 0.0000000 E 0.0000000 ( BC ) BBS ( 00:0f:3d:3a:1d:f8 ) 08:48:56 (GMT)
[ 46 95 49 ]
N 0.0000000 E 0.0000000 ( BC ) BBS ( 00:0f:3d:3a:1d:f8 ) 08:48:57 (GMT)
[ 46 95 49 ]
N 0.0000000 E 0.0000000 ( BC ) BBS ( 00:0f:3d:3a:1d:f8 ) 08:48:58 (GMT)
[ 47 96 49 ]
N 0.0000000 E 0.0000000 ( BC ) BBS ( 00:0f:3d:3a:1d:f8 ) 08:48:59 (GMT)
[ 47 96 49 ]
N 0.0000000 E 0.0000000 ( BC ) BBS ( 00:0f:3d:3a:1d:f8 ) 08:49:00 (GMT)
[ 47 96 49 ]
N 0.0000000 E 0.0000000 ( BC ) BBS ( 00:0f:3d:3a:1d:f8 ) 08:49:01 (GMT)
[ 47 96 49 ]
N 0.0000000 E 0.0000000 ( BC ) BBS ( 00:0f:3d:3a:1d:f8 ) 08:49:02 (GMT)
[ 46 95 49 ]
N 0.0000000 E 0.0000000 ( BC ) BBS ( 00:0f:3d:3a:1d:f8 ) 08:49:03 (GMT)
[ 46 95 49 ]
N 0.0000000 E 0.0000000 ( BC ) BBS ( 00:0f:3d:3a:1d:f8 ) 08:49:04 (GMT)
[ 47 96 49 ]
N 0.0000000 E 0.0000000 ( BC ) BBS ( 00:0f:3d:3a:1d:f8 ) 08:49:05 (GMT)
[ 47 96 49 ]
N 0.0000000 E 0.0000000 ( BC ) BBS ( 00:0f:3d:3a:1d:f8 ) 08:49:06 (GMT)
[ 46 95 49 ]
N 0.0000000 E 0.0000000 ( BC ) BBS ( 00:0f:3d:3a:1d:f8 ) 08:49:07 (GMT)
[ 46 95 49 ]
N 0.0000000 E 0.0000000 ( BC ) BBS ( 00:0f:3d:3a:1d:f8 ) 08:49:08 (GMT)
[ 49 98 49 ]
N 0.0000000 E 0.0000000 ( BC ) BBS ( 00:0f:3d:3a:1d:f8 ) 08:49:09 (GMT)
[ 49 98 49 ]
N 0.0000000 E 0.0000000 ( BC ) BBS ( 00:0f:3d:3a:1d:f8 ) 08:49:10 (GMT)
[ 48 97 49 ]
N 0.0000000 E 0.0000000 ( BC ) BBS ( 00:0f:3d:3a:1d:f8 ) 08:49:12 (GMT)
[ 48 97 49 ]
N 0.0000000 E 0.0000000 ( BC ) BBS ( 00:0f:3d:3a:1d:f8 ) 08:49:13 (GMT)
[ 48 97 49 ]
N 0.0000000 E 0.0000000 ( BC ) BBS ( 00:0f:3d:3a:1d:f8 ) 08:49:14 (GMT)
[ 48 97 49 ]
N 0.0000000 E 0.0000000 ( BC ) BBS ( 00:0f:3d:3a:1d:f8 ) 08:49:15 (GMT)
[ 48 97 49 ]
N 0.0000000 E 0.0000000 ( BC ) BBS ( 00:0f:3d:3a:1d:f8 ) 08:49:16 (GMT)
[ 48 97 49 ]
N 0.0000000 E 0.0000000 ( BC ) BBS ( 00:0f:3d:3a:1d:f8 ) 08:49:17 (GMT)
[ 48 97 49 ]
N 0.0000000 E 0.0000000 ( BC ) BBS ( 00:0f:3d:3a:1d:f8 ) 08:49:18 (GMT)
[ 48 97 49 ]
N 0.0000000 E 0.0000000 ( BC ) BBS ( 00:0f:3d:3a:1d:f8 ) 08:49:19 (GMT)
[ 48 97 49 ]
N 0.0000000 E 0.0000000 ( BC ) BBS ( 00:0f:3d:3a:1d:f8 ) 08:49:20 (GMT)
[ 48 97 49 ]
N 0.0000000 E 0.0000000 ( BC ) BBS ( 00:0f:3d:3a:1d:f8 ) 08:49:21 (GMT)
[ 48 97 49 ]
N 0.0000000 E 0.0000000 ( BC ) BBS ( 00:0f:3d:3a:1d:f8 ) 08:49:22 (GMT)
[ 48 97 49 ]
N 0.0000000 E 0.0000000 ( BC ) BBS ( 00:0f:3d:3a:1d:f8 ) 08:49:23 (GMT)
[ 48 97 49 ]
N 0.0000000 E 0.0000000 ( BC ) BBS ( 00:0f:3d:3a:1d:f8 ) 08:49:24 (GMT)
[ 48 97 49 ]
N 0.0000000 E 0.0000000 ( BC ) BBS ( 00:0f:3d:3a:1d:f8 ) 08:49:25 (GMT)
[ 48 97 49 ]
N 0.0000000 E 0.0000000 ( BC ) BBS ( 00:0f:3d:3a:1d:f8 ) 08:49:26 (GMT)
[ 48 97 49 ]
N 0.0000000 E 0.0000000 ( BC ) BBS ( 00:0f:3d:3a:1d:f8 ) 08:49:27 (GMT)
[ 48 97 49 ]
N 0.0000000 E 0.0000000 ( BC ) BBS ( 00:0f:3d:3a:1d:f8 ) 08:49:28 (GMT)
[ 47 96 49 ]
N 0.0000000 E 0.0000000 ( BC ) BBS ( 00:0f:3d:3a:1d:f8 ) 08:49:29 (GMT)
[ 47 96 49 ]
N 0.0000000 E 0.0000000 ( BC ) BBS ( 00:0f:3d:3a:1d:f8 ) 08:49:31 (GMT)
[ 48 97 49 ]
N 0.0000000 E 0.0000000 ( BC ) BBS ( 00:0f:3d:3a:1d:f8 ) 08:49:32 (GMT)
[ 48 97 49 ]
N 0.0000000 E 0.0000000 ( BC ) BBS ( 00:0f:3d:3a:1d:f8 ) 08:49:33 (GMT)
[ 48 97 49 ]
N 0.0000000 E 0.0000000 ( BC ) BBS ( 00:0f:3d:3a:1d:f8 ) 08:49:34 (GMT)
[ 47 96 49 ]
N 0.0000000 E 0.0000000 ( BC ) BBS ( 00:0f:3d:3a:1d:f8 ) 08:49:35 (GMT)
[ 47 96 49 ]
N 0.0000000 E 0.0000000 ( BC ) BBS ( 00:0f:3d:3a:1d:f8 ) 08:49:36 (GMT)
[ 47 96 49 ]
N 0.0000000 E 0.0000000 ( BC ) BBS ( 00:0f:3d:3a:1d:f8 ) 08:49:37 (GMT)
[ 47 96 49 ]
N 0.0000000 E 0.0000000 ( BC ) BBS ( 00:0f:3d:3a:1d:f8 ) 08:49:38 (GMT)
[ 48 97 49 ]
N 0.0000000 E 0.0000000 ( BC ) BBS ( 00:0f:3d:3a:1d:f8 ) 08:49:39 (GMT)
[ 48 97 49 ]
N 0.0000000 E 0.0000000 ( BC ) BBS ( 00:0f:3d:3a:1d:f8 ) 08:49:40 (GMT)
[ 50 99 49 ]
N 0.0000000 E 0.0000000 ( BC ) BBS ( 00:0f:3d:3a:1d:f8 ) 08:49:41 (GMT)
[ 50 99 49 ]
N 0.0000000 E 0.0000000 ( BC ) BBS ( 00:0f:3d:3a:1d:f8 ) 08:49:42 (GMT)
[ 47 96 49 ]
N 0.0000000 E 0.0000000 ( BC ) BBS ( 00:0f:3d:3a:1d:f8 ) 08:49:43 (GMT)
[ 47 96 49 ]
N 0.0000000 E 0.0000000 ( BC ) BBS ( 00:0f:3d:3a:1d:f8 ) 08:49:44 (GMT)
[ 48 97 49 ]
N 0.0000000 E 0.0000000 ( BC ) BBS ( 00:0f:3d:3a:1d:f8 ) 08:49:45 (GMT)
[ 48 97 49 ]
N 0.0000000 E 0.0000000 ( BC ) BBS ( 00:0f:3d:3a:1d:f8 ) 08:49:46 (GMT)
[ 48 97 49 ]
N 0.0000000 E 0.0000000 ( BC ) BBS ( 00:0f:3d:3a:1d:f8 ) 08:49:47 (GMT)
[ 48 97 49 ]
N 0.0000000 E 0.0000000 ( BC ) BBS ( 00:0f:3d:3a:1d:f8 ) 08:49:48 (GMT)
[ 48 97 49 ]
N 0.0000000 E 0.0000000 ( BC ) BBS ( 00:0f:3d:3a:1d:f8 ) 08:49:49 (GMT)
[ 48 97 49 ]
N 0.0000000 E 0.0000000 ( BC ) BBS ( 00:0f:3d:3a:1d:f8 ) 08:49:50 (GMT)
[ 48 97 49 ]
 
G

Guest

Sounds like your WAP is the problem then. What brand/model is it? Have you
checked for a BIOS update?

Richard Beilby said:
By "continually crashes", I mean exactly that. It crashes and resets
itself. No log reports, just restarts. I do not think the problems are
due to loss of signal through the signal being weak. I am confident the
problems are due to hardware or software bugs. The frequency of the
disconnection, reconnection, etc.

Below is a sample of the report from Net Stumbler:-

# $Creator: Network Stumbler Version 0.4.0
# $Format: wi-scan
# Latitude Longitude ( SSID ) Type ( BSSID ) Time (GMT) [ SNR Sig Noise
]
# $DateGMT: 2005-01-22
N 0.0000000 E 0.0000000 ( BC ) BBS ( 00:0f:3d:3a:1d:f8 ) 08:48:49 (GMT)
[ 46 95 49 ]
N 0.0000000 E 0.0000000 ( BC ) BBS ( 00:0f:3d:3a:1d:f8 ) 08:48:50 (GMT)
[ 47 96 49 ]
N 0.0000000 E 0.0000000 ( BC ) BBS ( 00:0f:3d:3a:1d:f8 ) 08:48:51 (GMT)
[ 47 96 49 ]
N 0.0000000 E 0.0000000 ( BC ) BBS ( 00:0f:3d:3a:1d:f8 ) 08:48:52 (GMT)
[ 46 95 49 ]
N 0.0000000 E 0.0000000 ( BC ) BBS ( 00:0f:3d:3a:1d:f8 ) 08:48:53 (GMT)
[ 46 95 49 ]
N 0.0000000 E 0.0000000 ( BC ) BBS ( 00:0f:3d:3a:1d:f8 ) 08:48:54 (GMT)
[ 47 96 49 ]
N 0.0000000 E 0.0000000 ( BC ) BBS ( 00:0f:3d:3a:1d:f8 ) 08:48:55 (GMT)
[ 47 96 49 ]
N 0.0000000 E 0.0000000 ( BC ) BBS ( 00:0f:3d:3a:1d:f8 ) 08:48:56 (GMT)
[ 46 95 49 ]
N 0.0000000 E 0.0000000 ( BC ) BBS ( 00:0f:3d:3a:1d:f8 ) 08:48:57 (GMT)
[ 46 95 49 ]
N 0.0000000 E 0.0000000 ( BC ) BBS ( 00:0f:3d:3a:1d:f8 ) 08:48:58 (GMT)
[ 47 96 49 ]
N 0.0000000 E 0.0000000 ( BC ) BBS ( 00:0f:3d:3a:1d:f8 ) 08:48:59 (GMT)
[ 47 96 49 ]
N 0.0000000 E 0.0000000 ( BC ) BBS ( 00:0f:3d:3a:1d:f8 ) 08:49:00 (GMT)
[ 47 96 49 ]
N 0.0000000 E 0.0000000 ( BC ) BBS ( 00:0f:3d:3a:1d:f8 ) 08:49:01 (GMT)
[ 47 96 49 ]
N 0.0000000 E 0.0000000 ( BC ) BBS ( 00:0f:3d:3a:1d:f8 ) 08:49:02 (GMT)
[ 46 95 49 ]
N 0.0000000 E 0.0000000 ( BC ) BBS ( 00:0f:3d:3a:1d:f8 ) 08:49:03 (GMT)
[ 46 95 49 ]
N 0.0000000 E 0.0000000 ( BC ) BBS ( 00:0f:3d:3a:1d:f8 ) 08:49:04 (GMT)
[ 47 96 49 ]
N 0.0000000 E 0.0000000 ( BC ) BBS ( 00:0f:3d:3a:1d:f8 ) 08:49:05 (GMT)
[ 47 96 49 ]
N 0.0000000 E 0.0000000 ( BC ) BBS ( 00:0f:3d:3a:1d:f8 ) 08:49:06 (GMT)
[ 46 95 49 ]
N 0.0000000 E 0.0000000 ( BC ) BBS ( 00:0f:3d:3a:1d:f8 ) 08:49:07 (GMT)
[ 46 95 49 ]
N 0.0000000 E 0.0000000 ( BC ) BBS ( 00:0f:3d:3a:1d:f8 ) 08:49:08 (GMT)
[ 49 98 49 ]
N 0.0000000 E 0.0000000 ( BC ) BBS ( 00:0f:3d:3a:1d:f8 ) 08:49:09 (GMT)
[ 49 98 49 ]
N 0.0000000 E 0.0000000 ( BC ) BBS ( 00:0f:3d:3a:1d:f8 ) 08:49:10 (GMT)
[ 48 97 49 ]
N 0.0000000 E 0.0000000 ( BC ) BBS ( 00:0f:3d:3a:1d:f8 ) 08:49:12 (GMT)
[ 48 97 49 ]
N 0.0000000 E 0.0000000 ( BC ) BBS ( 00:0f:3d:3a:1d:f8 ) 08:49:13 (GMT)
[ 48 97 49 ]
N 0.0000000 E 0.0000000 ( BC ) BBS ( 00:0f:3d:3a:1d:f8 ) 08:49:14 (GMT)
[ 48 97 49 ]
N 0.0000000 E 0.0000000 ( BC ) BBS ( 00:0f:3d:3a:1d:f8 ) 08:49:15 (GMT)
[ 48 97 49 ]
N 0.0000000 E 0.0000000 ( BC ) BBS ( 00:0f:3d:3a:1d:f8 ) 08:49:16 (GMT)
[ 48 97 49 ]
N 0.0000000 E 0.0000000 ( BC ) BBS ( 00:0f:3d:3a:1d:f8 ) 08:49:17 (GMT)
[ 48 97 49 ]
N 0.0000000 E 0.0000000 ( BC ) BBS ( 00:0f:3d:3a:1d:f8 ) 08:49:18 (GMT)
[ 48 97 49 ]
N 0.0000000 E 0.0000000 ( BC ) BBS ( 00:0f:3d:3a:1d:f8 ) 08:49:19 (GMT)
[ 48 97 49 ]
N 0.0000000 E 0.0000000 ( BC ) BBS ( 00:0f:3d:3a:1d:f8 ) 08:49:20 (GMT)
[ 48 97 49 ]
N 0.0000000 E 0.0000000 ( BC ) BBS ( 00:0f:3d:3a:1d:f8 ) 08:49:21 (GMT)
[ 48 97 49 ]
N 0.0000000 E 0.0000000 ( BC ) BBS ( 00:0f:3d:3a:1d:f8 ) 08:49:22 (GMT)
[ 48 97 49 ]
N 0.0000000 E 0.0000000 ( BC ) BBS ( 00:0f:3d:3a:1d:f8 ) 08:49:23 (GMT)
[ 48 97 49 ]
N 0.0000000 E 0.0000000 ( BC ) BBS ( 00:0f:3d:3a:1d:f8 ) 08:49:24 (GMT)
[ 48 97 49 ]
N 0.0000000 E 0.0000000 ( BC ) BBS ( 00:0f:3d:3a:1d:f8 ) 08:49:25 (GMT)
[ 48 97 49 ]
N 0.0000000 E 0.0000000 ( BC ) BBS ( 00:0f:3d:3a:1d:f8 ) 08:49:26 (GMT)
[ 48 97 49 ]
N 0.0000000 E 0.0000000 ( BC ) BBS ( 00:0f:3d:3a:1d:f8 ) 08:49:27 (GMT)
[ 48 97 49 ]
N 0.0000000 E 0.0000000 ( BC ) BBS ( 00:0f:3d:3a:1d:f8 ) 08:49:28 (GMT)
[ 47 96 49 ]
N 0.0000000 E 0.0000000 ( BC ) BBS ( 00:0f:3d:3a:1d:f8 ) 08:49:29 (GMT)
[ 47 96 49 ]
N 0.0000000 E 0.0000000 ( BC ) BBS ( 00:0f:3d:3a:1d:f8 ) 08:49:31 (GMT)
[ 48 97 49 ]
N 0.0000000 E 0.0000000 ( BC ) BBS ( 00:0f:3d:3a:1d:f8 ) 08:49:32 (GMT)
[ 48 97 49 ]
N 0.0000000 E 0.0000000 ( BC ) BBS ( 00:0f:3d:3a:1d:f8 ) 08:49:33 (GMT)
[ 48 97 49 ]
N 0.0000000 E 0.0000000 ( BC ) BBS ( 00:0f:3d:3a:1d:f8 ) 08:49:34 (GMT)
[ 47 96 49 ]
N 0.0000000 E 0.0000000 ( BC ) BBS ( 00:0f:3d:3a:1d:f8 ) 08:49:35 (GMT)
[ 47 96 49 ]
N 0.0000000 E 0.0000000 ( BC ) BBS ( 00:0f:3d:3a:1d:f8 ) 08:49:36 (GMT)
[ 47 96 49 ]
N 0.0000000 E 0.0000000 ( BC ) BBS ( 00:0f:3d:3a:1d:f8 ) 08:49:37 (GMT)
[ 47 96 49 ]
N 0.0000000 E 0.0000000 ( BC ) BBS ( 00:0f:3d:3a:1d:f8 ) 08:49:38 (GMT)
[ 48 97 49 ]
N 0.0000000 E 0.0000000 ( BC ) BBS ( 00:0f:3d:3a:1d:f8 ) 08:49:39 (GMT)
[ 48 97 49 ]
N 0.0000000 E 0.0000000 ( BC ) BBS ( 00:0f:3d:3a:1d:f8 ) 08:49:40 (GMT)
[ 50 99 49 ]
N 0.0000000 E 0.0000000 ( BC ) BBS ( 00:0f:3d:3a:1d:f8 ) 08:49:41 (GMT)
[ 50 99 49 ]
N 0.0000000 E 0.0000000 ( BC ) BBS ( 00:0f:3d:3a:1d:f8 ) 08:49:42 (GMT)
[ 47 96 49 ]
N 0.0000000 E 0.0000000 ( BC ) BBS ( 00:0f:3d:3a:1d:f8 ) 08:49:43 (GMT)
[ 47 96 49 ]
N 0.0000000 E 0.0000000 ( BC ) BBS ( 00:0f:3d:3a:1d:f8 ) 08:49:44 (GMT)
[ 48 97 49 ]
N 0.0000000 E 0.0000000 ( BC ) BBS ( 00:0f:3d:3a:1d:f8 ) 08:49:45 (GMT)
[ 48 97 49 ]
N 0.0000000 E 0.0000000 ( BC ) BBS ( 00:0f:3d:3a:1d:f8 ) 08:49:46 (GMT)
[ 48 97 49 ]
N 0.0000000 E 0.0000000 ( BC ) BBS ( 00:0f:3d:3a:1d:f8 ) 08:49:47 (GMT)
[ 48 97 49 ]
N 0.0000000 E 0.0000000 ( BC ) BBS ( 00:0f:3d:3a:1d:f8 ) 08:49:48 (GMT)
[ 48 97 49 ]
N 0.0000000 E 0.0000000 ( BC ) BBS ( 00:0f:3d:3a:1d:f8 ) 08:49:49 (GMT)
[ 48 97 49 ]
N 0.0000000 E 0.0000000 ( BC ) BBS ( 00:0f:3d:3a:1d:f8 ) 08:49:50 (GMT)
[ 48 97 49 ]

--

Regards,

Richard Beilby.
 
R

Richard Beilby

It is D-Link DI-624 Router. It has the current firmware in it,
downloaded from the D-Link UK website. I am sorry to say that D-Link
have not been at all helpful and I have difficulties contacting them.
 
G

Guest

It's possible you have a defective device. Or maybe "dirty" power going to
it? Whatever the case, an WAP shouldn't be reseting itself like that. Are
you sure someone isn't hacking into your wireless network?
 
Ad

Advertisements

R

Richard Beilby

There's no indication in the log to suggest hacking. There are the
occasional TCP, UDP and ICMP blocking reported. Most of these seem to
stem from legitimate organisations. The only time that the wireless
network is reasonably stable is when the w98se notebook is powered up
AND connected to the router.
 
G

Guest

Not sure what's going on. Try changing the channel on the WAP. 1, 6, and 11
are best. You could have a faulty client network card that's intefering with
the WAP.
 
R

Richard Beilby

I used to use channel 6 and changed to 3 which is more stable. I will
try 1 and see what happens.
 
R

Richard Beilby

Channel 1 is a lot more stable, but, we are still getting data transfer
problems. Fro instance, if copying a large file approx. 700 Mb, then
disconnection occurs.

Can you explain the event messages in my original posting? The W2K m/c
is still reporting another computer with the same name on the network
(which is NOT the case) and about the master browser being stopped.
 
J

Jay Somerset

Channel 1 is a lot more stable, but, we are still getting data transfer
problems. Fro instance, if copying a large file approx. 700 Mb, then
disconnection occurs.

Can you explain the event messages in my original posting? The W2K m/c
is still reporting another computer with the same name on the network
(which is NOT the case) and about the master browser being stopped.

Your mention of greater stability on some channels vs others suggests that
you may be getting interfering signals on some or all channels.

Most wireless cards support a "site survey" command (my Dlink DWL-624g
certainly does). Use this to see what other wirless access points are in
your vicinity, and chose an unshared channel for yours.

I live in an apartment building, and can see several competing signals, and
noticed that my dropouts disappeared after picking an unused channel. In my
case, Channel 10 seems to work best.
Jay.
 
Ad

Advertisements

G

Guest

Richard Beilby said:
Channel 1 is a lot more stable, but, we are still getting data transfer
problems. Fro instance, if copying a large file approx. 700 Mb, then
disconnection occurs.

You should only be using channels 1, 6, or 11. WAPs allow for more, but any
other channel uses less xmit power and is more susceptible to inteference.
Can you explain the event messages in my original posting? The W2K m/c
is still reporting another computer with the same name on the network
(which is NOT the case) and about the master browser being stopped.

DHCP errors are caused when a computer can't find your DHCP server (server
down or can't be reached.)

The Browser election error happens when the "Master Browser" computer is no
longer available on the network. This is a Windows only network protocol and
happens transparently. One computer on any Windows LAN is always the Master
Browser and can force an election to request another computer to become the
MB.

As for another computer being on the network with the same name, if you're
certain that's not the case, then it's probably the same computer seeing
itself somehow due to the packet losses you're experiencing. Not sure how
that could happen though, but weird things can happen on a lossy network.
Either that or someone else is attaching to your network using a computer
with the same name.
 
R

Richard Beilby

Jay,

I run Network Stumbler frequently and this shows the occasional AP in
operation, but, channel 1 is not being used by anybody else (yet).
 
Ad

Advertisements

R

Richard Beilby

Thanks for your reply. I am using channel 1 and will continue to do so.
Thank you for the explanation of the event log messages. I assume the
DHCP time-out is because the AP/router is not behaving properly.

I am going to continue using channel 1, although I may review the
hardware. The data transfer causing the connection to be lost is
serious. I dare not use the computer for important and critical work.
It's fine for internet browsing and e-mail, but, not for development and
accounts.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top