cant connect by \\name sometimes
cant connect by \\name sometimes
Sometimes I cannot access servers by their \\servername. The only way I can access them is by their full DNS name (servername.domain.local). I am connected via VPN and my w2k3 primary DNS server is the first one being handed out. Im not sure if its something with Cox in Phx because we have a small office connected and they have to use the full DNS name all the time.
any help appreciated
any help appreciated
Will Work For FSB
- YeOldeStonecat
- SG VIP
- Posts: 51171
- Joined: Mon Jan 15, 2001 12:00 pm
- Location: Somewhere along the shoreline in New England
Don't need WINS, just DNS should do it. Well...lemme rephrase that....Win2K or XP clients don't need WINS, only DNS, whereas Win9X clients need WINS. Win9X clients should have WINS even for local networks...to keep broadcasts to a minimum.
Did you have bandwidth allocated to the VPN? You know in the Sonics...you can divy up your bandwidth and assure that the VPN gets primary attention, instead of default...where it gets splitup according to whatever needs there are.
The DC should be the one and only DNS server handed out, you mention it's the first one....if you have any second DNS servers...what are they? ISP DNS? In which case I'd remove that. Or a second DC on the network, which I'd think would be OK.
Did you have bandwidth allocated to the VPN? You know in the Sonics...you can divy up your bandwidth and assure that the VPN gets primary attention, instead of default...where it gets splitup according to whatever needs there are.
The DC should be the one and only DNS server handed out, you mention it's the first one....if you have any second DNS servers...what are they? ISP DNS? In which case I'd remove that. Or a second DC on the network, which I'd think would be OK.
MORNING WOOD Lumber Company
Guinness for Strength!!!
Guinness for Strength!!!
- YeOldeStonecat
- SG VIP
- Posts: 51171
- Joined: Mon Jan 15, 2001 12:00 pm
- Location: Somewhere along the shoreline in New England
Play around, give a high percentage at first, like 70% or so.
Might wanna try yanking the ISP DNS servers, wonder if it queries the DC DNS, doesn't get a response fast enough, so moves onto the 2nd DNS, which naturally wouldn't know about your LAN setup.
How many satellite PCs? Give a shot with an lmhost entry?
Might wanna try yanking the ISP DNS servers, wonder if it queries the DC DNS, doesn't get a response fast enough, so moves onto the 2nd DNS, which naturally wouldn't know about your LAN setup.
How many satellite PCs? Give a shot with an lmhost entry?
MORNING WOOD Lumber Company
Guinness for Strength!!!
Guinness for Strength!!!
- YeOldeStonecat
- SG VIP
- Posts: 51171
- Joined: Mon Jan 15, 2001 12:00 pm
- Location: Somewhere along the shoreline in New England
- koldchillah
- Senior Member
- Posts: 4629
- Joined: Thu Apr 04, 2002 1:45 pm
- Location: Orlando
That was going to be my first guess, having dealt with a similar situation when I was first inherited my current network..YeOldeStonecat wrote: ISP DNS? In which case I'd remove that.
As YOSC already touched on, those ISP DNS servers should only be used as external forwarders configured within the DNS server properties. As far as the LAN clients are concerned, the DC should be their only DNS server. That way the clients don't end up looking outside your network while trying to resolve internal hosts.
I was just messing around with a sonicwall in new mexico and I couldnt get the name to resolve. I only had the private DNS server listed and when I did a DNS name lookup from the sonicwall the server that it used to check the name was my DNS server. I resolve with full DNS for both DNS lookup and ping only, this is a qwest DSL connection.
editing the host file works but I dont want to do that on every remote PC we have.
editing the host file works but I dont want to do that on every remote PC we have.
Will Work For FSB
- koldchillah
- Senior Member
- Posts: 4629
- Joined: Thu Apr 04, 2002 1:45 pm
- Location: Orlando
I don't have much experience with SonicWalls, but if this isn't a bandwidth setting issue:
Are you using dynamic DNS? w/ scavenging?
Can you do a reverse lookup?
Kinda silly, but port 53 isn't getting blocked along the way anywhere right?
You should be able to add the host records and/or PTR records manually to the server instead of modifying host files on each local machine..
Are you using dynamic DNS? w/ scavenging?
Can you do a reverse lookup?
Kinda silly, but port 53 isn't getting blocked along the way anywhere right?
You should be able to add the host records and/or PTR records manually to the server instead of modifying host files on each local machine..
- koldchillah
- Senior Member
- Posts: 4629
- Joined: Thu Apr 04, 2002 1:45 pm
- Location: Orlando
Sonicwall 2040 at corporate, tele3 SP at 2 of the offices. Tele3 SP has 6606 firmware and the sonic has sonicOS 2.0 I think. I have the Tele 3 at 2 locations and the TZ 170 SP in about 5 offices.
I added 2 of the PCs into the domain and I dont have problems using UNC name now, I didnt add my home PC to the domain though. None of my remote PCs have been added to the domain yet but they dont have problems accessing servers by UNC name.
I added 2 of the PCs into the domain and I dont have problems using UNC name now, I didnt add my home PC to the domain though. None of my remote PCs have been added to the domain yet but they dont have problems accessing servers by UNC name.
Will Work For FSB