Virgin Super Hub - Pi set up problems

[mad-hatter]

Hello,

My old set up was a Virgin cable modem and a Belkin router, worked fine.
I've now been supplied with a "Super Hub" and I am having some problems.
I've set it up as a router with no wireless, just cable to the Pi.
I'm trying to do away with the Belkin router (one less thing to go wrong).
From Windows 7, I can connnect to the Pi with no problems.
From the Pi to Windows 7, I can't get a connection.
Ifconfig gives me the inet addr, bcast addr and the mask code.
I try to use Filezilla, and no matter what address or protocol I use,
I am getting Connection timed out, could not connect to server.
On the Pi, I can use a browser ok (midori, iceweasel are fine).

Can somebody please tell me what I need to set on the Pi (Raspbian wheezy).
Its so long ago that I set things up that I've forgotten how.

Regards

[DeeJay]

What server or service are you running on the Windows device to accept the connection? Is a Windows Firewall setting getting in the way?

[mad-hatter]

Hello,

On Windows, putty, tightvnc.
On Pi, tightvnc, x11vnc.

I turned off the windows firewall and my AVG firewall, same problems.
Everything was working, both ways. The only change is from a Virgin modem
and router to a Virgin Super hub.

Regards

[FTrevorGowen]

Hello,

My old set up was a Virgin cable modem and a Belkin router, worked fine.
I've now been supplied with a "Super Hub" and I am having some problems.
I've set it up as a router with no wireless, just cable to the Pi.
I'm trying to do away with the Belkin router (one less thing to go wrong).
From Windows 7, I can connnect to the Pi with no problems.
From the Pi to Windows 7, I can't get a connection.
Ifconfig gives me the inet addr, bcast addr and the mask code.
I try to use Filezilla, and no matter what address or protocol I use,
I am getting Connection timed out, could not connect to server.
On the Pi, I can use a browser ok (midori, iceweasel are fine).

Can somebody please tell me what I need to set on the Pi (Raspbian wheezy).
Its so long ago that I set things up that I've forgotten how.

Can you "ping" both ways? This is the simplest test.
Do the Windows 7 and Pi "network settings" agree? (eg. Pi IP addr 192.168.x.y, Windows 192.168.x.z - ie. both are on the 192.168.x network)
Do you know if the "Super Hub" is running a DHCP server (which the Pi is probably using - that's the common method with router's). IIRC Windows boxes can use other methods to obtain their IP addr.
FWIW I'm also on "Virgin" via a "Scientific Atlanta 2100" cable modem which (I think) can be used via an ethernet port or as a USB modem (it has both sockets). However, given the number of m/c's (not counting mobile 'phones etc.), including upto four Pi's, I have two wireless routers and several switches that (eventually) connect to its ethernet port for WAN/Internet access. Given that you're no longer using a router I'm guessing it's something to do with the "Super Hub's" setup (unless the Windows box is connected via USB and the Pi via ethernet???)
Trev.

[turbine2]

Okay, some questions for you.
Have you changed any of the configuration of the Super Hub?
What IP are your Win 7, Super Hub and PI on?
Can you ping from PC to PI? (Start, Run, CMD then enter PING x.x.x.x where x.x.x.x is the PI IP)
Does the Super Hub indicate that it can see the PI (Login, click on Device Connection Status, can you see the PI in Wired Devices?)
Does the Super Hub indicate that it has issues the PI and address (assuming the PI is not fixed address but uses DHCP)? (Login, click on Advanced button, accept the warning, click on DHCP reservation under DHCP, can you see your PI in IP lease table?)
Can you ping from Super Hub to PI? (Login, click on Advanced button, accept the warning, click on Ping under Tools, enter the PI IP address)
Can you ping from PI to Super Hub? (default Super Hub IP address is 192.168.0.1)
Can you ping from PI to internet (e.g. 8.8.8.8)?

For a short term get around, you can stick the Super Hub into 'Modem Mode' (Login, click on Super Hub Settings, Click on Enable Modem Mode and stick your old router into the port nearest the cable connection, note that when you do this the IP address of the Super Hub changes to 192.168.100.1)

[MattHawkinsUK]

Port forwarding didn't work on my Superhub. I put it into modem mode and setup up my old Netgear router.

This also improved some wireless issues I had.

[turbine2]

Port forwarding didn't work on my Superhub. I put it into modem mode and setup up my old Netgear router.

This also improved some wireless issues I had.

Just, out of interest, what version of the firmware was this on? The current (R37 IIRC) fixed a number of wireless performance issues (among other things).

[mad-hatter]

Hello FTrevorGowen,

Windows 7 - ipconfig - gives me 192.168.z.y

ping from widows - 192.168.z.x ok
- 192.168.z.x-1 ok
- 192.168.z.x-2 ok

Pi - ifconfig - gives me 192.168.z.x

ping from Pi - 192.168.z.y ok
- 192.168.z.y-1 ok
- 192.168.z.y+1 ok

DHCP is switched on.
The LAN IP address 192.168.z.x
DHCP address 192.168.z.y

I turned windows, the super hub and AVG firewalls off, no luck.



Helo turbine2,

Of course I've changed the super hub settings, tyring to get something to work.
I think I've also changed them all back to the original settings.
I know I can always reset the settings.

LAN IP address - 192.168.z.a
Win IP address - 192.168.z.x
Pi IP address - 192.168.z.y

Pinging - see above.

Super hub can see the Pi. - see enclosed wired devices.jpeg
DCHP can see the PI. - see enclosed attached devices.jpeg

Ping - Super Hub to Pi - ok
Ping - 8.8.8.8 - ok

I tried in Modem Mode with a Belkin router.
Windows to Pi - OK
Pi to Windows - No luck



Hello MattHawkinsUK,

I've played with router and modem settings - no luck.


Hello again turbine2,

Firmware V2.37.01



Thanks to you all.

general settings.jpg (32.68 KiB) Viewed 4416 times

wired devices.jpg (17.98 KiB) Viewed 4416 times

attached devices.jpg (17.33 KiB) Viewed 4416 times

[turbine2]

Ok, so for ping PI to Internet works, PI to Super Hub works and PI to Windows 7 works.

What service on the Windows 7 PC are you trying to get? What's not working, you say you can't get a connection but a connection to what? Ping indicates that the network is there so I'm guessing a service?

[mad-hatter]

Hello turbine2,

From the Pi, I can't get filezilla or dolphin to connect to Windows 7
or cups to see my windows printer.
I had these setup and working with my old Virgin modem & Belkin router.

Regards

[turbine2]

Okay, filezilla for FTP, dolphin I'm not sure about (browser? gamecube / Wii emulator? something else?) and CUPS for printing.

I'm guessing (quite possibly incorrectly) that this has something to do with name resolution, can you ping the windows 7 machine by name from the PI? Can you use filezilla by using the IP address of the PC rather than the PC name?

Did you edit your hosts file on the PI originally with the IP address of the Windows 7 PC and now it's on a different address?

[turbine2]

I tried in Modem Mode with a Belkin router.
Windows to Pi - OK
Pi to Windows - No luck

Just noticed this too. If it worked before with the Belkin and no longer works with the Belkin attached to the Super Hub in Modem Mode then it's something else and not the Super Hub. When in Modem Mode the only thing the Super Hub does is take the DOCSIS Cable network and the Ethernet home network and passes traffic through, much like the old modem would have. All services other than that (firewall, DHCP, DNS, NAT, etc.) are disabled by modem mode.

[mad-hatter]

Hello turbine2,

Been playing:-
Installed wheezy RC1 on my PC - Logged in.
On the Pi with filezilla, I can access wheezy on my PC.
So I'm guessing, its some sort of configuration problem with my
Windows 7 setup and nothing to do with the Virgin super hub.

Regards

[turbine2]

So I'm guessing, its some sort of configuration problem with my
Windows 7 setup and nothing to do with the Virgin super hub.

Well, from my professional perspective that's good to hear, although does not solve your problem.

I think at this point I'd start looking at the usual suspects on the Windows 7 PC (firewall, application set up, anything that the service patches have installed since it was last working). Netstat should show you what is running / listening on the PC, and look out for the relevant ports (22, 25, etc.).

netstat -b will give the application name (or add -b -v for the full detail), so look out for the server service against the port, just in case something else has taken over that, although I've got to admit I'm going in to areas I'm not so sure about here and the firewall may kick in elsewhere.

Good luck with getting it working again,

David