PC won't connect to Switch but Ok with Router?

Mel_P

Mel_P

Mel_P

Soldato
Joined
27 Feb 2004
Posts
2,577
Location
Kent
I have a Virgin Media modem and have a TP-link 8-way switch and a Netgear wirless router connected to two of the modem's ports.

All of my kit (2 pcs / 2 printers / NAS / homeplug) are connected to the TP-link switch BUT one PC just won't NOW connect to it and show a connection to the internet - BUT IT USED TO!!

It connects to the network but shows a red "X" on the internet link on the "map".

If I plug the PC network cable into the WGR 614 netgear router it connects OK.

WHAT can have changed to stop a PC working through a switch? I cannot understand this.....

Any ideas please?
 
I cannot understand this - I have disconnected everything and just plugged the errant PC into my Virgin "Superhub". Again it connects to the network but not to the internet. I have a PCI network connection and one on the m/board and they both behave the same - must be some software setting? Beats me!

Mel
 
You are possibly correct - but what and how do I resolve it - I installed an additional PCI network card and this shows the same behaviour - where do I attack the PC! please.
 
The set up doesn't matter as much as these "facts":

I (used to) connect ALL of my devices via an 8-way gigabit TP link switch to a VM supahub.

I also have a Netgear WGR 614 wifi / router which was connected directly to the VM hub to provide WiFi (only).

"Suddenly" 1 PC connected to the switch is not seeing the internet (but can see the network).

Now, EVEN connecting it directly to the VM hub it cannot see the internet (this is the puzzling thing).

However, if I plug the errant PC cable directly into one of the ports on the WGR614 it works OK (even more puzzling).

Have tried different cables etc.
 
Last edited:
Have tried ipconfig commands to no avail.

Tried drivers already - no difference.

Can't seem to access VM hub via 192.168.0.1 - I could yesterday!

ill try hard reset on VM superhub later when nobody is using the internet for work (work from home)
 
VM not set as router - thus I have 2 x wifi networks available.

When all plugged into TP-Link switch then all devices automatically assigned IPs 192.168.0.x EVEN the PC that can't access the internet.

As I have it now (and its the only way I can get nearly ALL to work)

- printers, NAS, PC1 PC2 - via switch assigned IP via VM S/Hub 192.168.0.2 upwards.

- errant PC3 - plugged into wifi router which assigns IPs 192.168.1.2 etc. via its own DCHP. Ipad also connected to this as 192.168.1.3

ALL works except PC3 cannot access NAS on switch.

Mel
 
Error Log has lots of IP / DNS errors - but I am not sure which is cause and which is effect!

The errant PC is win 7; the OK PCs are XP SP3.

It's only strange as I have to use the WGR614 on one port of the SH as the VM S/Hub wifi is carp.

Don't forget - last week it all worked OK
 
Nocky24 said:
Wouldn't it be easier to leave your SH as a router/DHCP and configure the netgear as an access point to the same network??
Click to expand...

Couldn't get it to work - but having 2 x wifi works Ok - range of netgear far superior.

Nocky24 said:
I think the issue you're running into is double natting, but I could be wrong. Either way, I'd recommend the above config unless there's a specific reason you want to keep them separate?
Click to expand...

Can you explain double natting - having 2 x DCHP is Ok as long as different IP ranges?

BUT it worked last week - will shut it all down tonight with some hard resets and try again then

Till tommorow . . . . .
 
Well what do you know! My printers are assigned fixed IP addresses. The Virgin Hub seemed to have forgotten that and it kept assigning my PC3 to the same address as one of the printers. This didn't show up in the list of devices in the VM SuperCrapHub as it had not assigned the IP address via DCHP

So it was going on unbeknown to me. All OK now - and I am wiser.

I thought it was someting weird! I manually assigned my PC an IP address and all is OK. What a waste of time!
 
You must log in or register to reply here.
Back
Top Bottom