• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

DNS Problem - Domain

D

djnes

Fully [H]
Joined
Mar 24, 2000
Messages
19,560
I may not be describing this very well, but here goes.

My company recently switched to a new ISP. I updated our router with the proper IP and DNS settings. We seem to be okay from that standpoint. However, I have 2 remote users who can't connect to anything by name once they VPN in. I can ping their machines, and they can access network shares by IP (such as \\1.2.3.4\Shared), but not by name. Several of my other remote users aren't having any trouble. All remote users connect to a Windows 2003 server using the built in XP VPN connection. DNS is one of my weak points, but our internal DNS settings shouldn't be affected by the outside ISP's DNS, would they? I haven't reboot any of my DCs since we switched ISPs on Friday afternoon....could this be the problem? If not, where would I start looking to troubleshoot this? Again, it only affects 2 out of 10 users.
 
May be stating a obvious thing but did you try ipconfig /flushdns ?
 
I sent that to the remote people, and have yet to hear a response.
 
Im just guessing but rebooting the server may be the key..if you changed the IP and DNS settings on the router...but the server still has the old settings?
Im guessing the server is also doing routing for the VPN to the network, so if it doesnt have the right IP settings...
 
I take it your DNS server handles both internal network and public requests? Our DNS server only manages the DNS for our internal network domain, and forwards the rest to the ISP DNS servers. If that is the case, I would think you would need to change the addresses for the new ISP's DNS in the forwarding setup.
 
Can they reach internal servers over VPN by using the FQDN? If so, have them make an entry to the DNS search suffixes for your internal domain.
 
it is a small enough network, and it is NOT a huge issue - try these things to resolve:

first - have the users HARD SET the DNS ip's in the VPN connection to your work DNS server IP's. I have had luck doing that

Second - if you can - enable NetBIOS over TCP/IP on the servers that they are trying to get to. that should open up the friendly-name UNC stuff. \\servername\sharename

just a few ideas
 
NetAxis said:
first - have the users HARD SET the DNS ip's in the VPN connection to your work DNS server IP's. I have had luck doing that
Click to expand...
I'm going to try this today and see how it works. This way, when the users connect by VPN, that connection will use our internal DNS servers, which should correct the problem. As a temporary workaround, I had them change their shortcuts to use the IP addresses.
 
Okay, here's what I tried. I did the ipconfig /flushdns, nbtstat -R, and nbtstat -RR. I rebooted the main server overnight, and also had the same users hard-code our internal DNS settings into the VPN's IP settings. All of them can connect to our network remotely, but still can't access anything by name. I've currently re-mapped a bunch of their shortcuts to use the IP address, so they all have a temporary workaround. I'm running out of ideas at this point. What still baffles me is that 10 other people can connect fine.
 
Ok, is the 10 guys running the same os configuration and if the 2 who can't connect running a different configuration ?
 
To the best of my knowledge, they are. I didn't configure their computers, but from what I can tell, they all should be the same.
 
\\NAMEOFCOMPUTER\ is normally used with WINS and not DNS. Check with the VPN on the windows 2003 server for WINS Server, and make the WINS server is the Windows 2003, and of course setup WINS. Its not hard, may take 3 minutes or could take you while if you dont have the install disc.
 
trav04 said:
\\NAMEOFCOMPUTER\ is normally used with WINS and not DNS. Check with the VPN on the windows 2003 server for WINS Server, and make the WINS server is the Windows 2003, and of course setup WINS. Its not hard, may take 3 minutes or could take you while if you dont have the install disc.
Click to expand...


Don't use WINS unless you're still using NT4. It's dead. Windows UNCs work fine with DNS.
Did you try using the FQDN? Usually when my users cant connect to machines by name over VPN, that's what it is. They're trying to resolve "{server}.comcast.com" (or whatever) instead of "{server}.yourcompany.com".
 
Gambrinus said:
Don't use WINS unless you're still using NT4. It's dead. Windows UNCs work fine with DNS.
Did you try using the FQDN? Usually when my users cant connect to machines by name over VPN, that's what it is. They're trying to resolve "{server}.comcast.com" (or whatever) instead of "{server}.yourcompany.com".
Click to expand...
I have this down and what I'm going to try tomorrow.
 
You must log in or register to reply here.
Back
Top