Remote Shares problem

johnpoz

Did you change your network on your software firewalls, did they use to be 192.168.x.x and you changed them to 10.x.x.x ? Or were they running the 10.x network before?

When windows 7 sees a new network, it classifies it for its firewall - should of asked you, is network public or home, etc. If thinks it unknown or public then windows 7 would block access to file shares for sure.

thespazz

UUUUUUUUUUUUGHHHH. It had auto-assigned public. Back to Home and working. :)

Edit: So now I can access servers by IP, but cannot access by hostname. Any tips on this?

johnpoz

Are you trying to broadcast for them, use dns what?

from a command line what do you get when you ping hostname of computer, example

C:\Windows\System32>ping p4-28g

Pinging p4-28g.local.lan [192.168.1.4] with 32 bytes of data:
Reply from 192.168.1.4: bytes=32 time<1ms TTL=64
Reply from 192.168.1.4: bytes=32 time<1ms TTL=64
Reply from 192.168.1.4: bytes=32 time<1ms TTL=64

See how it resolved to fqdn there.

What happens with your machine? Do you want to use dns or just broadcast? You may have to enabled netbios over tcp, look at output of ipconfig /all

example

C:\Windows\System32>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : quad-w7
Primary Dns Suffix . . . . . . . : local.lan
** Node Type . . . . . . . . . . . . : Hybrid**
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : local.lan

Ethernet adapter gig:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek PCIe GBE Family Controller
Physical Address. . . . . . . . . : 00-21-9B-03-AC-A7
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2001:470:snipped:b85::666(Preferred)
Link-local IPv6 Address . . . . . : fe80::794f:b5ca:8dc7:92d7%10(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.1.100(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 2001:470:1f11:b85::1
fe80::209:5bff:fee2:ccdb%10
192.168.1.253
DHCPv6 IAID . . . . . . . . . . . : 234889627
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-12-99-CA-17-00-21-9B-03-AC-A7
DNS Servers . . . . . . . . . . . : 2001:470:snipped:b85::1
192.168.1.253
** NetBIOS over Tcpip. . . . . . . . : Enabled**

Also look at your node type - if sent in wrong mode it will not broadcast but only ask wins server, seen this on machines coming from schools where they were in P-node and would never broadcast.

thespazz

I have node type hyrbid as well as netbios over tcpip enabled. What is the difference between using broadcast or dns? I'm pretty sure I'm using broadcast.

edit: when trying to ping by hostname, it failed to find the host. pinging by IP works splendid.

edit2: to clarify, i do NOT have my own DNS servers.

thespazz

bump

wallabybob

@thespazz:

I have node type hyrbid as well as netbios over tcpip enabled. What is the difference between using broadcast or dns? I'm pretty sure I'm using broadcast.

edit: when trying to ping by hostname, it failed to find the host. pinging by IP works splendid.

edit2: to clarify, i do NOT have my own DNS servers.

If you don't have your own DNS servers then what are you expecting will translate a hostname given to ping into an IP address?

stephenw10

Is there no way of getting pfSense to translate hostnames to IPs based on it's dhcp table?

Steve

GruensFroeschli

Yes there is.
But you have to enable it under:
Services –> DNS forwarder
Enable the checkbox: "Register DHCP leases in DNS forwarder"

If your devices on the LAN use the pfSense as DNS server, it will resolve the DNS names for them.

johnpoz

"then what are you expecting will translate a hostname given to ping into an IP address?"

Well if netbios over tcp/ip is enabled and not blocked by firewall and node type set to allow for broadcast. And devices are on the same segment what will happen is a windows machine will broadcast for the name. Now will some other non windows machine answer this I have no idea.

http://technet.microsoft.com/en-us/library/bb727005.aspx
Local broadcast

Up to three NetBIOS Name Query Request messages are broadcast on the local subnet to resolve the IPv4 address of a specified NetBIOS name.

Can do a network capture and show you these packets. But just because your machine puts them on the wire, does not mean the other machine will answer.

You could also setup host or lmhost file to resolve your hostnames to ip, if your not wanting to use dns. But as mentioned you have a dns server right at your fingertips - your pfsense box, more than capable of resolving your your local hosts for you.

here you go is my windows machine broadcasting for a test123 machine. Nothing answers of course, but here is what goes out on the wire when a windows machines falls to broadcasting for netbios names.

broadcastfor.jpg_thumb

stephenw10

@GruensFroeschli:

Yes there is.


C:\Documents and Settings\Steve>ping voip841

Pinging voip841.fire.box [192.168.3.2] with 32 bytes of data:

Reply from 192.168.3.2: bytes=32 time=1ms TTL=63

Sweet! ;D

Steve