Question Locked

can't see office domain with VPN ?

0 helpful
12 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I've got a VPN setup with windows server 2000 (and winXP at home) but when I am connected I do not see the office domain under "Microsoft windows network", how can I fix that ?

notes:

- VPN clients are Windows Vista & XP Home/Pro
- VPN clients have windows firewall activated with "File and printer sharing" exception (checked/activated)
- not all (computer) clients have joined the domain but everyone of them can logon to the VPN
- when in "Microsoft windows network" it still shows the workgroups on the LAN and doesn't display anything related to the VPN network

12 replies

by jwilliams

Is the computer your trying to see this information from part of the domain? Else you will only see network shares. In fact I think you will only see network shares that you at one time have specified the file path to on your home machine, could be wrong on the second part though.

by jan.

no I have VPN clients that are part of a workgroup too, can they still see the domain? I'd like to know which policy (Active dir.) I could set for that if there is one.

by jwilliams

I'm not sure if you can set that or not; Knowing Microsoft probably not. What advantage do you hope to gain by allowing everyone to see every computer on the network? That sounds like a serious security risk to me. A better option would be to just tell people VPNing in, to remote desktop to computers. In this manner you have some minimum security in place. You can also set up network shares that people can access without VPNing in. Just shared the files you think people will need access to then they can get to them by opening a "Run Prompt" and typing the IP of the machine hosting the shares and then name of file...like this " \\192.168.1.2\share " Of course you would enter the IP of the machine and the name of the folder.

by shady108

how is the vpn setup??

i assume you connect to your wan ie 77.75.xx.xx and then your vpn gives them a new ip ie 192.168.0.100

can you ping the servers by name and by ip?

if so can you map network drives also just by typing in the location? \\server1\folder

by jan.

the vpn server is win server 2000 with one network adapter wich is also the domain controller for 5-10 users, not more than 3 users use VPN.

yes I get an IP address from the office.

I can ping the server by IP

If I ttype "\\server\folder" it doesn't work, UNC paths don't work. that is what I explained in post 1 of this topic..

by jwilliams

Is the "Everyone" group set up on this share? I think you might need that. i could be wrong. however this sound very familure to me, ill try to get you a link for solutions to "unable to connect network paths through vpn"

by jan.

ok just to make things clear, I can access the shares with the IP address, not the name of the server.

by Former member

\\ipaddress\sharename

Either that or create some lmhosts entries or use the local network's wins server.

by robo_dev

Windows domain authentication uses Kerberos over large UDP packets. Since UDP is a connectionless protocol, these packets are usually larger than the MTU size of the VPN...therefore they get fragmented and arrive out-of-order and are therefore dropped. No-tickee, no-washee (sorry, that's some Kerberos humor).

Set Kerberos to work over TCP instead of UDP.
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Lsa\Kerberos\Parameters]
"MaxPacketSize"=dword:00000001

http://support.microsoft.com/kb/244474

it looks like a DNS problem, but it's a UDP thing.

To fine tune things you should also adjust your MTU so fragementation is not happening for tcp packets.

Fixing the MTU by itself won't help because kerberos UDP packets larger than the physical MTU will just get dropped at the interface. (can't fit a grape thru a straw).

by jan.

"To fine tune things you should also adjust your MTU so fragementation is not happening for tcp packets."

The MTU setting of the win2000 server or the router or both ?

is the registry edit needed on the clients or the server or both ?

by robo_dev

The server will respond to TCP or UDP Kerberos packets, so no changes are needed at the server.

The mtu setting is sorta complex, but it's typically only the client that needs to be changed. I would only dig into MTU settings if you spot a performance issue.

MTU FAQ
http://www.dslreports.com/faq/5793

This discussion is closed to new replies.