Limited or no connectivity... apparently

[Simon]

Hi,

I have windows Vista Ultimate with all the latest updates, (as far as I
know).
I am happily connected to the internet with the VISTA machine and I can
send/receive emails without any problem.

I also have 2 computers connected to my VISTA machine, a windows XP(sp2) and
a windows 98 machine.

But neither machines can go on the internet, I can ping the XP machine but I
get a 169.254.*.* IP address.
I can connect to it via remote desktop, (I don't use a screen for that PC as
it is only used to do lengthy calculations), and work without any problems.

I use a router, (Genius), but even if I connect the 2 computers directly,
(the XP and the VISTA), I still cannot get the XP machine on the internet.

The fact that the IP address is in the range 169.254.*.* tells me that there
is something else wrong.

But what I don't understand is, if the remote desktop works why do I have
limited connectivity?
What can I try to fix the problem?

Many thanks

Simon

 

[Not Me]

sometimes you will get a corruption in the LSP or Winsock, many times caused
by spyware or removal of same.
The common symptom is that IM, Email or even remote desktop may work, but
the browser can't get to a webpage.
If you remove ALL Network adapters in Device manager then reboot and let
XP/98 restore them, the XP/98 machine should then be able to connect.
If it is the LSP, there is also an lspfix.exe file available (google it)
that does somewhat the same thing.

Normally your router will have an IP of 192.168.1.1 or such, that should be
the IP range of the XP machine. (192.168.1.105 or such)
Make sure the router is setup to use DHCP and has enough IP addresses
available.
If the router is set to only assign 1 IP via DHCP, you can have that problem
as well.

 

[Simon]

sometimes you will get a corruption in the LSP or Winsock, many times

caused by spyware or removal of same.
The common symptom is that IM, Email or even remote desktop may work, but
the browser can't get to a webpage.
If you remove ALL Network adapters in Device manager then reboot and let
XP/98 restore them, the XP/98 machine should then be able to connect.
If it is the LSP, there is also an lspfix.exe file available (google it)
that does somewhat the same thing.

Thanks, I tried that but it did not fix the problem the VISTA machine does
not have a valid IP address as well.
I get the same problem as
http://thevistaforums.com/index.php?showtopic=14072
but none of the solutions seem to work.

My network is reported as "unindentifed network" with "Local Access Only"
But my Adsl modem also has "Local Access Only".

Normally your router will have an IP of 192.168.1.1 or such, that should
be the IP range of the XP machine. (192.168.1.105 or such)
Make sure the router is setup to use DHCP and has enough IP addresses
available.
If the router is set to only assign 1 IP via DHCP, you can have that
problem as well.

The router has been working fine, and in any case if I plug the XP machine
directly with the VISTA machine, (not using the router), it still does not
work.

Obviously a windows update has caused some kind of change to my settings.

Simon

 

[Not Me]

Maybe I am missing something.
Is the CAT5 cable from the ADSL modem plugged into the WAN port on the
router?
Is the router is set to get an IP automatically?
Is the router set to assign IP addresses via DHCP and has at least 3
addresses available?
Are all PCs set to 'get an IP address automatically'?
Are the Vista Machine, XP machine and W98 machines plugged into network
ports on the router? (numbered 1-4)
Check your owners documentation for the default IP of the router and modem,
but 98% of the ones I use have IPs as described below.
I have seen people plug the cable from the modem into one of the network
ports (numbered 1-4) instead of the WAN port of the router.
When that happens, the only PC that will connect is the one plugged into the
WAN port.
I have also seen improperly configured modems.
Generally the modem has an address at 192.168.100.1 but you may need to
check the modem manual to access it.
The modem should be set to get an IP address automatically, and assign an IP
automatically (to the router).
The IP address for the router may be 192.168.100.x on the (WAN) modem side
but should be 192.168.1.1 on the LAN side.
As far as the Modem is concerned, it's IP should be the gateway address in
the router and the router's IP should be the gateway IP showing on the PCs.
The external (ISP side of the modem) may show a 169.xx.xx.xx IP, but the LAN
side should be 192.168.100.1 or such.
If any of the above is NOT true, power everything down.
Start with the cable from the modem to the WAN port and make sure every
cable is correctly placed.
Then power on the modem.
After 2 minutes, power on the router.
After 2 minutes, power on the PCs, 1 at a time.
Do they work?

 

[Rick Rogers]

Hi,

First you want to find out where the problem lies. Connect a monitor &
keyboard to the XP machine and connect it directly to your internet feed,
not through another host or the router, but directly to it. If it connects
properly, then you know there is a problem in the configuration, if not then
you have a problem with the network stack in XP.

--
Best of Luck,

Rick Rogers, aka "Nutcase" - Microsoft MVP

Windows help - www.rickrogers.org
My thoughts http://rick-mvp.blogspot.com

 

[Simon]

Are all PCs set to 'get an IP address automatically'?

Yes/

Are the Vista Machine, XP machine and W98 machines plugged into network
ports on the router? (numbered 1-4)

I am not using the router anymore, only the XP is connected to the VISTA
machine.

Then power on the modem.
After 2 minutes, power on the router.
After 2 minutes, power on the PCs, 1 at a time.
Do they work?

Thanks again, but it still does not work.

As I said I have taken the router and modem out of the equation.

The VISTA computer is now connected to the XP computer directly, (both via
their respective network cards).
And I am still having a problem, (unidentified network, private IP address
169.*.*.*).

So basically the VISTA machine cannot get an IP address.

Simon

 

[Simon]

First you want to find out where the problem lies. Connect a monitor &
keyboard to the XP machine and connect it directly to your internet feed,
not through another host or the router, but directly to it. If it connects
properly, then you know there is a problem in the configuration, if not
then you have a problem with the network stack in XP.

Thanks for the reply.
But the problem is the network, if I unplug the modem and the router and
simply plug the XP computer to the VISTA computer, (via their network
cards), I still cannot connect properly.

I still get network limited connectivity.
I also get the 'Unidentified Network' message telling me that there is
something wrong with the network configuration.

Simon

 

[Not Me]

If you just take a CAT5 cable and connect the NIC from 1 computer to
another, they will never connect.
To do that requires what is called a crossover cable. It looks the same as a
CAT5, but 2 of the wires are reversed internally.
Ask at a computer store.
That is why you connect the PCs to the switch portion of the Router.
A regular CAT5 cable plugged into the router works to connect the 2
computers because the router sends the data to the correct wires in the
cable, a direct connection does NOT.
The modem or router then 'bridges' the connection between your ISP and the
computers. See my previous message describing internal and external IPs.
To get an IP address, you need to have a DHCP server. Unless you set one of
the computers as a DHCP server and use Internet Connection Sharing (which
isn't a good idea when you have the hardware you described).
The ADSL modem provides that service, generally for 1 IP address.
It then assigns that IP address to the Router which can supply up to 254 IP
addresses via the routers DHCP service.
If you don't have the modem connected, neither machine has a path to the
internet..
If you look at my last post, and make sure everything is connected and setup
as described, I think you'll be surprised when it actually works.
That is assuming all the hardware is good.

 

[Simon]

If you just take a CAT5 cable and connect the NIC from 1 computer to
another, they will never connect.

I am using a cross over cable.

If you don't have the modem connected, neither machine has a path to the
internet..

They cannot even connect to each others.

If you look at my last post, and make sure everything is connected and
setup as described, I think you'll be surprised when it actually works.

I will have another look, but I think I need to get the network working and
then I can worry about the internet.
As it is now I cannot even get a local network.

Simon

 

[Simon]

Try going to start in search type service.msc when you get there

disconnect and reconnect.

I am not sure I understand, disconnect what?
And what must I do with the services? What service do you want me to
stop/start?

Simon

 

[Mr. Arnold]

Hi,

I have windows Vista Ultimate with all the latest updates, (as far as I
know).
I am happily connected to the internet with the VISTA machine and I can
send/receive emails without any problem.

I also have 2 computers connected to my VISTA machine, a windows XP(sp2)
and a windows 98 machine.

But neither machines can go on the internet, I can ping the XP machine but
I get a 169.254.*.* IP address.

Yeah that's right. The machine cannot access the Internet, because the O/S
assigned the 169.xxx IP to the NIC, which it does when the O/S cannot get an
IP from the DHCP server on the LAN. It's sign of trouble.

I can connect to it via remote desktop, (I don't use a screen for that PC
as it is only used to do lengthy calculations), and work without any
problems.

The 169.xxx IP when assigned to a computer's NIC will allow the computer to
access other computers in a LAN situation. But the IP will not allow the
computer to access the WAN/Internet, because it's not using an IP that was
assigned to it by a router and its DHCP server as an example.

I use a router, (Genius), but even if I connect the 2 computers directly,
(the XP and the VISTA), I still cannot get the XP machine on the internet.

Sometimes, the 169.xxx IP gets locked on the NIC by the O/S, and you have to
use IPconfig /release and IPconfig /renew at the Command Prompt to release
the IP. But sometimes that doesn't work either, and you have to reset the
TCP Stack on the O/S to release the IP, which the procedures for doing this
are different for Win 9'x as opposed to a Win NT classed O/S like Vista and
XP -- Vista and XP should be the same procedure. You can use Google and find
out how to reset TCP Stack on the O/S.

The fact that the IP address is in the range 169.254.*.* tells me that
there is something else wrong.

See above

But what I don't understand is, if the remote desktop works why do I have
limited connectivity?
What can I try to fix the problem?

See above

 

[Simon]

Sometimes, the 169.xxx IP gets locked on the NIC by the O/S, and you have
to use IPconfig /release and IPconfig /renew at the Command Prompt to
release the IP. But sometimes that doesn't work either, and you have to
reset the TCP Stack on the O/S to release the IP, which the procedures for
doing this are different for Win 9'x as opposed to a Win NT classed O/S
like Vista and XP -- Vista and XP should be the same procedure. You can
use Google and find out how to reset TCP Stack on the O/S.

Thanks for the info, it looks like the right solution/problem.

I can run the 'IPconfig /renew' command
but the 'IPconfig /release *uni*' command gives me a 'The operation failled
as no adapter is in the state permissible for this operation'

So I tried to reset the stack as per microsoft advise,
http://support.microsoft.com/kb/299357

netsh int ip reset c:\resetlog.txt

but that did not work, (no file was created and even after the reboot I have
the same problem).

DHCP does not seem to be enabled, but as far as I can tell it is,

This is my ipconfig /all

-----------------------------------------
Windows IP Configuration

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

PPP adapter Microcom ADSL DeskPorte USB:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microcom ADSL DeskPorte USB
Physical Address. . . . . . . . . :
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : xxx.xxx.xxx.xxx(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.255
Default Gateway . . . . . . . . . : 0.0.0.0
DNS Servers . . . . . . . . . . . : xx.xx.xx.xx
xx.xx.xx.xx
NetBIOS over Tcpip. . . . . . . . : Disabled

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek RTL8139/810x Family Fast
Ethernet NIC
Physical Address. . . . . . . . . : x-x-x-x-x-x
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . :
fe80::ce9:f9e1:22f1:ca3f%35(Preferred)
Autoconfiguration IPv4 Address. . : 169.254.202.63(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :
DHCPv6 IAID . . . . . . . . . . . : 587208024
DNS Servers . . . . . . . . . . . : x:x:x:x::1%1
x:x:x:x::2%1
x:x:x:x::3%1
NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter Local Area Connection* 6:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter #23
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 9:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . :
isatap.{2798FD57-5908-4254-90ED-DD7CCAEFDFB4}
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 18:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . :
isatap.{2798FD57-5908-4254-90ED-DD7CCAEFDFB4}
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 19:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . :
isatap.{2798FD57-5908-4254-90ED-DD7CCAEFDFB4}
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 21:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . :
isatap.{2798FD57-5908-4254-90ED-DD7CCAEFDFB4}
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 22:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . :
isatap.{2798FD57-5908-4254-90ED-DD7CCAEFDFB4}
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 23:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . :
isatap.{2798FD57-5908-4254-90ED-DD7CCAEFDFB4}
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 24:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . :
isatap.{2798FD57-5908-4254-90ED-DD7CCAEFDFB4}
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 26:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . :
isatap.{2798FD57-5908-4254-90ED-DD7CCAEFDFB4}
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 27:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . :
isatap.{2798FD57-5908-4254-90ED-DD7CCAEFDFB4}
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 29:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . :
isatap.{2798FD57-5908-4254-90ED-DD7CCAEFDFB4}
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 31:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . :
isatap.{2798FD57-5908-4254-90ED-DD7CCAEFDFB4}
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 11:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter #24
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : xx::xx:xx:xx.xx.xx.3%41(Preferred)
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . : xx.xx.xx.xx
xx.xx.xx.xx
NetBIOS over Tcpip. . . . . . . . : Disabled

Tunnel adapter Local Area Connection* 33:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft 6to4 Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Temporary IPv6 Address. . . . . . : xx:xx:xx::xx:8a03(Preferred)
Default Gateway . . . . . . . . . : xx:xx:xx::xx:6301
DNS Servers . . . . . . . . . . . : xx.xx.xx.xx
xx.xx.xx.xx
NetBIOS over Tcpip. . . . . . . . : Disabled

 

[Not Me]

Assuming the router is good, you should be able to get the network going.
On the Vista machine, uninstall the NIC (if you have more than one network
adapter remove them all) from device manager.
Power down.
Plug the Vista machine into port 1 on the router with a standard CAT5 cable,
then turn on the router, wait 2 minutes and power on the Vista machine.
It should detect and install the NIC. Once it says new hardware installed
and ready, open your browser and type 192.168.1.1 in the address box.
A few routers use 192.168.0.1, so if 1.1 fails try that.
Once in the router, check the settings, DHCP enabled, starting IP is
192.168.1.50 (or such). I do that so I can assign fixed IPs if desired on my
network as well as using DHCP.
Most routers have a setting for how many IPs to allow using DHCP. Make sure
the router is set to assign at least as many as you plan to connect.
If the machine is not able to connect to the router with a standard cat5
cable; the NIC is bad (or has a bad driver) or the cable is bad or you have
a bad router.
Sometimes it is 1, sometimes all 3...
Once you have the Vista machine connected to the router, follow the same
procedure with the XP machine.
Plug the CAT5 cable from the XP machine into port 2 on the router.
Remove the NIC from device manager, reboot. Once the NIC is reinstalled,
open the browser and access the router using the IP above.
Again, if it won't connect, check the cable, and NIC (by now I assume the
router works if Vista will connect to it).
Once you have those 2 networked, go to the W98 system.
Plug the CAT5 cable from the W98 system into port 3 on the router.
Remove the NIC from device manager, reboot. Once reinstalled, open the
browser and see if you can access the router.
Once all machines can see the router, you can setup sharing on each system
as desired.
Then comes the modem.
Once all machines can see the router and sharing is setup, power all 3 down,
power off the router.
Connect the modem's CAT5 cable to the WAN port on the router.
Power on the modem.
After 2 minutes, power on the router.
After 2 minutes, power on the Vista machine.
Can it see the router?
Can it access the internet?

 

[Not Me]

uninstalling/reinstalling the NIC usually resolves the 'locked IP' too,
unless some software sets it back...like malware or some third party
security suites.
The subnet mask on the ADSL USB shows as 255.255.255.255 and the subnet mask
on the realtek adapter shows 255.255.0.0, usually both are 255.255.255.0.
something is amiss there.
But the ADSL modem should be connected to the router to make the network
work properly.
That is a LOT of local area connections. It looks like it keeps creating new
ones every time you attempt to join the network.
If they are listed, I'd be tempted to remove them and have just 1 available
to worry about configuring.

 

[Mr. Arnold]

Thanks for the info, it looks like the right solution/problem.

I can run the 'IPconfig /renew' command
but the 'IPconfig /release *uni*' command gives me a 'The operation
failled
as no adapter is in the state permissible for this operation'

You should just be using IPconfig /release and not ipconfig /release *uni*,
as it would be looking for an adapter that started with *uni* as the name.

So I tried to reset the stack as per microsoft advise,
http://support.microsoft.com/kb/299357

netsh int ip reset c:\resetlog.txt

but that did not work, (no file was created and even after the reboot I
have the same problem).

That command works. I don't know what your problem is with the command.

DHCP does not seem to be enabled, but as far as I can tell it is,

What would be enabled on the NIC would be *Obtain an IP automatically* in
its configuration, to tell the NIC to get its IP from the DHCP server on the
LAN. I don't know because I don't use Internet Connection Sharing between
computers, but in the printout you posted here, the DHCP enabled on a NIC
would be for the computer that is hosting other computers in a ICS
environment I would think.

The DHCP server is on the router for any computer connected to the router,
or the DHCP server is on the host computer and serves an IP to the computers
in an ICS situation.

The router, NIC or cable can be going bad, and the computer cannot get a
DHCP IP from a DHCP server on the LAN The 169.254 IP is being assigned by
the O/S. It could be that a firewall is enabled on the host computer that's
blocking computers in an ICS situation too.

You'll get to the bottom of the root cause, but that's your problem. I would
start with connecting the computers to modem to see if they can get a DHCP
IP from the ISP's network.

 

[Simon]

You should just be using IPconfig /release and not ipconfig /release
*uni*, as it would be looking for an adapter that started with *uni* as
the name.

I also did that and it makes no difference.

That command works. I don't know what your problem is with the command.

no problem, just that the file is not created as expected.
And after the reboot it does not work.

What would be enabled on the NIC would be *Obtain an IP automatically* in
its configuration, to tell the NIC to get its IP from the DHCP server on
the LAN. I don't know because I don't use Internet Connection Sharing
between computers, but in the printout you posted here, the DHCP enabled
on a NIC would be for the computer that is hosting other computers in a
ICS environment I would think.

The DHCP server is on the router for any computer connected to the router,
or the DHCP server is on the host computer and serves an IP to the
computers in an ICS situation.

The router, NIC or cable can be going bad, and the computer cannot get a
DHCP IP from a DHCP server on the LAN The 169.254 IP is being assigned by
the O/S. It could be that a firewall is enabled on the host computer
that's blocking computers in an ICS situation too.

This is posible, but by looking at the amount of similar problems reported
my guess is that some VISTA setting was changed.

You'll get to the bottom of the root cause, but that's your problem. I
would start with connecting the computers to modem to see if they can get
a DHCP IP from the ISP's network.

I have done that and yes, they can connect.

Simon

 

[Simon]

uninstalling/reinstalling the NIC usually resolves the 'locked IP' too,
unless some software sets it back...like malware or some third party
security suites.

I have tried that.
SpyBot S&D does not report any malware and windows defender does not either.

The subnet mask on the ADSL USB shows as 255.255.255.255 and the subnet
mask on the realtek adapter shows 255.255.0.0, usually both are
255.255.255.0. something is amiss there.

But they are set to be automatic, so how can I change their settings?
Do you know where those are set?

But the ADSL modem should be connected to the router to make the network
work properly.
That is a LOT of local area connections. It looks like it keeps creating
new ones every time you attempt to join the network.
If they are listed, I'd be tempted to remove them and have just 1
available to worry about configuring.

I realize that, but as I said, the network itself is not working.

When I connect computer A to computer B via their network cards I still
cannot get a valid IP address.
Once I can connect I will get the best possible setup, for now I cannot get
VISTA to talk to the XP machine on a simple network.

Simon

 

[Rick Rogers]

Make sure you are using an elevated command prompt, not just running one
from an admin account but right clicking the CMD executable or shortcut and
choosing the option to 'run as administrator'.

--
Best of Luck,

Rick Rogers, aka "Nutcase" - Microsoft MVP

Windows help - www.rickrogers.org
My thoughts http://rick-mvp.blogspot.com

 

[Simon]

Make sure you are using an elevated command prompt, not just running one

from an admin account but right clicking the CMD executable or shortcut
and choosing the option to 'run as administrator'.

Yes I am Admin so when I start cmd it runs with 'Administrative privileges'

Simon

 

[Simon]

Yeah that's right. The machine cannot access the Internet, because the O/S
assigned the 169.xxx IP to the NIC, which it does when the O/S cannot get
an IP from the DHCP server on the LAN. It's sign of trouble.

Well in the end I had to do it the dirty way and set a static address.
DHCP is obviously broken with some new updates of VISTA.

So now I have my VISTA machine as 192.168.0.1 and the other machine can see
me properly.

A bit of a hack, but at least it works.

Simon.