Q. The landlord went to print a web page, where the page has in it a "Frame" that scrolled and had a persons professional resume and experince in it. When printed it would print the page as it is seen (like one would print a picture of it). Only the part of the frame showing (as scrolled) would print. I tried to get the "url" for the frame, but . . . but i dont know what i am doing. Want to print the "whole page"
So I have a NAS hooked up to a router-as-switch and I can't see it from my Surface Pro 2 anymore, at least in Network Neighborhood, but I can connect to it just fine via IP address.
What confuses me is that my desktop, which also runs Windows 8.1 Pro, can see it just fine.
@allquixotic, I'm pretty sure it had a defective SDD, which I replaced, but also when I did that I broke the sound. Broke the whole thing when I tried to fix the sound later.
Yeah
Anyways, back to my issue. I can't find out why this thing can't see my NAS.
It can't resolve by name and doesn't show up when I browse the network.
the stupid popup asking you if you want it to be a private or public network probably popped up while you were typing and you hit "n" or something and it automatically selected a choice for you
@allquixotic: Yes. I've checked: homegroup & sharing settings, firewall, tried both registry hacks, reset the router it's hooked up to and reconfigured it, checked UPnP on both routers, disabled router firewall
@BenRichards did you wireshark the DNS query and make sure it's asking your router? and do you get a different answer about the DNS result between your two computers?
would be super weird if the router is giving different query results to the separate hosts in response to the exact same request
but if the request differs, or isn't going to your router at all, there's your problem
in short, if you understand how to use wireshark, this problem should be eminently diagnosable, if not directly treatable (your next step is to know why whatever's effing up is effing up)
Oh... but I do see this on my tablet (for reference)
> C:\Users\Ben>ping 192.168.0.107
Pinging 192.168.0.107 with 32 bytes of data: Reply from 192.168.0.107: bytes=32 time=3ms TTL=64 Reply from 192.168.0.107: bytes=32 time=1ms TTL=64 Reply from 192.168.0.107: bytes=32 time=3ms TTL=64 Reply from 192.168.0.107: bytes=32 time=3ms TTL=64
Ping statistics for 192.168.0.107: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 1ms, Maximum = 3ms, Average = 2ms
> UDP: Typically, NBNS uses UDP as its transport protocol. The well known UDP port for NBNS traffic is 137.
TCP: NBNS can also use TCP as its transport protocol for some operations, although this might never be done in practice. The well known TCP port for NBNS traffic is 137.
@JourneymanGeek the only reason i am keeping my phone on Android 4.2.2 until the second soak KitKat build is released (the first soak build bricked about 10% of users' devices, no matter whether they'd previously rooted/tampered)
> In addition, to start a session or to send a datagram to a particular host rather than to broadcast the datagram, NBT will have to determine the IP address of the host with a given NetBIOS name; this is done by broadcasting a "Name Query" packet, and/or sending it to the NetBIOS name server. The response will have the IP address of the host with that name.
Most routers can't even proxy DNS properly, let alone act as a proper DNS server. See RFC 5625.
Try and find one that uses the popular dnsmasq software internally, which means it'll be one with a Linux kernel too.
Ob. Disclaimer - I wrote that RFC.
@BenRichards windows update installs new wifi driver -> new wifi driver wipes out old settings because it's considered a new "device" -> netBIOS settings are reset
> The 'client identifier' is an opaque key, not to be interpreted by the server; for example, the 'client identifier' may contain a hardware address, identical to the contents of the 'chaddr' field, or it may contain another type of identifier, such as a DNS name.
> You may receive this message after a system restoration when your network adapter has been changed before the backup.
@_@
> This behavior can occur if your network adapter has been changed to another model of network adapter without first being properly uninstalled by using the Add/Remove Hardware tool in Control Panel.
@Bob that would take about an hour on my desktop with the hardware RAID controller... "Booting controller kernel....................... / | \ / | \ / | \ / | \" ... but on my Surface Pro or NUC, about 2 minutes
> UDP: Typically, NBNS uses UDP as its transport protocol. The well known UDP port for NBNS traffic is 137.
TCP: NBNS can also use TCP as its transport protocol for some operations, although this might never be done in practice. The well known TCP port for NBNS traffic is 137.
translate this for me? The NetBios would have got the computer Name for the number, as sent out by that computer? And the netbios goes over the regular tcpip, but that is archaic? Instead the computer Name should be got via DNS? and where would this Name be "stored" then for the dns resolve?
so problem 1 is to get that annoying dialog to stop popping up when you go to tcpip properties; problem 2 is to enable netbios once you get it to stop; problem 3 is to stop bob from biting your ankle for using NetBIOS
@BenRichards Please don't ask to ask; if you simply ask your actual question, we will help you if we know the answer or can help you find it. This is much faster and simpler than asking if it's OK to ask. As a rule, it is always OK to ask in this channel. Please go ahead.
Most routers can't even proxy DNS properly, let alone act as a proper DNS server. See RFC 5625.
Try and find one that uses the popular dnsmasq software internally, which means it'll be one with a Linux kernel too.
Ob. Disclaimer - I wrote that RFC.
