How to login to a domain through wireless Internet?

[Jskid]

We just setup a wireless network using a home wireless router. However no one can login to there domain account, probably because you need to login to Windows and enter the password to connect to the wireless network. What's the best way to resolve this problem?

 

[DelJo63]

That question has multiple issues.

1) at home, we seldomly use a DOMAIN; we use workgroups. An XP/Home system can only use the workgroup. Unless you have a Windows Server 2000,2003, or 2008 - -
you can only use workgroups.

2) the computer WiFi connects to your WiFi router, not a domain NOR a workgroup.
Connecting to the router should be possible using the Wireless Network Setup tool in the Controls. (it needs the service Wireless Zero Configuration to be running).

 

[DelJo63]

using an admin account:

• launch Control->User Accounts
  you should see all logins defined for this system
  I have four and all are visible
  If you have more than one and you can't
  see them all, then you're not using an admin account
  
  Click Change the way users log on or off
  [x] Use the Welcome screen
  [x] use Fast User Switching
  
  click apply
  
• launch run->services.msc
  scroll to find Net Logon
  dbl-click
  set Startup Type to MANUAL or DISABLED
  (this is where one would login to a domain AFTER joining it)

 

[Jskid]

That question has multiple issues.

1) at home, we seldomly use a DOMAIN; we use workgroups. An XP/Home system can only use the workgroup. Unless you have a Windows Server 2000,2003, or 2008 - -
you can only use workgroups.

2) the computer WiFi connects to your WiFi router, not a domain NOR a workgroup.
Connecting to the router should be possible using the Wireless Network Setup tool in the Controls. (it needs the service Wireless Zero Configuration to be running).

We do use Windows Server 2003s and 2008s and Windows XP Pro. They won't be able to get to the shared drives, will they?

 

[DelJo63]

Very unusual setup - - but it should be doable.

Step one is to connect to the router. This puts all systems on the same subnet.
Let the router use its DHCP to assign IP addresses for everyone OTHER THAN the servers.
Typically, the router is at x.y.z.1, so set the DHCP range to 2-10.
The servers need static addresses and you might set them to 20-30.
This can be manually OR depending upon the router make/model, you might be able
to map a MAC address directly to an IP address in the 20-30 range.

Your network is correct when

1. each system can ping any other (by ip address!)
2. and can resolve a domain name into its IP address, eg:
   run->cmd /k nslookup google.com. (note the trailing DOT)

This will allow the browser to get webpages and you can read/write email.

Step two is the sharing or other functions you intend from your Win/2xxx servers.
Simple Print/File Sharing(P/FS) does not require the server approach AND
if you need other server features, then P/FS will not be the approach to take.

Assuming you need Server functions, then each client computer will need to
JOIN the domain created by the Server. There's a lot of tasks to creating a Windows Server, and I'll refer you to the manuals for the details.

Once a system is JOINED, then the normal approach is to create folders on the server
where specific types of data are stored, and then use Map Network Drives ... on each Client system.

When the user (Client) systems boot, they frequently then use the Network Login service to access the server. It is possible that they can also still Login Locally and access the server when needed - - again, I'll refer you to the manuals

 

[Jskid]

Alright, thanks.