BeastOfBodmin
asked on
VPN to remote network problem seeing workgroups and accessing the remote server.
Hi,
I am trying to access my works network via vpn, the administrators have given me the ip to connect to and enabled my logon name and password but when I connect I cannot see the workgroup at all .
The same machine when connected to the works lan can see the workgroup and access all areas of the network I have permissions for .
Can any one walk me through this , I'm having to come up to speed in a hurry. I have been given the tools but am lacking in the experience.
I am using Windows server 2003
Remote server is unix based?
I am trying to access my works network via vpn, the administrators have given me the ip to connect to and enabled my logon name and password but when I connect I cannot see the workgroup at all .
The same machine when connected to the works lan can see the workgroup and access all areas of the network I have permissions for .
Can any one walk me through this , I'm having to come up to speed in a hurry. I have been given the tools but am lacking in the experience.
I am using Windows server 2003
Remote server is unix based?
ASKER
before the admin staff left work this evening I was told to allow protocol 47 in my NAT FIREWALL / ROUTER will this be an issue?
ASKER
i'm not sure if the protocol issue is an issue at all since I can connect through the vpn and my logon and password are accepted, and I can ping all the computrs on the network (I just cant see the computers in my workgroup)
If you can ping, then you are correct that you don't have any firewall/router issues.
What you have is a netbios name resolution issue.
Try creating a LMHOSTS file on you PC that has at a minimum the domain controller entries:
How to Write an LMHOSTS File for Domain Validation and Other Name Resolution Issues
http://support.microsoft.com/support/kb/articles/Q180/0/94.ASP
What you have is a netbios name resolution issue.
Try creating a LMHOSTS file on you PC that has at a minimum the domain controller entries:
How to Write an LMHOSTS File for Domain Validation and Other Name Resolution Issues
http://support.microsoft.com/support/kb/articles/Q180/0/94.ASP
Are you running WINS? Is Netbios over TCPIP configured?
If you not running wins, and you can ping them, then create static entries in your host file reflecting the IP to hostname:
hosts file is located c:\windows\system32\driver
it has no exstension on it, but you can edit it in notepad, with an entry like this:
192.168.1.5 server1
192.168.1.5 computer2
I am thinking the HOSTS file editing is going ot be the correct route for you, especially since you can ping everything.
If you not running wins, and you can ping them, then create static entries in your host file reflecting the IP to hostname:
hosts file is located c:\windows\system32\driver
it has no exstension on it, but you can edit it in notepad, with an entry like this:
192.168.1.5 server1
192.168.1.5 computer2
I am thinking the HOSTS file editing is going ot be the correct route for you, especially since you can ping everything.
Or the LMHOSTS....
ASKER
thanks lrmoore and Mazaraat , i'll read a bit more and see if I can ask the right question , as I said I'm having to get up to speed on the networking and vpn.
There's been a change to the servers and now there's a problem I suddenly find myself needing to know how to fix it :)
showing my ignorance here !
i'll get back in the next few hours.
There's been a change to the servers and now there's a problem I suddenly find myself needing to know how to fix it :)
showing my ignorance here !
i'll get back in the next few hours.
ASKER
Made a start but I am completely ignorant as to what I am writing for the lmhosts file do I just copy the lines mentioned or do I edit them?
10.0.0.1 PDCNAME #PRE #DOM:DOMAIN-NAME
10.0.0.1 "DOMAIN-NAME \0x1b" #PRE
# IP Address "123456789012345*7890"
??? sorry
10.0.0.1 PDCNAME #PRE #DOM:DOMAIN-NAME
10.0.0.1 "DOMAIN-NAME \0x1b" #PRE
# IP Address "123456789012345*7890"
??? sorry
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
The servers were migrated to newer versions and we have experienced some problems where users on the network get internet access but also cannot gain accees to the workgroup or to their shared folders.