Home Hub 4000 Computer Folder Sharing with Hostname Relative Network Path not working

Kursor17
Contributor

Prior to joining Bell, I was using my own router and using the ISP's modem in bridge mode and had/have a windows computer sharing certain folders on my local network.  I was able to connect to this windows computer with \\HostName instead of using the \\IPAddress.  However since having Bell installed with Bell Home Hub 4000 as acting as both my modem AND router, I'm unable to connect via the relative path of \\HostName.  I can connect via \\IPAddress.  Given nothing else has nothing else has changed, what do I need to do to be able to connect to the windows computer with the relative path of the hostname instead of using \\IPAddress  

0 3 2,301
1 helpful reply

Accepted Solutions

Issue seems to have self resolved either through a restart of the windows computer and/or simply enough time has passed (48+ hrs?).  I'm now able to connect via \\hostname and I'm adamant that I didn't do anything prior nor now.

To give more specifics of the original issue, prior to it self-resolving, The windows computer hostname was auto-populated in "Local Network" in VLC for Android that was on various wired and wireless devices on my local network.  However, when I had attempted to connect, it would be stuck "Loading...".  On a separate windows computer in both wired and wireless connections, I couldn't connect to the windows computer via \\hostname.  No changes were made on the windows computer that was sharing on the local network.  The temporary workaround prior to self resolving, was I had manually added the windows computer share via IP address as a SMB on each VLC device.

View reply in original post

3 REPLIES 3

ZaneP
Community All-Star
Community All-Star

Hi @Kursor17 

If you can browse shares by IP address but not by hostname, it could be a DNS issue.  

  • Is the HH4K DNS service running and working properly?
  • Do you get successful pings to the windows computer by IP address but not by its hostname? 
  • Are the DNS server entries the same on the computer as in the HH4K?
  • Did you recently update the Windows OS on the client computer?
  • Is there another computer you can attach to the HH4K, and attempt to connect to it via hostname?

Hopefully other on the forum will join in on this thread soon!

Meantime, keep us posted on your issue.

Cheers,

ZaneP

I am a Community All-Star and customer. I'm here to help by sharing my knowledge and experience. My views on Bell and the Community Forum are my own and not the views of Bell or any of its affiliates.

Issue seems to have self resolved either through a restart of the windows computer and/or simply enough time has passed (48+ hrs?).  I'm now able to connect via \\hostname and I'm adamant that I didn't do anything prior nor now.

To give more specifics of the original issue, prior to it self-resolving, The windows computer hostname was auto-populated in "Local Network" in VLC for Android that was on various wired and wireless devices on my local network.  However, when I had attempted to connect, it would be stuck "Loading...".  On a separate windows computer in both wired and wireless connections, I couldn't connect to the windows computer via \\hostname.  No changes were made on the windows computer that was sharing on the local network.  The temporary workaround prior to self resolving, was I had manually added the windows computer share via IP address as a SMB on each VLC device.

ZaneP
Community All-Star
Community All-Star

Glad to hear that the problem is resolved! A restart of the Windows computer was likely the solution, imo.

I am a Community All-Star and customer. I'm here to help by sharing my knowledge and experience. My views on Bell and the Community Forum are my own and not the views of Bell or any of its affiliates.