Invalid IP configuration with a different twist

Network:

Verison Router w/ DHCP 192.168.1.X
DLINK access point using DLINK router w/ DHCP 192.168.0.X
Cisco access point using DLINK router w/ DHCP 192.168.0.X

Problem:

New Toshiba notebook connects to Verizon router without difficulty, but cannot connect to DLINK or CISCO without "LIMITED" usage (IP configuration error) [With a lot of reset, renew and Win8 troubleshooting it will connect to the DLINK for about an hour, but the magic must be repeated after an hour or so]

History:

4 other Notebooks connect succesfully to any of the 3 access points
3 Phones connect succesfully to any of the 3 access points
2 Tablets connect succesfully to any of the 3 access points

Reason for DLINK or Cisco Connection:

Verizon router is outside of the local network containing shared drives.

More details:

available to serious responders

It may help to add the secondary subnet, IP, etc. to the advanced IPv4 TCP/Ip settings of which ever NIC you are using on the Toshiba, this is sometimes required when connecting to different subnets with the same NIC, although I'm not completely sure why it's not connecting to the other access points like the other notebooks.

The Toshiba may have one of those so called trial anti virus software's creating problems or some of the preinstalled Toshiba bloatware may be causing problems here.

Those other two routers may require a firmware update to work with Windows 8.

You might try setting up a single subnet through the Verizon router, turning off DHCP on the other routers so they can pick up an IP from the Verizon routers DHCP, though this doesn't suit your needs it may help to narrow down the problem.

I highly doubt this is an IP issue but rather a compatibility issue with the machine. Either an IP configuration is configured correctly or it isn't... A device shouldn't be able to connect for like an hour and then not be able to connect. I'd go with checking software and firmware updates rather than changing subnets

Josh

Shadowjk said:

I highly doubt this is an IP issue but rather a compatibility issue with the machine. Either an IP configuration is configured correctly or it isn't... A device shouldn't be able to connect for like an hour and then not be able to connect. I'd go with checking software and firmware updates rather than changing subnets

Josh

Click to expand...

I tend to agree with you here. Although adding the other subnet to the advanced TCP/IP settings can help when connecting to different subnets with the same NIC, it wouldn't hurt to try.

There are also better ways to isolate shares from certain users without setting up a separate subnet, most people are completely unaware of how to do this with Windows but between the Homegroup and Workgroup there is a virtual wall with a password required to get through it, it's easy to keep people from accessing Homegroup shares if they are in the workgroup. This is one of the reasons why they refer to a Homegroup as a private Domain in Windows 8.