Open Webif times out?

[NoDeity]

Not sure where I should have posted this but I figure it's a network issue.
I just reinstalled Windows 8.1 Pro 64bit, and for some reason, now I can't access Webif through my browser. First time this has happened, I reinstall as a matter of habit every 6 to 12 months, just to give it a cleanout. I've had the T3 since they were first released, but for some reason now when I try to open Webif I get this message after a minute or so, "The server at 192.168.1.235 is taking too long to respond".
info in box is:

IP: 192.168.1.235
Broadcast: 192.168.1.255
Gateway: 192.168.1.1 Default
Netmask: 255.255.255.0
MAC: 00:1E:A0:00:5F:41

I can build a new system and install an OS easily, but I've always had issues understanding Net related issues beyond the basics. I'm using Firefox, but I've tried it in Chrome and Icedragon, to no avail. I also have a NAS on the system which is running fine. Is there something basic I'm missing here?

[simoncasey]

Windows 8 Pro running in a home network has some of the old workgroup settings disabled that were on older (xp and before) systems. The theory being that Pro users won't normally be using workgroup networks and because they are "pro" they know how to fix it up.

There's a number of things to check, try enabling netbios (Google netbios on win8).

Also worth checking how your T3 is configured on the network, static or DHCP IP and how your router manages that.

[NoDeity]

Windows 8 Pro running in a home network has some of the old workgroup settings disabled that were on older (xp and before) systems. The theory being that Pro users won't normally be using workgroup networks and because they are "pro" they know how to fix it up.
There's a number of things to check, try enabling netbios (Google netbios on win8).
Also worth checking how your T3 is configured on the network, static or DHCP IP and how your router manages that.

Thanks for that. Netbios is set to default, and because I have other equipment on the network, like the NAS and the T3 I think it would be best to leave it there. I've also tried reserving a DHCP address in the router, and the T3 is set to automatic DHCP. Seems really strange that a fresh install would just randomly set different settings, so I can only assume something has changed that I haven't taken into account. Really don't want to do a fresh install to see what happens though!

[MrQuade]

You also seem to be connecting via the t3's IP address, so NetBIOS shouldn't be the problem.

Have you tried the basics like pinging the t3's IP address from the Windows machine?

[simoncasey]

If you can ping the T3 Then it is worth testing OpenWebIF in the T3. , OpenWebIF is a plugin so it is worth checking that it is running in the plugins menu.

Also, there may be an issue with the port being blocked through your router/firewall. Try entering :80 at the end of the IP address, assuming that OpenWebIF is on the default port.

Otherwise it may be worth trying a reinstall of the firmware from sub.

[NoDeity]

You also seem to be connecting via the t3's IP address, so NetBIOS shouldn't be the problem.

Have you tried the basics like pinging the t3's IP address from the Windows machine?

Thanks, I've enabled telnet and used this command
telnet [192.168.1.235] [80] I think the port is 80 but I keep getting invalid command. Oh and Simon, Webif is installed and apparently running. What is the correct command line to ping 192.168.1.235? Thanks

[prl]

You also seem to be connecting via the t3's IP address, so NetBIOS shouldn't be the problem.

Have you tried the basics like pinging the t3's IP address from the Windows machine?

Thanks, I've enabled telnet and used this command
telnet [192.168.1.235] [80] I think the port is 80 but I keep getting invalid command. Oh and Simon, Webif is installed and apparently running. What is the correct command line to ping 192.168.1.235? Thanks

ping 192.168.1.235

The telnet command is correct apart from the brackets. You should use:
telnet 192.168.1.235 80

If the telnet command connects (you get a "Connected to" message from the command), and then you type something other than an empty line, you should get something like:
HTTP/1.1 400 Bad Request
and a closed connection unless you've carefully crafted an actual HTTP request

I'm assuming you're using a command-line telnet.

[NoDeity]

You also seem to be connecting via the t3's IP address, so NetBIOS shouldn't be the problem.

Have you tried the basics like pinging the t3's IP address from the Windows machine?

Thanks, I've enabled telnet and used this command
telnet [192.168.1.235] [80] I think the port is 80 but I keep getting invalid command. Oh and Simon, Webif is installed and apparently running. What is the correct command line to ping 192.168.1.235? Thanks

ping 192.168.1.235

The telnet command is correct apart from the brackets. You should use:
telnet 192.168.1.235 80

If the telnet command connects (you get a "Connected to" message from the command), and then you type something other than an empty line, you should get something like:
HTTP/1.1 400 Bad Request
and a closed connection unless you've carefully crafted an actual HTTP request

I'm assuming you're using a command-line telnet.

Yeah telnet.exe the basic windows program. I've tried typing in the command just as you've shown, but I keep getting "invalid command". Also tried using ping in the CMD box and got this "Connecting to 192.168.1.235...Could not open connection to the host, on port 80: connect failed" Also tried a tracert and got this:

tracert 192.168.1.235
tracing route to WizT3 [192.168.1.235]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms WizT3 [192.168.1.235]

Trace complete. very weird

[prl]

... Also tried using ping in the CMD box and got this "Connecting to 192.168.1.235...Could not open connection to the host, on port 80: connect failed" ...

That's a wierd thing for ping to have as an error, because ping doesn't try to establish a connection, and doesn't use port 80, or any port, for that matter. Ping uses ICMP Echo/Echo reply packets which don't contain any port numbers.

My T3 certainly responds to pings (from WIn7 in VirtualBox on OS X):

Code: Select all

C:\Users\prl>ping 192.168.178.29

Pinging 192.168.178.29 with 32 bytes of data:
Reply from 192.168.178.29: bytes=32 time<1ms TTL=127
Reply from 192.168.178.29: bytes=32 time<1ms TTL=127
Reply from 192.168.178.29: bytes=32 time=1ms TTL=127
Reply from 192.168.178.29: bytes=32 time=1ms TTL=127

Ping statistics for 192.168.178.29:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 1ms, Average = 0ms

C:\Users\prl>

I don't seem to have telnet, though.

[MrQuade]

I don't think that telnet is installed by default in Windows since after XP. That will be the source of the invalid command errors.

It sounds like you have used the worrying command for ping too. There is no requirement to add an 80 in anywhere.

[prl]

... There is no requirement to add an 80 in anywhere.

There is if you want to use telnet to test connectivity to an HTTP server. Then the correct form is:
telnet IPaddress 80
or
telnet IPaddress http

Also, the error I get when I try to run telnet on Win7 isn't simply "invalid command". It's a much longer message:

Code: Select all

C:\Users\prl>telnet
'telnet' is not recognized as an internal or external command,
operable program or batch file.

C:\Users\prl>

[netmask]

For what it's worth I had to enable telnet on my Win 7 machine

[NoDeity]

... Also tried using ping in the CMD box and got this "Connecting to 192.168.1.235...Could not open connection to the host, on port 80: connect failed" ...

That's a wierd thing for ping to have as an error, because ping doesn't try to establish a connection, and doesn't use port 80, or any port, for that matter. Ping uses ICMP Echo/Echo reply packets which don't contain any port numbers.

My T3 certainly responds to pings (from WIn7 in VirtualBox on OS X):

Code: Select all

C:\Users\prl>ping 192.168.178.29

Pinging 192.168.178.29 with 32 bytes of data:
Reply from 192.168.178.29: bytes=32 time<1ms TTL=127
Reply from 192.168.178.29: bytes=32 time<1ms TTL=127
Reply from 192.168.178.29: bytes=32 time=1ms TTL=127
Reply from 192.168.178.29: bytes=32 time=1ms TTL=127

Ping statistics for 192.168.178.29:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 1ms, Average = 0ms

C:\Users\prl>

I don't seem to have telnet, though.

Hmm, using ping in cmd I get this
C:\WINDOWS\system32>ping 192.168.1.235

Pinging 192.168.1.235 with 32 bytes of data:
Reply from 192.168.1.235: bytes=32 time<1ms TTL=64
Reply from 192.168.1.235: bytes=32 time<1ms TTL=64
Reply from 192.168.1.235: bytes=32 time<1ms TTL=64
Reply from 192.168.1.235: bytes=32 time<1ms TTL=64

Ping statistics for 192.168.1.235:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

C:\WINDOWS\system32>

Like I said, I'm not all that ejimacated when it comes to networking, so what am I doing wrong with webif.?

[MrQuade]

There is if you want to use telnet to test connectivity to an HTTP server.

I was talking about ping, not telnet.

I believe he said he was getting messages about port 80 in regards to the ping response. Which is unusual as you pointed out.

I am not exactly sure what he did wrong to get that message, jusr that it wasn't correct.

[MrQuade]

That's the response you'd be looking for.

The next step would be to ensure that it is the t3 responding to those pings.

You can try disconnecting the t3 from the network and setting if pings still work.

If they do, something else had taken that address though that seems unlikely. If pins stop them it is indeed the t3 you are pinging.

If the t3 is definitely confirmed as the device returning the pings, then the web ui might not be responding.

I assume you have fully rebooted the t3 to deep standby already just for good measure?

[prl]

... Like I said, I'm not all that ejimacated when it comes to networking, so what am I doing wrong with webif.?

The ping and tracert results you posted shows that the underlying networkis working (and that the T3 responds to ICMP echo request messages and to the UDP messages that tracert uses).

It's possible that there's a firewall restriction on your Win8 box that's blocking access from your PC to web servers on your local net (assuming that you can get to web pages in the wider internet). I'm not sure what the purpose of such a rule would be, and I don't know how to check whether there is one.

It's not uncommon for firewalls to simply not pass on traffic that they want to block, rather than returning an error, That's to slow down people who try to portscan your network looking for vulnerable services. A rule that did that would produce a timeout error when a browser (any browser) tried to connect to a Web server that was being blocked in that way.

It's also possible for a similar firewall protection to be in place on your router, but it's the change on the PC that seems to have triggered the problem.

I'd still suggest trying to get the telnet command for Win8 and trying to connect to port 80 on the T3 as you did before. However, I don't know how you do get it.

[MrQuade]

Telnet needs to be installed as an optional component under the add remove software section. At least under win 7. Not sure what they did with windows 8.

[prl]

Found it! On Win7 it's on Control Panel>Programs>Turn Windows features on or off, then tick the Telnet client box.

It does what I expect it to do when I connect to port 80 on my T3.

[simoncasey]

Do you have any other devices (tablet, iPhone, other PC/laptop) that you can check from.

Also, confirm that OpenWebIF is actually configured for port 80 in the plugin setup (it should be but you never know)

[peteru]

Check that your browser is not using a proxy for your local network. It may be a system wide setting under Windows.

[NoDeity]

Seems to be working on my laptop, thanks for suggesting this btw Simon
So I assume the problem is in my Router or my Firewall? I've tried reserving the Webif address in DHCP to no avail, and consequently went back to no reservation. I've tried allowing the following services through the firewall:

Netlogon Service
Routing and remote access
Secure Socket Tunneling Protocol

to no avail, and consequently reverted back to original settings. Frankly I'm flummoxed. It's not like I'm going to cry over this, and at least I can access it vie my Lappy, but it certainly is annoying. Thanks anyway guys, your help is appreciated

[simoncasey]

What version of windows are your running on the laptop, Win 7 or 8, Pro or Home?

[NoDeity]

What version of windows are your running on the laptop, Win 7 or 8, Pro or Home?

8.1 Pro, same as my PC.

[NoDeity]

Got it working, seems all I had to do was reinstall Windows! Easy...

[NoDeity]

OK, I now have a definitive answer to my problem. Seems the Killer E200 drivers I was using are complete crap! I removed the lot, and simply installed the basic inf driver, and everything now works a treat. Wish I'd figured that out before i reinstalled my system. Even then it was just chance that I noticed where it was breaking down. The Windows 8 to Windows 8.1 update was installing crap I didn't need. Thanks for the help though guys.