ethernet problems in Windows Vista with wireless connection

I have an HP laptop running Windows Vista Home Premium. It connects to the
internet through a wireless router (NetGear) that is connected to a DSL
modem. My internet connection is fine.

When I try to connect a hardware device to the ethernet port on the laptop,
Vista doesn't see it. Using the command line prompt, I "ping" the address of
the device and get "general failure" four times.

I went through the procedure of manage network
connections>properties>unclick ipv6 but no help.

The device has it's own hardwired IP address. I know it is working because
I hooked it up to a desktop machine running XP and had no problems. The
desktop is also connected to the internet through the same router (but with
an ethernet cable, as the desktop does not have wireless).

Here are the results of ipconfig /all:
Microsoft Windows [Version 6.0.6000]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.

C:\Users\Daddy>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : Vulcan
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Wireless LAN adapter Wireless Network Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Broadcom 802.11b/g WLAN
Physical Address. . . . . . . . . : 00-1A-73-50-72-3A
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 192.168.1.5(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Sunday, December 02, 2007 10:56:33 AM
Lease Expires . . . . . . . . . . : Monday, December 03, 2007 10:56:34 AM
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 192.168.1.1
NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : NVIDIA nForce Networking Controller
Physical Address. . . . . . . . . : 00-1B-24-30-E2-AB
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 191.30.10.199(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . : 191.30.0.1
NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter Local Area Connection* 6:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : 6TO4 Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Temporary IPv6 Address. . . . . . : 2002:bf1e:ac7::bf1e:ac7(Preferred)
Default Gateway . . . . . . . . . : 2002:c058:6301::c058:6301
NetBIOS over Tcpip. . . . . . . . : Disabled

Tunnel adapter Local Area Connection* 7:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . :
isatap.{313DDD98-589B-42A1-BBFF-F71310302
713}
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::5efe:192.168.1.5%15(Preferred)
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . : 192.168.1.1
NetBIOS over Tcpip. . . . . . . . : Disabled

Tunnel adapter Local Area Connection* 9:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 02-00-54-55-4E-01
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 14:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . :
isatap.{90B417F8-A0C1-4A5C-B6FF-A35FD7E1A
224}
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . :
fe80::200:5efe:191.30.10.199%16(Preferred
)
Default Gateway . . . . . . . . . :
NetBIOS over Tcpip. . . . . . . . : Disabled

C:\Users\Daddy>

Any suggestions?
--
leave well enough alone

raymondvillain wrote:
> I have an HP laptop running Windows Vista Home Premium. It connects to the
> internet through a wireless router (NetGear) that is connected to a DSL
> modem. My internet connection is fine.
>
> When I try to connect a hardware device to the ethernet port on the laptop,
> Vista doesn't see it. Using the command line prompt, I "ping" the address of
> the device and get "general failure" four times.
>
> I went through the procedure of manage network
> connections>properties>unclick ipv6 but no help.
>
> The device has it's own hardwired IP address. I know it is working because
> I hooked it up to a desktop machine running XP and had no problems. The
> desktop is also connected to the internet through the same router (but with
> an ethernet cable, as the desktop does not have wireless).

(snippage)

You forgot to tell us what the device is.


Malke
--
Elephant Boy Computers
www.elephantboycomputers.com
"Don't Panic!"
MS-MVP Windows - Shell/User

The device is a ScaniValve DSA 3218 pressure sensing module. We hook up
tubes to it. The other ends of the tubes are in a duct with moving air, or
other gases. The tubes conduct pressure back to the device. The pressures
are measured and converted to binary numbers. The ethernet connection allows
us to record 16 pressures simultaneously to a file, database, software
program, etc. All this is used in an engineering laboratory. We have used
it for over 3 years on Windows XP machines with no problems.
--
leave well enough alone


"Malke" wrote:

> raymondvillain wrote:
> > I have an HP laptop running Windows Vista Home Premium. It connects to the
> > internet through a wireless router (NetGear) that is connected to a DSL
> > modem. My internet connection is fine.
> >
> > When I try to connect a hardware device to the ethernet port on the laptop,
> > Vista doesn't see it. Using the command line prompt, I "ping" the address of
> > the device and get "general failure" four times.
> >
> > I went through the procedure of manage network
> > connections>properties>unclick ipv6 but no help.
> >
> > The device has it's own hardwired IP address. I know it is working because
> > I hooked it up to a desktop machine running XP and had no problems. The
> > desktop is also connected to the internet through the same router (but with
> > an ethernet cable, as the desktop does not have wireless).
>
> (snippage)
>
> You forgot to tell us what the device is.
>
>
> Malke
> --
> Elephant Boy Computers
> www.elephantboycomputers.com
> "Don't Panic!"
> MS-MVP Windows - Shell/User
>

raymondvillain wrote:
> The device is a ScaniValve DSA 3218 pressure sensing module. We hook up
> tubes to it. The other ends of the tubes are in a duct with moving air, or
> other gases. The tubes conduct pressure back to the device. The pressures
> are measured and converted to binary numbers. The ethernet connection allows
> us to record 16 pressures simultaneously to a file, database, software
> program, etc. All this is used in an engineering laboratory. We have used
> it for over 3 years on Windows XP machines with no problems.

It sounds as though it is not compatible with Vista. For such a
specialized piece of equipment, you need to contact the equipment
mftr.'s tech support for help. The fact that you have used it
successfully with XP is irrelevant; Vista is a different operating
system. If the ScaniValve people will not support their hardware on
Vista, you will be in the same boat as many other businesses and will
need to run your specialized equipment/software on XP.


Malke
--
Elephant Boy Computers
www.elephantboycomputers.com
"Don't Panic!"
MS-MVP Windows - Shell/User

I have a similar setup, hp laptop with vista, and the netgear router and a
dsl modem, I also had problems with connections when I got this POS, I called
my isp and they got everything straightened out for me over the phone

"raymondvillain" wrote:

> I have an HP laptop running Windows Vista Home Premium. It connects to the
> internet through a wireless router (NetGear) that is connected to a DSL
> modem. My internet connection is fine.
>
> When I try to connect a hardware device to the ethernet port on the laptop,
> Vista doesn't see it. Using the command line prompt, I "ping" the address of
> the device and get "general failure" four times.
>
> I went through the procedure of manage network
> connections>properties>unclick ipv6 but no help.
>
> The device has it's own hardwired IP address. I know it is working because
> I hooked it up to a desktop machine running XP and had no problems. The
> desktop is also connected to the internet through the same router (but with
> an ethernet cable, as the desktop does not have wireless).
>
> Here are the results of ipconfig /all:
> Microsoft Windows [Version 6.0.6000]
> Copyright (c) 2006 Microsoft Corporation. All rights reserved.
>
> C:\Users\Daddy>ipconfig /all
>
> Windows IP Configuration
>
> Host Name . . . . . . . . . . . . : Vulcan
> Primary Dns Suffix . . . . . . . :
> Node Type . . . . . . . . . . . . : Hybrid
> IP Routing Enabled. . . . . . . . : No
> WINS Proxy Enabled. . . . . . . . : No
>
> Wireless LAN adapter Wireless Network Connection:
>
> Connection-specific DNS Suffix . :
> Description . . . . . . . . . . . : Broadcom 802.11b/g WLAN
> Physical Address. . . . . . . . . : 00-1A-73-50-72-3A
> DHCP Enabled. . . . . . . . . . . : Yes
> Autoconfiguration Enabled . . . . : Yes
> IPv4 Address. . . . . . . . . . . : 192.168.1.5(Preferred)
> Subnet Mask . . . . . . . . . . . : 255.255.255.0
> Lease Obtained. . . . . . . . . . : Sunday, December 02, 2007 10:56:33 AM
> Lease Expires . . . . . . . . . . : Monday, December 03, 2007 10:56:34 AM
> Default Gateway . . . . . . . . . : 192.168.1.1
> DHCP Server . . . . . . . . . . . : 192.168.1.1
> DNS Servers . . . . . . . . . . . : 192.168.1.1
> NetBIOS over Tcpip. . . . . . . . : Enabled
>
> Ethernet adapter Local Area Connection:
>
> Connection-specific DNS Suffix . :
> Description . . . . . . . . . . . : NVIDIA nForce Networking Controller
> Physical Address. . . . . . . . . : 00-1B-24-30-E2-AB
> DHCP Enabled. . . . . . . . . . . : No
> Autoconfiguration Enabled . . . . : Yes
> IPv4 Address. . . . . . . . . . . : 191.30.10.199(Preferred)
> Subnet Mask . . . . . . . . . . . : 255.255.0.0
> Default Gateway . . . . . . . . . : 191.30.0.1
> NetBIOS over Tcpip. . . . . . . . : Enabled
>
> Tunnel adapter Local Area Connection* 6:
>
> Connection-specific DNS Suffix . :
> Description . . . . . . . . . . . : 6TO4 Adapter
> Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
> DHCP Enabled. . . . . . . . . . . : No
> Autoconfiguration Enabled . . . . : Yes
> Temporary IPv6 Address. . . . . . : 2002:bf1e:ac7::bf1e:ac7(Preferred)
> Default Gateway . . . . . . . . . : 2002:c058:6301::c058:6301
> NetBIOS over Tcpip. . . . . . . . : Disabled
>
> Tunnel adapter Local Area Connection* 7:
>
> Connection-specific DNS Suffix . :
> Description . . . . . . . . . . . :
> isatap.{313DDD98-589B-42A1-BBFF-F71310302
> 713}
> Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
> DHCP Enabled. . . . . . . . . . . : No
> Autoconfiguration Enabled . . . . : Yes
> Link-local IPv6 Address . . . . . : fe80::5efe:192.168.1.5%15(Preferred)
> Default Gateway . . . . . . . . . :
> DNS Servers . . . . . . . . . . . : 192.168.1.1
> NetBIOS over Tcpip. . . . . . . . : Disabled
>
> Tunnel adapter Local Area Connection* 9:
>
> Media State . . . . . . . . . . . : Media disconnected
> Connection-specific DNS Suffix . :
> Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
> Physical Address. . . . . . . . . : 02-00-54-55-4E-01
> DHCP Enabled. . . . . . . . . . . : No
> Autoconfiguration Enabled . . . . : Yes
>
> Tunnel adapter Local Area Connection* 14:
>
> Connection-specific DNS Suffix . :
> Description . . . . . . . . . . . :
> isatap.{90B417F8-A0C1-4A5C-B6FF-A35FD7E1A
> 224}
> Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
> DHCP Enabled. . . . . . . . . . . : No
> Autoconfiguration Enabled . . . . : Yes
> Link-local IPv6 Address . . . . . :
> fe80::200:5efe:191.30.10.199%16(Preferred
> )
> Default Gateway . . . . . . . . . :
> NetBIOS over Tcpip. . . . . . . . : Disabled
>
> C:\Users\Daddy>
>
> Any suggestions?
> --
> leave well enough alone

Thanks for the warning. Just for my general edification, is "ethernet" not
then a stand-alone specification but something that is tailored to the O. S.?
I have been thinking that "ethernet" was completely separate from the O. S.
--
leave well enough alone


"Malke" wrote:

> raymondvillain wrote:
> > The device is a ScaniValve DSA 3218 pressure sensing module. We hook up
> > tubes to it. The other ends of the tubes are in a duct with moving air, or
> > other gases. The tubes conduct pressure back to the device. The pressures
> > are measured and converted to binary numbers. The ethernet connection allows
> > us to record 16 pressures simultaneously to a file, database, software
> > program, etc. All this is used in an engineering laboratory. We have used
> > it for over 3 years on Windows XP machines with no problems.
>
> It sounds as though it is not compatible with Vista. For such a
> specialized piece of equipment, you need to contact the equipment
> mftr.'s tech support for help. The fact that you have used it
> successfully with XP is irrelevant; Vista is a different operating
> system. If the ScaniValve people will not support their hardware on
> Vista, you will be in the same boat as many other businesses and will
> need to run your specialized equipment/software on XP.
>
>
> Malke
> --
> Elephant Boy Computers
> www.elephantboycomputers.com
> "Don't Panic!"
> MS-MVP Windows - Shell/User
>

Your problem sounds like it is in the software program, not the Ethernet
connection; ethernet is "stateless".
Follow Malke's advice, but you could also try(and I mean try!) installing
the software in XP SP2 Mode.
On its setup.exe>right-click>properties>compatibility> and install in XP SP2.

"raymondvillain" wrote:

> Thanks for the warning. Just for my general edification, is "ethernet" not
> then a stand-alone specification but something that is tailored to the O. S.?
> I have been thinking that "ethernet" was completely separate from the O. S.
> --
> leave well enough alone
>
>
> "Malke" wrote:
>
> > raymondvillain wrote:
> > > The device is a ScaniValve DSA 3218 pressure sensing module. We hook up
> > > tubes to it. The other ends of the tubes are in a duct with moving air, or
> > > other gases. The tubes conduct pressure back to the device. The pressures
> > > are measured and converted to binary numbers. The ethernet connection allows
> > > us to record 16 pressures simultaneously to a file, database, software
> > > program, etc. All this is used in an engineering laboratory. We have used
> > > it for over 3 years on Windows XP machines with no problems.
> >
> > It sounds as though it is not compatible with Vista. For such a
> > specialized piece of equipment, you need to contact the equipment
> > mftr.'s tech support for help. The fact that you have used it
> > successfully with XP is irrelevant; Vista is a different operating
> > system. If the ScaniValve people will not support their hardware on
> > Vista, you will be in the same boat as many other businesses and will
> > need to run your specialized equipment/software on XP.
> >
> >
> > Malke
> > --
> > Elephant Boy Computers
> > www.elephantboycomputers.com
> > "Don't Panic!"
> > MS-MVP Windows - Shell/User
> >

"raymondvillain" <> wrote in message
news:315E4B97-67F3-44B1-B74D-...
>I have an HP laptop running Windows Vista Home Premium. It connects to the
> internet through a wireless router (NetGear) that is connected to a DSL
> modem. My internet connection is fine.
>
> When I try to connect a hardware device to the ethernet port on the
> laptop,
> Vista doesn't see it. Using the command line prompt, I "ping" the address
> of
> the device and get "general failure" four times.
>
> I went through the procedure of manage network
> connections>properties>unclick ipv6 but no help.
>
> The device has it's own hardwired IP address. I know it is working
> because
> I hooked it up to a desktop machine running XP and had no problems. The
> desktop is also connected to the internet through the same router (but
> with
> an ethernet cable, as the desktop does not have wireless).
>
> Here are the results of ipconfig /all:
> Microsoft Windows [Version 6.0.6000]
> Copyright (c) 2006 Microsoft Corporation. All rights reserved.
>
> C:\Users\Daddy>ipconfig /all
>
> Windows IP Configuration
>
> Host Name . . . . . . . . . . . . : Vulcan
> Primary Dns Suffix . . . . . . . :
> Node Type . . . . . . . . . . . . : Hybrid
> IP Routing Enabled. . . . . . . . : No
> WINS Proxy Enabled. . . . . . . . : No
>
> Wireless LAN adapter Wireless Network Connection:
>
> Connection-specific DNS Suffix . :
> Description . . . . . . . . . . . : Broadcom 802.11b/g WLAN
> Physical Address. . . . . . . . . : 00-1A-73-50-72-3A
> DHCP Enabled. . . . . . . . . . . : Yes
> Autoconfiguration Enabled . . . . : Yes
> IPv4 Address. . . . . . . . . . . : 192.168.1.5(Preferred)
> Subnet Mask . . . . . . . . . . . : 255.255.255.0
> Lease Obtained. . . . . . . . . . : Sunday, December 02, 2007 10:56:33
> AM
> Lease Expires . . . . . . . . . . : Monday, December 03, 2007 10:56:34
> AM
> Default Gateway . . . . . . . . . : 192.168.1.1
> DHCP Server . . . . . . . . . . . : 192.168.1.1
> DNS Servers . . . . . . . . . . . : 192.168.1.1
> NetBIOS over Tcpip. . . . . . . . : Enabled
>
> Ethernet adapter Local Area Connection:
>
> Connection-specific DNS Suffix . :
> Description . . . . . . . . . . . : NVIDIA nForce Networking Controller
> Physical Address. . . . . . . . . : 00-1B-24-30-E2-AB
> DHCP Enabled. . . . . . . . . . . : No
> Autoconfiguration Enabled . . . . : Yes
> IPv4 Address. . . . . . . . . . . : 191.30.10.199(Preferred)
> Subnet Mask . . . . . . . . . . . : 255.255.0.0
> Default Gateway . . . . . . . . . : 191.30.0.1
> NetBIOS over Tcpip. . . . . . . . : Enabled
>
> Tunnel adapter Local Area Connection* 6:
>
> Connection-specific DNS Suffix . :
> Description . . . . . . . . . . . : 6TO4 Adapter
> Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
> DHCP Enabled. . . . . . . . . . . : No
> Autoconfiguration Enabled . . . . : Yes
> Temporary IPv6 Address. . . . . . : 2002:bf1e:ac7::bf1e:ac7(Preferred)
> Default Gateway . . . . . . . . . : 2002:c058:6301::c058:6301
> NetBIOS over Tcpip. . . . . . . . : Disabled
>
> Tunnel adapter Local Area Connection* 7:
>
> Connection-specific DNS Suffix . :
> Description . . . . . . . . . . . :
> isatap.{313DDD98-589B-42A1-BBFF-F71310302
> 713}
> Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
> DHCP Enabled. . . . . . . . . . . : No
> Autoconfiguration Enabled . . . . : Yes
> Link-local IPv6 Address . . . . . : fe80::5efe:192.168.1.5%15(Preferred)
> Default Gateway . . . . . . . . . :
> DNS Servers . . . . . . . . . . . : 192.168.1.1
> NetBIOS over Tcpip. . . . . . . . : Disabled
>
> Tunnel adapter Local Area Connection* 9:
>
> Media State . . . . . . . . . . . : Media disconnected
> Connection-specific DNS Suffix . :
> Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
> Physical Address. . . . . . . . . : 02-00-54-55-4E-01
> DHCP Enabled. . . . . . . . . . . : No
> Autoconfiguration Enabled . . . . : Yes
>
> Tunnel adapter Local Area Connection* 14:
>
> Connection-specific DNS Suffix . :
> Description . . . . . . . . . . . :
> isatap.{90B417F8-A0C1-4A5C-B6FF-A35FD7E1A
> 224}
> Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
> DHCP Enabled. . . . . . . . . . . : No
> Autoconfiguration Enabled . . . . : Yes
> Link-local IPv6 Address . . . . . :
> fe80::200:5efe:191.30.10.199%16(Preferred
> )
> Default Gateway . . . . . . . . . :
> NetBIOS over Tcpip. . . . . . . . : Disabled
>
> C:\Users\Daddy>
>
> Any suggestions?
> --
> leave well enough alone


What is the IP address of the device you are trying to ping?
A general error usually means your machine can not find a route to the
device.

The address of the device I want to reach is 191.30.10.210.

Originally my vista machine was set to automatically obtain an IP address.
I changed that. Went through network>properties>IPv4>properties>set IP
address and subnet mask, etc. so that now the IP address is 191.30.10.199.
Still won't work.

If I have to I'll use an XP machine. But it would sure be convenient if I
could use the vista notebook.

I'm baffled. I thought ethernet was "stateless" and that there shouldn't be
any problem just because I'm using a PC that operates on vista. Any
suggestions would be greatly appreciated.
--
leave well enough alone


"Vista User" wrote:

> "raymondvillain" <> wrote in message
> news:315E4B97-67F3-44B1-B74D-...
> >I have an HP laptop running Windows Vista Home Premium. It connects to the
> > internet through a wireless router (NetGear) that is connected to a DSL
> > modem. My internet connection is fine.
> >
> > When I try to connect a hardware device to the ethernet port on the
> > laptop,
> > Vista doesn't see it. Using the command line prompt, I "ping" the address
> > of
> > the device and get "general failure" four times.
> >
> > I went through the procedure of manage network
> > connections>properties>unclick ipv6 but no help.
> >
> > The device has it's own hardwired IP address. I know it is working
> > because
> > I hooked it up to a desktop machine running XP and had no problems. The
> > desktop is also connected to the internet through the same router (but
> > with
> > an ethernet cable, as the desktop does not have wireless).
> >
> > Here are the results of ipconfig /all:
> > Microsoft Windows [Version 6.0.6000]
> > Copyright (c) 2006 Microsoft Corporation. All rights reserved.
> >
> > C:\Users\Daddy>ipconfig /all
> >
> > Windows IP Configuration
> >
> > Host Name . . . . . . . . . . . . : Vulcan
> > Primary Dns Suffix . . . . . . . :
> > Node Type . . . . . . . . . . . . : Hybrid
> > IP Routing Enabled. . . . . . . . : No
> > WINS Proxy Enabled. . . . . . . . : No
> >
> > Wireless LAN adapter Wireless Network Connection:
> >
> > Connection-specific DNS Suffix . :
> > Description . . . . . . . . . . . : Broadcom 802.11b/g WLAN
> > Physical Address. . . . . . . . . : 00-1A-73-50-72-3A
> > DHCP Enabled. . . . . . . . . . . : Yes
> > Autoconfiguration Enabled . . . . : Yes
> > IPv4 Address. . . . . . . . . . . : 192.168.1.5(Preferred)
> > Subnet Mask . . . . . . . . . . . : 255.255.255.0
> > Lease Obtained. . . . . . . . . . : Sunday, December 02, 2007 10:56:33
> > AM
> > Lease Expires . . . . . . . . . . : Monday, December 03, 2007 10:56:34
> > AM
> > Default Gateway . . . . . . . . . : 192.168.1.1
> > DHCP Server . . . . . . . . . . . : 192.168.1.1
> > DNS Servers . . . . . . . . . . . : 192.168.1.1
> > NetBIOS over Tcpip. . . . . . . . : Enabled
> >
> > Ethernet adapter Local Area Connection:
> >
> > Connection-specific DNS Suffix . :
> > Description . . . . . . . . . . . : NVIDIA nForce Networking Controller
> > Physical Address. . . . . . . . . : 00-1B-24-30-E2-AB
> > DHCP Enabled. . . . . . . . . . . : No
> > Autoconfiguration Enabled . . . . : Yes
> > IPv4 Address. . . . . . . . . . . : 191.30.10.199(Preferred)
> > Subnet Mask . . . . . . . . . . . : 255.255.0.0
> > Default Gateway . . . . . . . . . : 191.30.0.1
> > NetBIOS over Tcpip. . . . . . . . : Enabled
> >
> > Tunnel adapter Local Area Connection* 6:
> >
> > Connection-specific DNS Suffix . :
> > Description . . . . . . . . . . . : 6TO4 Adapter
> > Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
> > DHCP Enabled. . . . . . . . . . . : No
> > Autoconfiguration Enabled . . . . : Yes
> > Temporary IPv6 Address. . . . . . : 2002:bf1e:ac7::bf1e:ac7(Preferred)
> > Default Gateway . . . . . . . . . : 2002:c058:6301::c058:6301
> > NetBIOS over Tcpip. . . . . . . . : Disabled
> >
> > Tunnel adapter Local Area Connection* 7:
> >
> > Connection-specific DNS Suffix . :
> > Description . . . . . . . . . . . :
> > isatap.{313DDD98-589B-42A1-BBFF-F71310302
> > 713}
> > Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
> > DHCP Enabled. . . . . . . . . . . : No
> > Autoconfiguration Enabled . . . . : Yes
> > Link-local IPv6 Address . . . . . : fe80::5efe:192.168.1.5%15(Preferred)
> > Default Gateway . . . . . . . . . :
> > DNS Servers . . . . . . . . . . . : 192.168.1.1
> > NetBIOS over Tcpip. . . . . . . . : Disabled
> >
> > Tunnel adapter Local Area Connection* 9:
> >
> > Media State . . . . . . . . . . . : Media disconnected
> > Connection-specific DNS Suffix . :
> > Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
> > Physical Address. . . . . . . . . : 02-00-54-55-4E-01
> > DHCP Enabled. . . . . . . . . . . : No
> > Autoconfiguration Enabled . . . . : Yes
> >
> > Tunnel adapter Local Area Connection* 14:
> >
> > Connection-specific DNS Suffix . :
> > Description . . . . . . . . . . . :
> > isatap.{90B417F8-A0C1-4A5C-B6FF-A35FD7E1A
> > 224}
> > Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
> > DHCP Enabled. . . . . . . . . . . : No
> > Autoconfiguration Enabled . . . . : Yes
> > Link-local IPv6 Address . . . . . :
> > fe80::200:5efe:191.30.10.199%16(Preferred
> > )
> > Default Gateway . . . . . . . . . :
> > NetBIOS over Tcpip. . . . . . . . : Disabled
> >
> > C:\Users\Daddy>
> >
> > Any suggestions?
> > --
> > leave well enough alone
>
>
> What is the IP address of the device you are trying to ping?
> A general error usually means your machine can not find a route to the
> device.
>
>

raymondvillain wrote:
> The address of the device I want to reach is 191.30.10.210.
>
> Originally my vista machine was set to automatically obtain an IP address.
> I changed that. Went through network>properties>IPv4>properties>set IP
> address and subnet mask, etc. so that now the IP address is 191.30.10.199.
> Still won't work.
>
> If I have to I'll use an XP machine. But it would sure be convenient if I
> could use the vista notebook.
>
> I'm baffled. I thought ethernet was "stateless" and that there shouldn't be
> any problem just because I'm using a PC that operates on vista. Any
> suggestions would be greatly appreciated.

Well, ethernet itself as a method of connecting to a network isn't
operating system-dependent (if that's what you mean by "stateless"), but
the operating system knowing how to use the hardware connected to a
computer is driver-dependent or at it least needs to know how to
communicate with the device. I'm thinking here of the problems Vista has
with NAS devices.

Obviously I've never used your device and so don't know how you got it
to work in XP, but just as obviously it isn't working in Vista and so
the logical place to get support is the device mftr.


Malke
--
Elephant Boy Computers
www.elephantboycomputers.com
"Don't Panic!"
MS-MVP Windows - Shell/User