no network provider accepted the given path
Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance
This is the error message I get when trying to access xp machines from
my server.
The topology is as follows:
Server (2003 domain controller) is on 192.168.1.X network, hosted in
server farm.
XP machines 10.X.X.X office network.
I have an up and running IPSEC tunnel between the two networks. I can
ping from each network, and I can view the net shares from the XP
machines to the server, but not the other way around.
So to sum things up:
From the server, if i try to access my XP machines (all of them)
through FQDN OR through IP address (\\machinename OR \\IP) I get "no
network provider accepted the given path".
Looks like anything that has to do with TCP is blocked. (because even
trying to see the http printer host - is not possible)
Any help would be appreciated.
Thanks.
.
Relevant Pages
- RE: Strange Irregular DNS/Networking Problems
... My network is not a complicated set up and only has one domain controller. ... problems with DNS resolving after changing DNS servers. ... I was already using the server for DHCP. ... (microsoft.public.windows.server.dns) - Re: SBS 2003 Win XP/2000 Pro Clients TCP/IP Problems
... network and no DHCP services provided by any machines still on the network. ... Check all machines for DNS entries. ... It really sounds like a IP Address conflict the way the server stops ... > PCs, 3 of which are running Windows XP Pro, the rest 2000 Pro. ... (microsoft.public.windows.server.sbs) - Re: Vista, SBS 2003 and RAS not working
... We have a windows SBS 2003 server – straight out of the box, ... The VPN connection between your computer and the VPN server could not ... You mention that the clients are Vista machines, which means that their built-in firewall works on outgoing messages as well as incoming ones, and the firewall needs to be told that outgoing PPTP VPN connections should be allowed. ... Computers don't need to be joined to the domain to connect by VPN, by the way, so you can use other remote computers for testing, it's just that only domain machines get access to all network resources easily. ... (microsoft.public.windows.server.sbs) - Re: Problem getting a new XP computer to join an NT 4.0/Win 98 domain
... > the computers and the file server with the goal of getting ... > If you scan Network Neighborhood for the Entire Network after ... > booting, there are 3 workgroups: ... > machines to see and map to shares on the NT file server. ... (microsoft.public.windowsxp.network_web) - Re: Problem getting a new XP computer to join an NT 4.0/Win 98 domain
... > the computers and the file server with the goal of getting ... > If you scan Network Neighborhood for the Entire Network after ... > booting, there are 3 workgroups: ... > machines to see and map to shares on the NT file server. ... (microsoft.public.win2000.networking) |
|