Networking problems
-
Maynard Cornchowder
- Posts: 13
- Joined: 3. Feb 2017, 00:31
Re: Networking problems
I can connect to every other computer in the workgroup except the one I want..
-
scottgus1
- Site Moderator
- Posts: 20945
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: Windows, Linux
Re: Networking problems
That sounds like a working Virtualbox network connection, good! It would return a "\\Server can't be found" or something like that if the Virtualbox network wasn't connected.
When you type the user name, you also have to indicate the computer name first. If your shop network is controlled by a domain controller and the server you're trying to connect to is on the domain, you'd enter the user name as:
domainname\username
If you just have a bunch of PCs in a network, or the server is not on a domain, you'd enter as the user name:
server\username
where 'server' is the network name of the computer you're trying to reach.
"username" is the name of a user with suitable permissions on the computer you're trying to get into, not necessarily the name you're using to log into the guest OS with.
When you type the user name, you also have to indicate the computer name first. If your shop network is controlled by a domain controller and the server you're trying to connect to is on the domain, you'd enter the user name as:
domainname\username
If you just have a bunch of PCs in a network, or the server is not on a domain, you'd enter as the user name:
server\username
where 'server' is the network name of the computer you're trying to reach.
"username" is the name of a user with suitable permissions on the computer you're trying to get into, not necessarily the name you're using to log into the guest OS with.
-
Maynard Cornchowder
- Posts: 13
- Joined: 3. Feb 2017, 00:31
Re: Networking problems
with every other computer i usually type server\pos with the pw and it works just fine.
is there a way to see if my server is on a domain?
It's trying to connect to server,central,websapien,net
which is the name of the computer I'm trying to reach.
is there a way to see if my server is on a domain?
It's trying to connect to server,central,websapien,net
which is the name of the computer I'm trying to reach.
-
scottgus1
- Site Moderator
- Posts: 20945
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: Windows, Linux
Re: Networking problems
You need to find out what the status of the server holding the shared folder is. What is that machine's OS?
-
Maynard Cornchowder
- Posts: 13
- Joined: 3. Feb 2017, 00:31
Re: Networking problems
Windows 2000 Pro Service Pack 4
-
scottgus1
- Site Moderator
- Posts: 20945
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: Windows, Linux
Re: Networking problems
I'm going to have to suggest now that you google for further info. I don't know myself what limitations 2000 places on a network. If you guest is able to connect to other computers on your network and you can access shared folders on other computers in the guest, then Virtualbox is doing its job. It now becomes a question of how to connect an XP OS to a 2000 server. That's all the more I can help with in this situation.
Hope you can get things going!
Hope you can get things going!
-
Maynard Cornchowder
- Posts: 13
- Joined: 3. Feb 2017, 00:31
Re: Networking problems
Well thank you very much for helping me eliminate a list of other problems it could've been. I can hopefully manage it from here.
-
BillG
- Volunteer
- Posts: 5106
- Joined: 19. Sep 2009, 04:44
- Primary OS: MS Windows 10
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: Windows 10,7 and earlier
- Location: Sydney, Australia
Re: Networking problems
If you are in a workgroup you can forget about domains.
There are several reasons why you can't connect to a particular machine or see it in the network display. The first is that it is in the wrong network and can't be reached. The second is that it is not in the right workgroup. The third is that Netbios over TCP/IP is not enabled. The fourth is that file sharing is not enabled on the target machine.
If all of those check out OK and you are still in trouble I would suggest that you try a Windows server forum.
There are several reasons why you can't connect to a particular machine or see it in the network display. The first is that it is in the wrong network and can't be reached. The second is that it is not in the right workgroup. The third is that Netbios over TCP/IP is not enabled. The fourth is that file sharing is not enabled on the target machine.
If all of those check out OK and you are still in trouble I would suggest that you try a Windows server forum.
Bill