Wifi/ethernet conflict
Posted by bartdietrich
|
Wifi/ethernet conflict November 16, 2018 04:30AM |
Registered: 9 years ago Posts: 106 |
Hi all,
I have a very annoying communications issue with a computer connected to an Ormerod 2 at work. Basically, it's either internet via wifi, or talking to the printer via ethernet, but not both at the same time.
The printer is attached to a Windows 7 computer via ethernet cable and so long as I don't plug in the Wifi dongle, I can talk to the printer without issue. When I plug in the Wifi dongle, I get internet connectivity but lose the ability to connect to the printer (browser reports request timed out). HOWEVER: I am still able to ping the printer! The Wifi adapter is configured for DHCP and the ethernet adapter as static IP. Sounds like a routing issue of some sort but I don't know enough about networking to fix it. Does anyone have any ideas?
I had the exact same problem on a previous computer that was connected to the printer but solved it by wiping everything and reinstalling Windows from scratch. This is quite a drastic measure and I'd rather not have to do it with this computer, especially after having spent hours/days downloading and installing updates (the computer had not been used for quite some time) and syncing Dropbox/Google drive/OneDrive!
Cheers,
Bart
I have a very annoying communications issue with a computer connected to an Ormerod 2 at work. Basically, it's either internet via wifi, or talking to the printer via ethernet, but not both at the same time.
The printer is attached to a Windows 7 computer via ethernet cable and so long as I don't plug in the Wifi dongle, I can talk to the printer without issue. When I plug in the Wifi dongle, I get internet connectivity but lose the ability to connect to the printer (browser reports request timed out). HOWEVER: I am still able to ping the printer! The Wifi adapter is configured for DHCP and the ethernet adapter as static IP. Sounds like a routing issue of some sort but I don't know enough about networking to fix it. Does anyone have any ideas?
I had the exact same problem on a previous computer that was connected to the printer but solved it by wiping everything and reinstalling Windows from scratch. This is quite a drastic measure and I'd rather not have to do it with this computer, especially after having spent hours/days downloading and installing updates (the computer had not been used for quite some time) and syncing Dropbox/Google drive/OneDrive!
Cheers,
Bart
|
Re: Wifi/ethernet conflict November 16, 2018 05:45AM |
Registered: 8 years ago Posts: 123 |
With the wifi connected, press windows key and X key at the same time. Then click at Command Prompt. Type ipconfig /all at the Command Prompt window, press Enter,
Then do the same with the ethernet connected.
Paste the contents here, labelled (and preferably using the "formatted code" button in the post to make it more readable)
e.g.
And we'll see what we can see.
Then do the same with the ethernet connected.
Paste the contents here, labelled (and preferably using the "formatted code" button in the post to make it more readable)
e.g.
Ethernet adapter Ethernet:
Connection-specific DNS Suffix . : cheeseandham.local
Description . . . . . . . . . . . : Hyper-V Virtual Ethernet Adapter
Physical Address. . . . . . . . . : 64-00-6A-98-85-B8
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::4a5:79e4:6146:ee00%11(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.0.26(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : 14 November 2018 20:38:06
Lease Expires . . . . . . . . . . : 17 November 2018 08:38:06
Default Gateway . . . . . . . . . : 192.168.0.1
DHCP Server . . . . . . . . . . . : 192.168.0.2
DHCPv6 IAID . . . . . . . . . . . : 224657514
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1E-9E-CB-6C-64-00-6A-98-85-B8
DNS Servers . . . . . . . . . . . : 8.8.8.8
8.8.4.4
Primary WINS Server . . . . . . . : 192.168.0.2
NetBIOS over Tcpip. . . . . . . . : Enabled
And we'll see what we can see.
|
Re: Wifi/ethernet conflict November 16, 2018 06:41AM |
Registered: 9 years ago Posts: 106 |
Hi cheeseandham,
Thanks for your reply.
The printer is configured for static IP, 192.168.0.20, gateway 192.168.0.1, netmask 255.255.255.0.
This is the output from ipconfig without the Wifi dongle attached:
And this is the output with the Wifi dongle attached:
Cheers,
Bart
Thanks for your reply.
The printer is configured for static IP, 192.168.0.20, gateway 192.168.0.1, netmask 255.255.255.0.
This is the output from ipconfig without the Wifi dongle attached:
Windows IP Configuration
Host Name . . . . . . . . . . . . : BART-LAB-PC
Primary Dns Suffix . . . . . . . : campus.gla.ac.uk
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : campus.gla.ac.uk
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) 82579LM Gigabit Network Connection
Physical Address. . . . . . . . . : F8-B1-56-D4-B0-14
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::158e:8975:f3c:f63f%11(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.0.10(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.1
DHCPv6 IAID . . . . . . . . . . . : 267956566
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1A-D9-88-78-F8-B1-56-D4-B0-14
DNS Servers . . . . . . . . . . . : 8.8.8.8
4.4.4.4
NetBIOS over Tcpip. . . . . . . . : Enabled
Tunnel adapter isatap.{70B4C8B4-2385-4A53-B4DE-F2E39913E697}:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Tunnel adapter 6TO4 Adapter:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft 6to4 Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Tunnel adapter Local Area Connection* 11:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
And this is the output with the Wifi dongle attached:
Windows IP Configuration
Host Name . . . . . . . . . . . . : BART-LAB-PC
Primary Dns Suffix . . . . . . . : campus.gla.ac.uk
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : campus.gla.ac.uk
gla.ac.uk
Wireless LAN adapter Wireless Network Connection:
Connection-specific DNS Suffix . : gla.ac.uk
Description . . . . . . . . . . . : NETGEAR WNA3100M N300 Wireless Mini USB Adapter
Physical Address. . . . . . . . . : 8C-3B-AD-D4-6A-9A
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::1175:1ab:df01:d3bd%14(Preferred)
IPv4 Address. . . . . . . . . . . : 172.30.147.91(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.128.0
Lease Obtained. . . . . . . . . . : 16 November 2018 11:31:58
Lease Expires . . . . . . . . . . : 16 November 2018 11:46:57
Default Gateway . . . . . . . . . : fe80::f2f7:55ff:febe:2680%14
172.30.128.1
DHCP Server . . . . . . . . . . . : 172.31.1.1
DHCPv6 IAID . . . . . . . . . . . : 260848557
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1A-D9-88-78-F8-B1-56-D4-B0-14
DNS Servers . . . . . . . . . . . : 130.209.4.16
130.209.4.18
NetBIOS over Tcpip. . . . . . . . : Enabled
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) 82579LM Gigabit Network Connection
Physical Address. . . . . . . . . : F8-B1-56-D4-B0-14
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::158e:8975:f3c:f63f%11(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.0.10(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.1
DHCPv6 IAID . . . . . . . . . . . : 267956566
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1A-D9-88-78-F8-B1-56-D4-B0-14
DNS Servers . . . . . . . . . . . : 8.8.8.8
4.4.4.4
NetBIOS over Tcpip. . . . . . . . : Enabled
Tunnel adapter isatap.{70B4C8B4-2385-4A53-B4DE-F2E39913E697}:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Tunnel adapter 6TO4 Adapter:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft 6to4 Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Tunnel adapter Local Area Connection* 11:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Tunnel adapter isatap.gla.ac.uk:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . : gla.ac.uk
Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Cheers,
Bart
|
Re: Wifi/ethernet conflict November 16, 2018 06:52AM |
Registered: 8 years ago Posts: 123 |
Bart,
It looks like you are configured for two different networks, and both are configured to go out to the Internet, but if the ethernet network isn't connected to the Internet then this could potentially cause a problem (although it is weird how you can still ping the printer)
Can you tell me more about the physical connectivity? How is it set up?
Is the physical network plugged into the Glasgow university campus, or is it just a physical network in your room?
If the physical network is not plugged into the wider network, then I would go to your static Ethernet settings and remove the Default gateway and the DNS servers so they are blank and see if that solves your issue.
If it is plugged into the uni network, then we'll wait until your reply with more information about the setup.
It looks like you are configured for two different networks, and both are configured to go out to the Internet, but if the ethernet network isn't connected to the Internet then this could potentially cause a problem (although it is weird how you can still ping the printer)
Can you tell me more about the physical connectivity? How is it set up?
Is the physical network plugged into the Glasgow university campus, or is it just a physical network in your room?
If the physical network is not plugged into the wider network, then I would go to your static Ethernet settings and remove the Default gateway and the DNS servers so they are blank and see if that solves your issue.
If it is plugged into the uni network, then we'll wait until your reply with more information about the setup.
|
Re: Wifi/ethernet conflict November 16, 2018 08:44AM |
Registered: 9 years ago Posts: 106 |
|
Re: Wifi/ethernet conflict November 16, 2018 10:56AM |
Registered: 8 years ago Posts: 123 |
Hey Bart,
That's odd. Anyway, default gateway is to tell that connection where to send packets that are not for that network. For the ethernet connection that should be blank. DNS has no point on that connection either, so leave blank for now so they do not have any effect.
From the command prompt can you paste the output from "route print" with both connections active. it should look like
That's odd. Anyway, default gateway is to tell that connection where to send packets that are not for that network. For the ethernet connection that should be blank. DNS has no point on that connection either, so leave blank for now so they do not have any effect.
From the command prompt can you paste the output from "route print" with both connections active. it should look like
Microsoft Windows [Version 10.0.17134.407]
(c) 2018 Microsoft Corporation. All rights reserved.
C:\Users\cheeseandham>route print
===========================================================================
Interface List
32...02 15 f7 e6 7d 39 ......Hyper-V Virtual Ethernet Adapter #2
7...00 ff 2d 88 dc b3 ......TAP-NordVPN Windows Adapter V9
26...64 00 6a 98 85 b8 ......Intel(R) Ethernet Connection (2) I219-V
11...64 00 6a 98 85 b8 ......Hyper-V Virtual Ethernet Adapter
13...18 4f 32 f2 11 78 ......Bluetooth Device (Personal Area Network) #2
1...........................Software Loopback Interface 1
===========================================================================
IPv4 Route Table
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 192.168.0.1 192.168.0.26 35
127.0.0.0 255.0.0.0 On-link 127.0.0.1 331
127.0.0.1 255.255.255.255 On-link 127.0.0.1 331
127.255.255.255 255.255.255.255 On-link 127.0.0.1 331
172.21.13.0 255.255.255.240 On-link 172.21.13.1 271
172.21.13.1 255.255.255.255 On-link 172.21.13.1 271
172.21.13.15 255.255.255.255 On-link 172.21.13.1 271
192.168.0.0 255.255.255.0 On-link 192.168.0.26 291
192.168.0.26 255.255.255.255 On-link 192.168.0.26 291
192.168.0.255 255.255.255.255 On-link 192.168.0.26 291
224.0.0.0 240.0.0.0 On-link 127.0.0.1 331
224.0.0.0 240.0.0.0 On-link 192.168.0.26 291
224.0.0.0 240.0.0.0 On-link 172.21.13.1 271
255.255.255.255 255.255.255.255 On-link 127.0.0.1 331
255.255.255.255 255.255.255.255 On-link 192.168.0.26 291
255.255.255.255 255.255.255.255 On-link 172.21.13.1 271
===========================================================================
Persistent Routes:
None
IPv6 Route Table
===========================================================================
Active Routes:
If Metric Network Destination Gateway
1 331 ::1/128 On-link
11 291 fe80::/64 On-link
26 291 fe80::/64 On-link
32 271 fe80::/64 On-link
11 291 fe80::4a5:79e4:6146:ee00/128
On-link
32 271 fe80::6c47:4533:8f75:307/128
On-link
26 291 fe80::d5ba:ff54:bb1d:72fb/128
On-link
1 331 ff00::/8 On-link
11 291 ff00::/8 On-link
26 291 ff00::/8 On-link
32 271 ff00::/8 On-link
===========================================================================
Persistent Routes:
None
|
Re: Wifi/ethernet conflict November 16, 2018 12:44PM |
Registered: 9 years ago Posts: 106 |
Hi cheeseandham,
The output of route print is:
Cheers,
Bart
The output of route print is:
===========================================================================
Interface List
14...8c 3b ad d4 6a 9a ......NETGEAR WNA3100M N300 Wireless Mini USB Adapter
11...f8 b1 56 d4 b0 14 ......Intel(R) 82579LM Gigabit Network Connection
1...........................Software Loopback Interface 1
15...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter
13...00 00 00 00 00 00 00 e0 Microsoft 6to4 Adapter
12...00 00 00 00 00 00 00 e0 Teredo Tunneling Pseudo-Interface
16...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #2
===========================================================================
IPv4 Route Table
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 172.30.128.1 172.30.166.79 25
127.0.0.0 255.0.0.0 On-link 127.0.0.1 306
127.0.0.1 255.255.255.255 On-link 127.0.0.1 306
127.255.255.255 255.255.255.255 On-link 127.0.0.1 306
172.30.128.0 255.255.128.0 On-link 172.30.166.79 281
172.30.166.79 255.255.255.255 On-link 172.30.166.79 281
172.30.255.255 255.255.255.255 On-link 172.30.166.79 281
192.168.0.0 255.255.255.0 On-link 192.168.0.10 276
192.168.0.10 255.255.255.255 On-link 192.168.0.10 276
192.168.0.255 255.255.255.255 On-link 192.168.0.10 276
224.0.0.0 240.0.0.0 On-link 127.0.0.1 306
224.0.0.0 240.0.0.0 On-link 192.168.0.10 276
224.0.0.0 240.0.0.0 On-link 172.30.166.79 281
255.255.255.255 255.255.255.255 On-link 127.0.0.1 306
255.255.255.255 255.255.255.255 On-link 192.168.0.10 276
255.255.255.255 255.255.255.255 On-link 172.30.166.79 281
===========================================================================
Persistent Routes:
None
IPv6 Route Table
===========================================================================
Active Routes:
If Metric Network Destination Gateway
14 41 ::/0 fe80::f2f7:55ff:febe:2680
1 306 ::1/128 On-link
11 276 fe80::/64 On-link
14 281 fe80::/64 On-link
14 281 fe80::1175:1ab:df01:d3bd/128
On-link
11 276 fe80::158e:8975:f3c:f63f/128
On-link
1 306 ff00::/8 On-link
11 276 ff00::/8 On-link
14 281 ff00::/8 On-link
===========================================================================
Persistent Routes:
None
Cheers,
Bart
|
Re: Wifi/ethernet conflict November 18, 2018 08:31AM |
Registered: 8 years ago Posts: 123 |
Bart,
Looks normal enough, so there is something odd going on here. Obviously it's quite difficult to diagnose something like this remotely, especially as you are dealing with another network that is not under your control either.
Please do the following:-
i) let me know your printers IP address
ii) ping this address, with the Ethernet disconnected (yes I know, but just in case)
iii) try a/some different browser(s) to connect to the duet while the wifi is on.
iv) (i presume you've tried this) rebooting with both adapters on
Just something else to mention, I've used a TP-Link TL-WR802N in client mode.
Cheap and maybe a little slow compared to Ethernet, but worked perfectly well and would means that your printer would be wireless, and more importantly on the same network
Looks normal enough, so there is something odd going on here. Obviously it's quite difficult to diagnose something like this remotely, especially as you are dealing with another network that is not under your control either.
Please do the following:-
i) let me know your printers IP address
ii) ping this address, with the Ethernet disconnected (yes I know, but just in case)
iii) try a/some different browser(s) to connect to the duet while the wifi is on.
iv) (i presume you've tried this) rebooting with both adapters on
Just something else to mention, I've used a TP-Link TL-WR802N in client mode.
Cheap and maybe a little slow compared to Ethernet, but worked perfectly well and would means that your printer would be wireless, and more importantly on the same network
|
Re: Wifi/ethernet conflict November 18, 2018 01:19PM |
Registered: 8 years ago Posts: 26 |
This arrangement of ethernet cable to Ormerod and separate wifi from laptop to internet was how I first set up my Ormerod following the instructions on the RepRapPro site. The route involved bridging the networks in the laptop. The link [reprapltd.com] was described how to do it (although the URL to the page hasn't been resurrected from the archive) the host page [reprapltd.com] has and the non working link is under the "Connect via web interface section"
I jumped from XP to Windows 8 and now 10 but the way I remember to do it (in W10) is
Control panel/ All control panel items/Network connections Then right click the icon and select "Bridge connections". I can't remember which of the 2 networks to select but it must be worth experimenting.
Good luck
Dennis
I jumped from XP to Windows 8 and now 10 but the way I remember to do it (in W10) is
Control panel/ All control panel items/Network connections Then right click the icon and select "Bridge connections". I can't remember which of the 2 networks to select but it must be worth experimenting.
Good luck
Dennis
|
Re: Wifi/ethernet conflict November 21, 2018 01:35PM |
Registered: 9 years ago Posts: 106 |
Hi cheeseandham & Dennis,
Thanks for your suggestions, I tried them all but nothing seemed to help. For the record, the printer's address is 192.168.0.20 and I can't ping that address with the ethernet cable disconnected, booting with or without either adapter connected doesn't change a thing and neither does bridging the Wifi and LAN.
As I was getting quite annoyed by this, what with it being nearly 2019 and me thinking that I shouldn't have to choose between either internet or printer connectivity, I borrowed the Windows 7 install dongle from our IT guy and reinstalled the whole shebang. I now have both internet and can talk to the 3D printer! At the same time! Still got a million updates to download and install, all my other software, and I don't even want to think about syncing Dropbox, Google drive and Onedrive, but at least both networks are working!
Thanks for all your help!
Bart
Edited 2 time(s). Last edit at 11/21/2018 01:38PM by bartdietrich.
Thanks for your suggestions, I tried them all but nothing seemed to help. For the record, the printer's address is 192.168.0.20 and I can't ping that address with the ethernet cable disconnected, booting with or without either adapter connected doesn't change a thing and neither does bridging the Wifi and LAN.
As I was getting quite annoyed by this, what with it being nearly 2019 and me thinking that I shouldn't have to choose between either internet or printer connectivity, I borrowed the Windows 7 install dongle from our IT guy and reinstalled the whole shebang. I now have both internet and can talk to the 3D printer! At the same time! Still got a million updates to download and install, all my other software, and I don't even want to think about syncing Dropbox, Google drive and Onedrive, but at least both networks are working!
Thanks for all your help!
Bart
Edited 2 time(s). Last edit at 11/21/2018 01:38PM by bartdietrich.
|
Re: Wifi/ethernet conflict November 21, 2018 03:48PM |
Registered: 8 years ago Posts: 123 |
Bart,
This was a bizarre issue, as Windows should deal with that configuration in normal operation.
I wonder if this and the other machine that suffered from this are from the same manufacturer or even the same model line? Perhaps the company that created their standard image made a mistake somewhere.
Glad it is fixed!
This was a bizarre issue, as Windows should deal with that configuration in normal operation.
I wonder if this and the other machine that suffered from this are from the same manufacturer or even the same model line? Perhaps the company that created their standard image made a mistake somewhere.
Glad it is fixed!
Sorry, only registered users may post in this forum.