General discussion

Locked

Loging on to our domain with our wan.

By jbowman ·
The Computers connected to our network via a 56k line through our T1 can't login to our domain server. They also can't see any of our computers in network neiborhood, but they can ping every computer over the wan.
The only protocols installed are TCP/IP and netbeui. Should we install IPX/SPX to fix this problem? Or is it something else?

This conversation is currently closed to new comments.

5 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

Loging on to our domain with our wan.

by howardhenderson In reply to Loging on to our domain w ...

Hi,

There are several things to make sure are lined out depending on your exact scenario:

If you are pinging, then you have low-level connectivity. Not 'seeing' computer names in the network implies a name resolution problem. Either check your WINS server and/or clients settings to make sure WINS is operating properly.

If you are using static IP addresses, and have a small # of PC's, just create hosts files and/or lmhosts files on each PC.

Both of these solutions are ways to explain to your PC's that x.y.q.z IP adress maps to 'mainserver' server or 'joeuser' workstation.

Don't install IPX/SPX unless you have a valid reason.

Remember, NETBEUI isn't routable, so that protocol is not going to deliver any connectivity through a router.

There are several other points that could be pertinent here, but those should get you started...

Hope this helps,
Howard H.

Collapse -

Loging on to our domain with our wan.

by jbowman In reply to Loging on to our domain w ...

Can you help me with wins?
My email is jbowman@c-ws.net
Thanks for you help.
Jed

Collapse -

Loging on to our domain with our wan.

by Mike I. In reply to Loging on to our domain w ...

This sounds similar to a problem we had both dialing in and over our LAN. In our case, we would get an error message at login saying that the user was not recognized,then "do you want to specify a different domain" or words to that effect. Our solution takes three restarts. First, choose to switch the domain - then uncheck the context selection and choose the default server option at the top of the dialog - pick your domain name from the drop down, or type it if it does not appear. Save and restart. You will get the same error message. This time change the domain by typing in your exact context. Save and close and restart. You will probably get the same error message again. This time when you go to the "change domain" dialog, leave the context choice as is and save and close. Restart - you should now log on trouble-free.
A bit convoluted, but it does the trick on our wan and our lan when this error pops up.

Collapse -

Loging on to our domain with our wan.

by jbowman In reply to Loging on to our domain w ...

Poster rated this answer

Collapse -

Loging on to our domain with our wan.

by jbowman In reply to Loging on to our domain w ...

This question was closed by the author

Back to Windows Forum
5 total posts (Page 1 of 1)  

Related Discussions

Related Forums