small office network with xp

[Paul Dean]

I have a mixture of xp and 98se on a small office network. They work
fine apart from one xp machine. I posted here some weeks ago, but
couldn't resolve the problem. Now I've finally got service pack 2, I've
done a fresh install and get the same issues. This computer used to
work on the network, but then we had a virus attack and had to reinstall
after which it's never worked.

Firstly, the LAN says "Limited or No Connectivity". When I try to
'repair' the connection, it says "Windows could not finish repairing the
problem because the following action could not be completed: Renewing
your IP address."

Here's my ipconfig output:
Windows IP Configuration
Host Name . . . . . . . . . . . . : director
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter WORKGROUP:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek RTL8139/810x Family Fast
Ethernet NIC
Physical Address. . . . . . . . . : 00-30-1B-AB-78-4F
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Autoconfiguration IP Address. . . : 169.254.46.213
Subnet Mask . . . . . . . . . . . : 255.255.0.0
IP Address. . . . . . . . . . . . : fe80::230:1bff:feab:784f%4
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1

Tunnel adapter Teredo Tunneling Pseudo-Interface:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface

Physical Address. . . . . . . . . : FF-FF-FF-FF-FF-FF-FF-FF
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : fe80::5445:5245:444f%5
Default Gateway . . . . . . . . . :
NetBIOS over Tcpip. . . . . . . . : DisabledTunnel adapter Automatic
Tunneling Pseudo-Interface:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . :

Automatic Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : A9-FE-2E-D5
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : fe80::5efe:169.254.46.213%2
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
NetBIOS over Tcpip. . . . . . . . : Disabled

----

I don't know what this Teredo Tunneling Pseudo-Interface is - is it part
of SP2? Also I've now got Microsoft TCP/IP version 6 installed - I
guess that's from SP2 and nothing to worry about?

I've got through the settings on careyholzman.com and everything looks
as it should do.

Any help would be appreciated,
Paul

 

[Malke]

I have a mixture of xp and 98se on a small office network. They work
fine apart from one xp machine. I posted here some weeks ago, but
couldn't resolve the problem. Now I've finally got service pack 2,
I've
done a fresh install and get the same issues. This computer used to
work on the network, but then we had a virus attack and had to
reinstall after which it's never worked.

Firstly, the LAN says "Limited or No Connectivity". When I try to
'repair' the connection, it says "Windows could not finish repairing
the
problem because the following action could not be completed: Renewing
your IP address."

Here's my ipconfig output:
Windows IP Configuration
Host Name . . . . . . . . . . . . : director
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter WORKGROUP:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek RTL8139/810x Family Fast
Ethernet NIC
Physical Address. . . . . . . . . : 00-30-1B-AB-78-4F
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Autoconfiguration IP Address. . . : 169.254.46.213
Subnet Mask . . . . . . . . . . . : 255.255.0.0
IP Address. . . . . . . . . . . . : fe80::230:1bff:feab:784f%4
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1

Tunnel adapter Teredo Tunneling Pseudo-Interface:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface

Physical Address. . . . . . . . . : FF-FF-FF-FF-FF-FF-FF-FF
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : fe80::5445:5245:444f%5
Default Gateway . . . . . . . . . :
NetBIOS over Tcpip. . . . . . . . : DisabledTunnel adapter Automatic
Tunneling Pseudo-Interface:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . :

Automatic Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : A9-FE-2E-D5
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : fe80::5efe:169.254.46.213%2
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
NetBIOS over Tcpip. . . . . . . . : Disabled

----

I don't know what this Teredo Tunneling Pseudo-Interface is - is it
part
of SP2? Also I've now got Microsoft TCP/IP version 6 installed - I
guess that's from SP2 and nothing to worry about?

I've got through the settings on careyholzman.com and everything looks
as it should do.

Any help would be appreciated,
Paul

Remove the Teredo Tunneling. The IP address you are getting indicates
that the machine thinks it should be getting its IP address from a DHCP
server and failing to do so. What is the physical structure of your
network? Ethernet to router? Hub? Switch? ICS? The gateway address is
showing blank and should be provided by the DHCP server. Post back with
the answers to my questions for more help.

Malke

 

[Paul Dean]

Remove the Teredo Tunneling. The IP address you are getting indicates
that the machine thinks it should be getting its IP address from a DHCP
server and failing to do so. What is the physical structure of your
network? Ethernet to router? Hub? Switch? ICS? The gateway address is
showing blank and should be provided by the DHCP server. Post back with
the answers to my questions for more help.

It's 5 PCs off a hub. Two of the PCs access the internet through a 56k
modem, but that's it.

My understanding was that the autoconfiguration of IP address is like a
psuedo-DHCP server in that they allocate themselves, and agree upon, IP
addresses as a group. There isn't one particular DHCP server and the
other machines (mix of xp and 98se) all network with no problem.
Tomorrow I'll remove the Teredo Tunneling and check the cable by trying
it with another PC, but it did work before the reinstall which suggests
the problem should be software related. It's a fresh install.

 

[Lanwench [MVP - Exchange]]

It's 5 PCs off a hub. Two of the PCs access the internet through a
56k modem, but that's it.

My understanding was that the autoconfiguration of IP address is like
a psuedo-DHCP server in that they allocate themselves, and agree
upon, IP addresses as a group. There isn't one particular DHCP
server and the other machines (mix of xp and 98se) all network with
no problem. Tomorrow I'll remove the Teredo Tunneling and check the
cable by trying it with another PC, but it did work before the
reinstall which suggests the problem should be software related.
It's a fresh install.

Don't rely on the autoconfigured addresses to work properly with each other.
If you don't have a DHCP server, assign static addresses on all PCs in a
private/non-routable range like 192.168.1.0, 10.1.1.0, 172.16.1.0, etc....

 

[Paul Dean]

Don't rely on the autoconfigured addresses to work properly with each other.
If you don't have a DHCP server, assign static addresses on all PCs in a
private/non-routable range like 192.168.1.0, 10.1.1.0, 172.16.1.0, etc....

Thanks. I've tried setting static addresses of the form 192.168.X.X and
it's the same - the other four continue to network and the one doesn't.

 

[Lanwench [MVP - Exchange]]

Thanks. I've tried setting static addresses of the form 192.168.X.X
and it's the same - the other four continue to network and the one
doesn't.

OK - leave the IP addresses alone. Are you connecting via a hub, or a
switch? Are you using autosense (for speed & duplex settings) on this NIC?
Do your event logs tell you anything? Got the latest NIC driver from your hw
mfr?

 

[Malke]

OK - leave the IP addresses alone. Are you connecting via a hub, or a
switch? Are you using autosense (for speed & duplex settings) on this
NIC? Do your event logs tell you anything? Got the latest NIC driver
from your hw mfr?

What about firewalls? Check to make sure the lan is allowed as Trusted.

Malke

 

[Paul Dean]

Lanwench [MVP - Exchange] wrote:

OK - leave the IP addresses alone. Are you connecting via a hub, or a
switch? Are you using autosense (for speed & duplex settings) on this
NIC? Do your event logs tell you anything? Got the latest NIC driver
from your hw mfr?

What about firewalls? Check to make sure the lan is allowed as Trusted.

Yep, that's OK. In any case, I imagine it would still get an IP address
(from itself)?

 

[Paul Dean]

OK - leave the IP addresses alone. Are you connecting via a hub, or a
switch? Are you using autosense (for speed & duplex settings) on this NIC?
Do your event logs tell you anything? Got the latest NIC driver from your hw
mfr?

It's a hub; I've never heard of autosense; the xp event logs don't say
anything; yes the driver is up to date.

 

[Paul Dean]

Paul Dean wrote:



Remove the Teredo Tunneling. The IP address you are getting indicates
that the machine thinks it should be getting its IP address from a DHCP
server and failing to do so. What is the physical structure of your
network? Ethernet to router? Hub? Switch? ICS? The gateway address is
showing blank and should be provided by the DHCP server. Post back with
the answers to my questions for more help.

Thanks for all the ideas. I should have had more confidence in myself -
when I thought, "I've checked everything and the software is set up
correctly" I should have known 100% that it was hardware. I put in a
new NIC and it works straight away.

Now we've just had a vsat system installed (satellite dish for always-on
64kbps connection because we live on a mountain). It comes with a box
which is apparently a gateway and a dhcp server (don't know what else,
if anything). For this I have two quick questions:

1) What's the best way to stay secure? All our computers will shortly
have xp pro, fully updated, firewalled and anti-virused. Is it OK to
have each of them individually connect to the gateway?

2) In fact I can only get two of the pcs to see the gateway. I'll try
to sort this out, but in case I can't - is it OK to set up one of these
PCs with ICS? i.e. having two gateways on the same small network?

Cheers,