Synopsis
--------

Very strange networking problem that would seem to be with the
motherboard (process of elimination) but doesn't seem possible as the
type of error that a motherboard *could* cause.

A particular system, connected to an established network, cannot see a
particular device (the router) no matter what adapter, OS, or settings
I use. Whilst I can access every other machine on the LAN I cannot
even ping the router or access the Internet.

Description
-----------

I've built a new system around an Abit IC7 Motherboard (P4 2.4GHz with
Hyperthreading, 2x256MB DDR400 Corsair RAM, 120GB SATA, Radeon
9600Pro, Liteon DVD/CD-RW & Sony DVD-RW). Aside from the DVD rewriter
& motherboard I pulled all of the parts from a working Shuttle SN61G2
(didn't like the noise levels) so I'm pretty confident about most of
these components. [System T]

I've had a home network established (mix of wired ethernet and 802.11b
wireless) for over a year. Broadband enabled router (D-Link DSL504)
wired to a Win 2003 Server [System S], a Win 2000 Advanced Server
Laptop [System L1] and a wireless access point (D-Link DWL-900AP+)
which provides network coverage for two more systems; a Win2k Pro
machine with a D-Link DWL-520 PCI Adapter [System D] and another Win2k
Pro machine with a D-Link DWL-650 PCMCIA Adapter [System L2]. All
machines are configured with static ip addresses.

Due to the location of this new system I knew from previously mapping
out signal coverage that a USB wireless adapter would offer me the
opportunity to achieve about 80-90% signal strength with a relatively
short cable (2 feet). I now get the following problem when using one:

I can ping every machine on the LAN *apart* from the router; I cannot
ping anything outside the LAN (i.e. on the Internet). Signal strength
is fine, I can ftp the other machines and download/upload at a good
rate of knots. When I ping the router I get 'Request Timed Out'.

I have already tried the following:

* Two different usb adapters (a Netgear MA111 & a Linksys WUSB11).

* Two different OS' (WinXP Pro with and without SP1, Win2k Pro with
SP3 and with SP4) and both adapters with each setup. NB: These were
completely fresh installations with just drivers installed, no extra
software.

* Disabling firewalls on every computer in the network and on the
router itself.

* Changing the ip address of the router.

* Changing the ip address I assign to the system (all in the range
192.168.0.x with subnet 255.255.255.0 - same as the other machines).
The DNS server addresses are set to those of my ISP, same as for every
other system.

* Changing the adapter settings to obtain ip address automatically and
enabled DHCP on the router.

* Flashing the motherboard BIOS to most recent version (little
disapointed that my brand new motherboard came with a year out of date
BIOS but thats not the issue).

* Changing BIOS settings to 'Fail Safe Defaults' then disabling
practically everything I didn't need (firewire, serial, USB2, sound).

* Trying the usb adapters on another system (they worked fine).

I'm not a network expert, not really that great with hardware either
but I've always managed to fix my problems before. My instinct is
pushing me towards a motherboard problem through process of
elimination but why? It doesn't make anysort of sense to me that it
could stop my network connection from 'seeing' a specific device
regardless of what ip address I assign to it.

I appologise for cross-posting this to a couple of newsgroups but I
can't narrow down exactly where to look for help. I will, of course,
be posting a full solution in the (increasingly) unlikely event that I
get this solved.

Tintax

Have you set the router as the gateway (in TCP/IP properties), on system T?

-
Tintax stood up, at show-n-tell, and said:

> Synopsis
> --------
>
> Very strange networking problem that would seem to be with the
> motherboard (process of elimination) but doesn't seem possible as the
> type of error that a motherboard *could* cause.
>
> A particular system, connected to an established network, cannot see a
> particular device (the router) no matter what adapter, OS, or settings
> I use. Whilst I can access every other machine on the LAN I cannot
> even ping the router or access the Internet.
>
> Description
> -----------
>
> I've built a new system around an Abit IC7 Motherboard (P4 2.4GHz with
> Hyperthreading, 2x256MB DDR400 Corsair RAM, 120GB SATA, Radeon
> 9600Pro, Liteon DVD/CD-RW & Sony DVD-RW). Aside from the DVD rewriter
> & motherboard I pulled all of the parts from a working Shuttle SN61G2
> (didn't like the noise levels) so I'm pretty confident about most of
> these components. [System T]
>
> I've had a home network established (mix of wired ethernet and 802.11b
> wireless) for over a year. Broadband enabled router (D-Link DSL504)
> wired to a Win 2003 Server [System S], a Win 2000 Advanced Server
> Laptop [System L1] and a wireless access point (D-Link DWL-900AP+)
> which provides network coverage for two more systems; a Win2k Pro
> machine with a D-Link DWL-520 PCI Adapter [System D] and another Win2k
> Pro machine with a D-Link DWL-650 PCMCIA Adapter [System L2]. All
> machines are configured with static ip addresses.
>
> Due to the location of this new system I knew from previously mapping
> out signal coverage that a USB wireless adapter would offer me the
> opportunity to achieve about 80-90% signal strength with a relatively
> short cable (2 feet). I now get the following problem when using one:
>
> I can ping every machine on the LAN *apart* from the router; I cannot
> ping anything outside the LAN (i.e. on the Internet). Signal strength
> is fine, I can ftp the other machines and download/upload at a good
> rate of knots. When I ping the router I get 'Request Timed Out'.
>
> I have already tried the following:
>
> * Two different usb adapters (a Netgear MA111 & a Linksys WUSB11).
>
> * Two different OS' (WinXP Pro with and without SP1, Win2k Pro with
> SP3 and with SP4) and both adapters with each setup. NB: These were
> completely fresh installations with just drivers installed, no extra
> software.
>
> * Disabling firewalls on every computer in the network and on the
> router itself.
>
> * Changing the ip address of the router.
>
> * Changing the ip address I assign to the system (all in the range
> 192.168.0.x with subnet 255.255.255.0 - same as the other machines).
> The DNS server addresses are set to those of my ISP, same as for every
> other system.
>
> * Changing the adapter settings to obtain ip address automatically and
> enabled DHCP on the router.
>
> * Flashing the motherboard BIOS to most recent version (little
> disapointed that my brand new motherboard came with a year out of date
> BIOS but thats not the issue).
>
> * Changing BIOS settings to 'Fail Safe Defaults' then disabling
> practically everything I didn't need (firewire, serial, USB2, sound).
>
> * Trying the usb adapters on another system (they worked fine).
>
> I'm not a network expert, not really that great with hardware either
> but I've always managed to fix my problems before. My instinct is
> pushing me towards a motherboard problem through process of
> elimination but why? It doesn't make anysort of sense to me that it
> could stop my network connection from 'seeing' a specific device
> regardless of what ip address I assign to it.
>
> I appologise for cross-posting this to a couple of newsgroups but I
> can't narrow down exactly where to look for help. I will, of course,
> be posting a full solution in the (increasingly) unlikely event that I
> get this solved.
>
> Tintax

--
Strontium

"It's no surprise, to me. I am my own worst enemy. `Cause every
now, and then, I kick the livin' **** `outta me." - Lit

Tintax <(E-Mail Removed)> wrote:
: Synopsis
: --------
:
: Very strange networking problem that would seem to be with the
: motherboard (process of elimination) but doesn't seem possible as the
: type of error that a motherboard *could* cause.
:
: A particular system, connected to an established network, cannot see a
: particular device (the router) no matter what adapter, OS, or settings
: I use. Whilst I can access every other machine on the LAN I cannot
: even ping the router or access the Internet.
:
: Description
: -----------
:
: I've built a new system around an Abit IC7 Motherboard (P4 2.4GHz with
: Hyperthreading, 2x256MB DDR400 Corsair RAM, 120GB SATA, Radeon
: 9600Pro, Liteon DVD/CD-RW & Sony DVD-RW). Aside from the DVD rewriter
: & motherboard I pulled all of the parts from a working Shuttle SN61G2
: (didn't like the noise levels) so I'm pretty confident about most of
: these components. [System T]
<snip>

Disable HT (hyperthreading), try again, and report back to the NG's.
I've seen HT do a lot of strange things to system setups lately. <sigh>

J.

--
--------
The end to "Personal Computing" as we know it is just around the corner.
TCPA will take away ALL rights from you, the consumer. Learn more
about it here: http://www.againsttcpa.com/what-is-tcpa.html and
here: http://www.againsttcpa.com/tcpa-faq-en.html

I second that. Also check for ip conflicts (i.e. router ip = one of the
machines ip)


"Strontium" <(E-Mail Removed)> wrote in message
news:-_(E-Mail Removed)...
| Have you set the router as the gateway (in TCP/IP properties), on system
T?
|
| -
| Tintax stood up, at show-n-tell, and said:
|
| > Synopsis
| > --------
| >
| > Very strange networking problem that would seem to be with the
| > motherboard (process of elimination) but doesn't seem possible as the
| > type of error that a motherboard *could* cause.
| >
| > A particular system, connected to an established network, cannot see a
| > particular device (the router) no matter what adapter, OS, or settings
| > I use. Whilst I can access every other machine on the LAN I cannot
| > even ping the router or access the Internet.
| >
| > Description
| > -----------
| >
| > I've built a new system around an Abit IC7 Motherboard (P4 2.4GHz with
| > Hyperthreading, 2x256MB DDR400 Corsair RAM, 120GB SATA, Radeon
| > 9600Pro, Liteon DVD/CD-RW & Sony DVD-RW). Aside from the DVD rewriter
| > & motherboard I pulled all of the parts from a working Shuttle SN61G2
| > (didn't like the noise levels) so I'm pretty confident about most of
| > these components. [System T]
| >
| > I've had a home network established (mix of wired ethernet and 802.11b
| > wireless) for over a year. Broadband enabled router (D-Link DSL504)
| > wired to a Win 2003 Server [System S], a Win 2000 Advanced Server
| > Laptop [System L1] and a wireless access point (D-Link DWL-900AP+)
| > which provides network coverage for two more systems; a Win2k Pro
| > machine with a D-Link DWL-520 PCI Adapter [System D] and another Win2k
| > Pro machine with a D-Link DWL-650 PCMCIA Adapter [System L2]. All
| > machines are configured with static ip addresses.
| >
| > Due to the location of this new system I knew from previously mapping
| > out signal coverage that a USB wireless adapter would offer me the
| > opportunity to achieve about 80-90% signal strength with a relatively
| > short cable (2 feet). I now get the following problem when using one:
| >
| > I can ping every machine on the LAN *apart* from the router; I cannot
| > ping anything outside the LAN (i.e. on the Internet). Signal strength
| > is fine, I can ftp the other machines and download/upload at a good
| > rate of knots. When I ping the router I get 'Request Timed Out'.
| >
| > I have already tried the following:
| >
| > * Two different usb adapters (a Netgear MA111 & a Linksys WUSB11).
| >
| > * Two different OS' (WinXP Pro with and without SP1, Win2k Pro with
| > SP3 and with SP4) and both adapters with each setup. NB: These were
| > completely fresh installations with just drivers installed, no extra
| > software.
| >
| > * Disabling firewalls on every computer in the network and on the
| > router itself.
| >
| > * Changing the ip address of the router.
| >
| > * Changing the ip address I assign to the system (all in the range
| > 192.168.0.x with subnet 255.255.255.0 - same as the other machines).
| > The DNS server addresses are set to those of my ISP, same as for every
| > other system.
| >
| > * Changing the adapter settings to obtain ip address automatically and
| > enabled DHCP on the router.
| >
| > * Flashing the motherboard BIOS to most recent version (little
| > disapointed that my brand new motherboard came with a year out of date
| > BIOS but thats not the issue).
| >
| > * Changing BIOS settings to 'Fail Safe Defaults' then disabling
| > practically everything I didn't need (firewire, serial, USB2, sound).
| >
| > * Trying the usb adapters on another system (they worked fine).
| >
| > I'm not a network expert, not really that great with hardware either
| > but I've always managed to fix my problems before. My instinct is
| > pushing me towards a motherboard problem through process of
| > elimination but why? It doesn't make anysort of sense to me that it
| > could stop my network connection from 'seeing' a specific device
| > regardless of what ip address I assign to it.
| >
| > I appologise for cross-posting this to a couple of newsgroups but I
| > can't narrow down exactly where to look for help. I will, of course,
| > be posting a full solution in the (increasingly) unlikely event that I
| > get this solved.
| >
| > Tintax
|
| --
| Strontium
|
| "It's no surprise, to me. I am my own worst enemy. `Cause every
| now, and then, I kick the livin' **** `outta me." - Lit
|
|

On 22 Aug 2003 01:18:54 -0700, (E-Mail Removed) (Tintax) wrote:

>Synopsis
>--------
>
>Very strange networking problem that would seem to be with the
>motherboard (process of elimination) but doesn't seem possible as the
>type of error that a motherboard *could* cause.
>
>A particular system, connected to an established network, cannot see a
>particular device (the router) no matter what adapter, OS, or settings
>I use. Whilst I can access every other machine on the LAN I cannot
>even ping the router or access the Internet.
>
>Description
>-----------
>
>I've built a new system around an Abit IC7 Motherboard (P4 2.4GHz with
>Hyperthreading, 2x256MB DDR400 Corsair RAM, 120GB SATA, Radeon
>9600Pro, Liteon DVD/CD-RW & Sony DVD-RW). Aside from the DVD rewriter
>& motherboard I pulled all of the parts from a working Shuttle SN61G2
>(didn't like the noise levels) so I'm pretty confident about most of
>these components. [System T]
>
>I've had a home network established (mix of wired ethernet and 802.11b
>wireless) for over a year. Broadband enabled router (D-Link DSL504)
>wired to a Win 2003 Server [System S], a Win 2000 Advanced Server
>Laptop [System L1] and a wireless access point (D-Link DWL-900AP+)
>which provides network coverage for two more systems; a Win2k Pro
>machine with a D-Link DWL-520 PCI Adapter [System D] and another Win2k
>Pro machine with a D-Link DWL-650 PCMCIA Adapter [System L2]. All
>machines are configured with static ip addresses.
>
>Due to the location of this new system I knew from previously mapping
>out signal coverage that a USB wireless adapter would offer me the
>opportunity to achieve about 80-90% signal strength with a relatively
>short cable (2 feet). I now get the following problem when using one:
>
>I can ping every machine on the LAN *apart* from the router; I cannot
>ping anything outside the LAN (i.e. on the Internet). Signal strength
>is fine, I can ftp the other machines and download/upload at a good
>rate of knots. When I ping the router I get 'Request Timed Out'.
>
>I have already tried the following:
>
>* Two different usb adapters (a Netgear MA111 & a Linksys WUSB11).
>
>* Two different OS' (WinXP Pro with and without SP1, Win2k Pro with
>SP3 and with SP4) and both adapters with each setup. NB: These were
>completely fresh installations with just drivers installed, no extra
>software.
>
>* Disabling firewalls on every computer in the network and on the
>router itself.
>
>* Changing the ip address of the router.
>
>* Changing the ip address I assign to the system (all in the range
>192.168.0.x with subnet 255.255.255.0 - same as the other machines).
>The DNS server addresses are set to those of my ISP, same as for every
>other system.
>
>* Changing the adapter settings to obtain ip address automatically and
>enabled DHCP on the router.
>
>* Flashing the motherboard BIOS to most recent version (little
>disapointed that my brand new motherboard came with a year out of date
>BIOS but thats not the issue).
>
>* Changing BIOS settings to 'Fail Safe Defaults' then disabling
>practically everything I didn't need (firewire, serial, USB2, sound).
>
>* Trying the usb adapters on another system (they worked fine).
>
>I'm not a network expert, not really that great with hardware either
>but I've always managed to fix my problems before. My instinct is
>pushing me towards a motherboard problem through process of
>elimination but why? It doesn't make anysort of sense to me that it
>could stop my network connection from 'seeing' a specific device
>regardless of what ip address I assign to it.
>
>I appologise for cross-posting this to a couple of newsgroups but I
>can't narrow down exactly where to look for help. I will, of course,
>be posting a full solution in the (increasingly) unlikely event that I
>get this solved.
>
>Tintax

Check to see if you have any other network interfaces in the computer
(probably built into the motherboard, possibly firewire). If so, make
sure they don't have an IP address assigned that conflicts with your
router. If you have unused network interfaces, probably best to
disable them in device manager.

mac address assignment? In some cases the MAC address has to be from the
original machine setup.

"Tintax" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Synopsis
> --------
>
> Very strange networking problem that would seem to be with the
> motherboard (process of elimination) but doesn't seem possible as the
> type of error that a motherboard *could* cause.
>
> A particular system, connected to an established network, cannot see a
> particular device (the router) no matter what adapter, OS, or settings
> I use. Whilst I can access every other machine on the LAN I cannot
> even ping the router or access the Internet.
>
> Description
> -----------
>
> I've built a new system around an Abit IC7 Motherboard (P4 2.4GHz with
> Hyperthreading, 2x256MB DDR400 Corsair RAM, 120GB SATA, Radeon
> 9600Pro, Liteon DVD/CD-RW & Sony DVD-RW). Aside from the DVD rewriter
> & motherboard I pulled all of the parts from a working Shuttle SN61G2
> (didn't like the noise levels) so I'm pretty confident about most of
> these components. [System T]
>
> I've had a home network established (mix of wired ethernet and 802.11b
> wireless) for over a year. Broadband enabled router (D-Link DSL504)
> wired to a Win 2003 Server [System S], a Win 2000 Advanced Server
> Laptop [System L1] and a wireless access point (D-Link DWL-900AP+)
> which provides network coverage for two more systems; a Win2k Pro
> machine with a D-Link DWL-520 PCI Adapter [System D] and another Win2k
> Pro machine with a D-Link DWL-650 PCMCIA Adapter [System L2]. All
> machines are configured with static ip addresses.
>
> Due to the location of this new system I knew from previously mapping
> out signal coverage that a USB wireless adapter would offer me the
> opportunity to achieve about 80-90% signal strength with a relatively
> short cable (2 feet). I now get the following problem when using one:
>
> I can ping every machine on the LAN *apart* from the router; I cannot
> ping anything outside the LAN (i.e. on the Internet). Signal strength
> is fine, I can ftp the other machines and download/upload at a good
> rate of knots. When I ping the router I get 'Request Timed Out'.
>
> I have already tried the following:
>
> * Two different usb adapters (a Netgear MA111 & a Linksys WUSB11).
>
> * Two different OS' (WinXP Pro with and without SP1, Win2k Pro with
> SP3 and with SP4) and both adapters with each setup. NB: These were
> completely fresh installations with just drivers installed, no extra
> software.
>
> * Disabling firewalls on every computer in the network and on the
> router itself.
>
> * Changing the ip address of the router.
>
> * Changing the ip address I assign to the system (all in the range
> 192.168.0.x with subnet 255.255.255.0 - same as the other machines).
> The DNS server addresses are set to those of my ISP, same as for every
> other system.
>
> * Changing the adapter settings to obtain ip address automatically and
> enabled DHCP on the router.
>
> * Flashing the motherboard BIOS to most recent version (little
> disapointed that my brand new motherboard came with a year out of date
> BIOS but thats not the issue).
>
> * Changing BIOS settings to 'Fail Safe Defaults' then disabling
> practically everything I didn't need (firewire, serial, USB2, sound).
>
> * Trying the usb adapters on another system (they worked fine).
>
> I'm not a network expert, not really that great with hardware either
> but I've always managed to fix my problems before. My instinct is
> pushing me towards a motherboard problem through process of
> elimination but why? It doesn't make anysort of sense to me that it
> could stop my network connection from 'seeing' a specific device
> regardless of what ip address I assign to it.
>
> I appologise for cross-posting this to a couple of newsgroups but I
> can't narrow down exactly where to look for help. I will, of course,
> be posting a full solution in the (increasingly) unlikely event that I
> get this solved.
>
> Tintax

"jack" <(E-Mail Removed)> wrote in message news:<bi4qg1$5121b$1@ID->
> Disable HT (hyperthreading), try again, and report back to the NG's.
> I've seen HT do a lot of strange things to system setups lately. <sigh>
>
> J.

Didn't think of a possible HT threading issue but alas no the problem
remains.

In answer to the other posts the router is set as gateway for System T
(and the others) and no ip address clashes with another one.

Tintax

If that were the case, none of the other systems would have a connection to
internet, either.

-
JAD stood up at show-n-tell, in
pVr1b.447$(E-Mail Removed), and said:

> mac address assignment? In some cases the MAC address has to be from
> the original machine setup.
>
> "Tintax" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
>> Synopsis
>> --------
>>
>> Very strange networking problem that would seem to be with the
>> motherboard (process of elimination) but doesn't seem possible as the
>> type of error that a motherboard *could* cause.
>>
>> A particular system, connected to an established network, cannot see
>> a particular device (the router) no matter what adapter, OS, or
>> settings I use. Whilst I can access every other machine on the LAN I
>> cannot even ping the router or access the Internet.
>>
<snip>

--
Strontium

"It's no surprise, to me. I am my own worst enemy. `Cause every
now, and then, I kick the livin' **** `outta me." - Lit

Whilst I can access every other machine on the LAN I
>> cannot even ping the router or access the Internet.


where did he say any other machines were connecting?

"Strontium" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> If that were the case, none of the other systems would have a connection
to
> internet, either.
>
> -
> JAD stood up at show-n-tell, in
> pVr1b.447$(E-Mail Removed), and said:
>
> > mac address assignment? In some cases the MAC address has to be from
> > the original machine setup.
> >
> > "Tintax" <(E-Mail Removed)> wrote in message
> > news:(E-Mail Removed)...
> >> Synopsis
> >> --------
> >>
> >> Very strange networking problem that would seem to be with the
> >> motherboard (process of elimination) but doesn't seem possible as the
> >> type of error that a motherboard *could* cause.
> >>
> >> A particular system, connected to an established network, cannot see
> >> a particular device (the router) no matter what adapter, OS, or
> >> settings I use. Whilst I can access every other machine on the LAN I
> >> cannot even ping the router or access the Internet.
> >>
> <snip>
>
> --
> Strontium
>
> "It's no surprise, to me. I am my own worst enemy. `Cause every
> now, and then, I kick the livin' **** `outta me." - Lit
>
>

>
> I'm not a network expert, not really that great with hardware either
> but I've always managed to fix my problems before. My instinct is
> pushing me towards a motherboard problem through process of
> elimination but why? It doesn't make anysort of sense to me that it
> could stop my network connection from 'seeing' a specific device
> regardless of what ip address I assign to it.

Have you tried shutting down all the systems except the offending one and
then using that system only resetting and reconfiguring the router, etc.?